[ http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12415066 ]
Deepa Remesh commented on DERBY-1326: ------------------------------------- I am seeing a hang in the test derbynet/DerbyNetNewServer.java with 'resolve_DRDConnThread_conflict.diff'' patch. I was using the same workspace where I had applied this patch to try out some things for DERBY-803. I started seeing a hang in derbynet/DerbyNetNewServer.java test. On looking at the .tmp file, I found that the test itself was running to the end. It looked like it was waiting for network server process to stop. I rechecked by reverting my changes, reapplying the patch and running a full build. I was still getting a hang in the test. It looks like there are additional changes in network server shutdown introduced by this patch. In an earlier mail, Bryan had mentioned that derbyall ran successfully with this patch. This could be because of "timeout=60" property specified in derbynetclientmats suite. To check this, I ran the test by specifying "-Dtimeout=3" on the command line. Then, the test process ran to the end within the timeout period and the test passed. It had this additional line on the console: "Server Process did not complete in time. Destroying..." Bryan, if you still have the results from derbyall run with this patch, can you please check to see how long the test derbynet/DerbyNetNewServer.java took? If it took close to an hour to complete, it will confirm what I just observed. Otherwise, it may be a problem with my test environment. > 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 > Type: Bug > Components: Network Server > Reporter: Deepa Remesh > Assignee: Bryan Pendleton > Attachments: repro1326.java, resolve_DRDConnThread_conflict.diff, > sessionMgmt1.diff, sessionMgmt1_and_nosessionsforclosedthreads.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
