[
https://issues.apache.org/jira/browse/DERBY-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden resolved DERBY-4319.
-----------------------------------
Resolution: Fixed
I marked this derby_backport_reject_10_5, not because of any risk but this
issue has just test changes made during the diagnosis of this issue. The real
fix it seems came under DERBY-5192, so there is no real value to backporting
to 10.5
If someone ever wants these changes in older releases for some reason it should
be fine to do so.
> 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_backport_reject_10_5
> Fix For: 10.8.1.2
>
> Attachments:
> LaunchedNetworkServer.javacore.20110309.160148.6488248.0001.txt,
> LaunchedNetworkServerAfterPing.javacore.20110310.124948.6488248.0002.txt,
> TestOutput2011-03-09.txt,
> TestProcess.javacore.20110310.123703.4390978.0001.txt,
> derby-4317_timeout_for_complete_diff.txt,
> derby-4319_disableSetPortPriorityAndDefaultProperties_diff.txt,
> derby-4319_disable_setPortPriorty_diff.txt,
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
