db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4319) hang in suites.all with ibm 1.5 on AIX after ttestDefaultProperties
Date Wed, 09 Mar 2011 22:10:59 GMT

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

Kathey Marsden commented on DERBY-4319:
---------------------------------------

There was some network maintenance that seems to be what got the aix machine out of its problematic
 state.   Myrna said in the past after reboot (this time it wasn't reboot but reboot of the
router) it will work for a while and then start to consistently fail.  I kicked of fifty runs
of the derbynet suite to see if I can get the machine back into the problematic state.



> 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-4317_timeout_for_complete_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