db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4053) suites.All hang with message java.net.BindException: Address already in use: NET_Bind in derby.log
Date Fri, 12 Jun 2009 19:47:07 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Mike Matrigali updated DERBY-4053:

Looking at the javacore the tests are hung waiting on a ping:
"main" prio=6 tid=0x003e9c00 nid=0x10ac runnable [0x0023f000..0x0023fe28]
   java.lang.Thread.State: RUNNABLE
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at java.net.SocketInputStream.read(SocketInputStream.java:90)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.fillReplyBuffer(Unknown Source)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(Unknown Source)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.pingWithNoOpen(Unknown Source)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(Unknown Source)
        at org.apache.derby.drda.NetworkServerControl.ping(Unknown Source)
        at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerUp(NetworkServerTestSetup.java:546)
        at org.apache.derbyTesting.junit.NetworkServerTestSetup.pingForServerStart(NetworkServerTestSetup.java:615)
        at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:191)

If anyone can reproduce this it might be interesting to instrument pingForServerUp to
see what path it is taking through this code.  Did the while loop go more than once,
what are all the variables to the routine, did it hit any of the try/catch blocks (some 
don't do anything), ...

It seems like this setup code should be changed to not wait forever in the ping since
the tests seem to be able to break the network server and make it not ping.  So maybe some
sort of timer thread could be used to make the ping not take forever.  
It would be best to understand why the ping is taking forever and maybe if we did
not hang then we could add more diagnostics to this routine to figure why the ping
is not returning.

> suites.All hang with message java.net.BindException: Address already in use: NET_Bind
in derby.log 
> ---------------------------------------------------------------------------------------------------
>                 Key: DERBY-4053
>                 URL: https://issues.apache.org/jira/browse/DERBY-4053
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions:
>            Reporter: Kathey Marsden
>         Attachments: derby-4053_repro_dont_commit_diff.txt, derby.log, javacore-20090420-1735.txt,
javacore.20090211.123031.4000.0001.txt, suites.All.out
> Running suites.All with IBM 1.5  on alpha - (743198)  I got a hang in the test
run.  The last test to run successfully was xtestNestedSavepoints, but I am not sure exactly
what test caused  the hang.  I took a thread dump which I will attach, which showed network
server up and running but no ClientThread and a ping attempt blocked.
> This hang is very similar to the hang that was seen after the fix attempts for DERBY-1465
but that change was backed out so it is not related to that change.   It could be that the
change for DERBY-1465 just made this highly intermittent problem more likely.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message