db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (DERBY-4319) hang in suites.all with ibm 1.5 on AIX after ttestDefaultProperties
Date Tue, 19 Apr 2011 07:59:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021457#comment-13021457
] 

Knut Anders Hatlen edited comment on DERBY-4319 at 4/19/11 7:58 AM:
--------------------------------------------------------------------

I'm wondering if this could have the same root cause as DERBY-5192 (fixed after 10.8.1.1).
That could prevent server shutdown from terminating the server, which would leave the server
process running forever. Since NetworkServerTestSetup waits until the external process terminates,
the test will just hang there. What Kathey observed when she pinged the hanging server on
AIX is also consistent with what I saw when I pinged a server that hung because of DERBY-5192
(see comment https://issues.apache.org/jira/browse/DERBY-5192?focusedCommentId=13020264&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13020264
).

      was (Author: knutanders):
    I'm wondering if this could have the same root cause as DERBY-5192 (fixed after 10.8.1.1).
That could prevent server shutdown from terminating the server, which would leave the server
process running forever. Since NetworkServerTestSetup waits until the external process terminates,
the test will just hang there. What Kathey observed when she pinged the hanging server on
AIX is also consistent with what I saw when I pinged a server that hung because of DERBY-5192
(see comment https://issues.apache.org/jira/browse/DERBY-5192?focusedCommentId=13020264&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13020264).
  
> 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: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message