users@tyrus.java.net

Grizzly worker thread

From: Jimmy Lin <y2klyf+work_at_gmail.com>
Date: Tue, 26 Aug 2014 01:44:57 -0700

Hi,
after creating(ClientManager.connectToServer) and closing(Session.close)
tyrus endpoint multiple times, we found out there are many Grizzly(1) (2)
and Selector thread left over in our VM.

Basically every time when our application detected session's state is
close(abnormally), we will first called session.close (attempt to clean up
everything) and then create new endpoint.

is it the best practice to clean up Grizzly worker threads in Grizzly
container/socket?
(basically assuming session.close will do all the magic, but apparently
somehow Grizzly threads still around)


thanks