[ http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434299 ] Bryan Pendleton commented on DERBY-1326: ----------------------------------------
> Does anyone see problems with reusing the threads? Deepa and I discussed this a fair amount in DERBY-1219; you should probably review that discussion to see if there's more you can learn from it. In particular, the discussion regarding "skipThreads.diff" at: http://issues.apache.org/jira/browse/DERBY-1219#action_12378300 If we didn't close down the threads, would we do anything to notify them of the shutdown? Were you proposing to leave them alone entirely? Or were you proposing to notify them of the shutdown, but not require the threads to exit? Are you sure a DRDAConnThread doesn't have dependencies on the engine instance? The thread has a pointer to a session, and a session seems like it could point to database objects (like Connection objects, e.g.) > 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
