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

Myrna van Lunteren commented on DERBY-4319:
-------------------------------------------

system/derby.log  at the time of the hang had 1 start ( on port 1531) and 3 
shutdowns.
2009-07-18 03:15:51.865 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
started and ready to accept connections on port 1531
2009-07-18 03:15:58.988 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
shutdown
2009-07-18 03:15:59.101 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
shutdown
2009-07-18 03:15:59.257 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
shutdown

logs/serverConsoleOutput.log had this: 
2009-07-18 03:15:03.669 GMT : Could not connect to Derby Network Server on host
127.0.0.1, port 1528: A remote host refused an attempted connect operation.
2009-07-18 03:15:04.177 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
started and ready to accept connections on port 1528
2009-07-18 03:15:04.259 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
shutdown
2009-07-18 03:15:04.361 GMT : Could not connect to Derby Network Server on host 
127.0.0.1, port 1528: A remote host refused an attempted connect operation.
2009-07-18 03:15:04.445 GMT : Could not connect to Derby Network Server on host
127.0.0.1, port 1527: A remote host refused an attempted connect operation.
2009-07-18 03:15:04.548 GMT : Could not connect to Derby Network Server on host
127.0.0.1, port 1527: A remote host refused an attempted connect operation.
2009-07-18 03:15:04.658 GMT : Could not connect to Derby Network Server on host
127.0.0.1, port 1527: A remote host refused an attempted connect operation.
2009-07-18 03:15:04.768 GMT : Could not connect to Derby Network Server on host
127.0.0.1, port 1527: A remote host refused an attempted connect operation.
2009-07-18 03:15:04.848 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
started and ready to accept connections on port 1527
2009-07-18 03:15:40.465 GMT : Apache Derby Network Server - 10.5.2.0 - (794445)
shutdown

I don't find any further helpful info.

> hang in suites.all with ibm 1.5 on AIX after ttestDefaultPort
> -------------------------------------------------------------
>
>                 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.

Reply via email to