Hi,
Our webapp creates several background long lasting threads (almost
permanent).
Those threads are worker threads which are synchronized and designed for
performance, no dead locks and fastest user experience.
However, it seems that Glassfish doesn't love long lasting threads when a
Servlet opens a thread with new Thread(something).start() glassfish admin
console might hand with "long lasting thread detected....".
Any way to suggest to Glassfish that those threads are app based background
threads?
Maybe setting then to "Deamon" would do, but those deamon threads might
prevent JM to shutdown.