[ http://issues.apache.org/jira/browse/DERBY-1966?page=comments#action_12450772 ] Daniel John Debrunner commented on DERBY-1966: ----------------------------------------------
Also occurs if a reference to the NetworkServerControl used to start the server is kept. Can reproduce this by not nulling out networkServerController in the tearDown method of NetworkServerTestSetup and then run a JUnit test that uses the decorator repeatably within the same JVM. Using the MathTrigFunctionsTest in the swingui (just keep clicking run once the test completes) I saw about 2 failures to start the network server every 15 runs. > NetworkServer startup can take 50+ seconds if a client holds an open > connection to the previous server booted within the same vm > -------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1966 > URL: http://issues.apache.org/jira/browse/DERBY-1966 > Project: Derby > Issue Type: Bug > Components: Network Server > Affects Versions: 10.3.0.0 > Environment: Windows XP - IBM JVM 1.4.2 > Reporter: Daniel John Debrunner > > Seen when a client in the same jvm held a open connection to a previously > booted network server within the same jvm. > Order would be: > boot server > client connect to server (hold onto connection and don't close) > shutdown server > boot server <<<<<------ this boot will take 50+ seconds -- 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
