[
https://issues.apache.org/jira/browse/DERBY-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4319:
----------------------------------
Attachment: derby-4319_teardown_kill_on_bad_ping.txt
The attached patch changes NetworkServerControl.tearDown() to print the stack
trace and destroy the server process if the test ping fails to some error other
than the standard Cannot Connect error that happens if the server is not up.
Before the patch if the ping failed for any reason the assumption was that the
server was down.
This doesn't eliminate the possibility for a hang entirely as if the test ping
itself were to hang, then we would still have the problem.
Note this patch does not get at the root cause of the Connection reset error on
aix, but will hopefully get the tests to finish their run. Currently if the the
process destruction is required, it won't result in the failure of a test, just
the print of the stacktrace to system.out.
> hang in suites.all with ibm 1.5 on AIX after ttestDefaultProperties
> -------------------------------------------------------------------
>
> Key: DERBY-4319
> URL: https://issues.apache.org/jira/browse/DERBY-4319
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.5.2.0
> Environment: ibm jvm 1.5 SR9-0 on IBM AIX 3.5
> Reporter: Myrna van Lunteren
> Assignee: Kathey Marsden
> Labels: derby_triage10_8
> Attachments: derby-4319_teardown_kill_on_bad_ping.txt,
> javacore.20090723.093837.25380.0001.txt,
> javacore.20090723.093909.24726.0001.txt
>
>
> 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 for DERBY-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:
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
