Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
10.5.2.0
-
ibm jvm 1.5 SR9-0 on IBM AIX 3.5
-
Urgent
-
High Value Fix
-
Regression Test Failure
Description
The test run for 10.5.2.0 hung in suites.All. The console output (the run was with -Dderby.tests.trace=true) showed ttestDefaultProperties had successfully completed but the run was halted.
ps -eaf | grep java showed the process that kicked off suites.All, and a networkserver process with the following flags:
- classpath <classpath including derby.jar, derbytools.jar, derbyclient.jar, derbynet.jar, derbyTesting.jar, derbyrun.jar, derbyTesting.jar and junit.jar> -Dderby.drda.logConnections= -Dderby.drda.traceAll= -Dderby.drda.traceDirectory= -Dderby.drda.keepAlive= -Dderby.drda.timeSlice= -Dderby.drda.host= -Dderby.drda.portNumber= -derby.drda.minThreads= -Dderby.drda.maxThreads= -Dderby.drda.startNetworkServer= -Dderby.drda.debug= org.apache.derby.drda.NetworkServerControl start -h localhost -p 1527
This process had been sitting for 2 days.
After killing the NetworkServerControl process, the test continued successfully (except forDERBY-4186, fixed in trunk), but the following was put out to the console:
START-SPAWNED:SpawnedNetworkServer STANDARD OUTPUT: exit code=137
2009-07-18 03:16:07.157 GMT : Security manager installed using the Basic server
security policy.
2009-07-18 03:16:09.169 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
started and ready to accept connections on port 1527
END-SPAWNED :SpawnedNetworkServer STANDARD OUTPUT:
Attachments
Attachments
Issue Links
- is related to
-
DERBY-5192 Setting up network server for management tests hangs intermittently
- Closed
- relates to
-
DERBY-4176 java.net.SocketException: Connection reset with ibm 1.5. running ServerPropertiesTest in suites.All
- Closed
-
DERBY-5122 Placeholder for marking disabled tests.
- Open