[ http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434428 ] Knut Anders Hatlen commented on DERBY-1326: -------------------------------------------
I'm also exploring these options: 1) Poisoning all active threads (those with session != null) and keeping the free threads. 2) Poisoning all threads and make poisoned threads put sessions back in runQueue. This would also require moving the creation of new threads to runQueueAdd() in order to prevent the queue from growing bigger than the pool of free threads. > Network server may abandon sessions when Derby system is shutdown and this > causes intermittent hangs in the client > ------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-1326 > URL: http://issues.apache.org/jira/browse/DERBY-1326 > Project: Derby > Issue Type: Bug > Components: Network Server > Reporter: Deepa Remesh > Assigned To: Knut Anders Hatlen > Attachments: repro1326.java, resolve_DRDConnThread_conflict.diff, > Restart.java, sessionMgmt1.diff, > sessionMgmt1_and_nosessionsforclosedthreads.diff, > unify_NSImpl_instances.diff, withNewThreadAndNoShutdownOfCurrentSession.diff > > > This issue was found when working on DERBY-1219. More details can be found in > the comments at http://issues.apache.org/jira/browse/DERBY-1219 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
