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] Updated: (DERBY-4053) suites.All hang with message java.net.BindException: Address already in use: NET_Bind in derby.log
Date Wed, 01 Jul 2009 20:57:47 GMT

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

Kathey Marsden updated DERBY-4053:

    Urgency: Urgent

With the DERBY-3319 fix I think this is much more likely to occur at a user site.  Marking
Urgent to try to get it into the 10.5.2 release.

I actually would have thought this would be a regression associated with 10.5 after DERBY-3319,
but Myrna has reported the problem on 10.4 as well.  If it is a regression, it should probably
move to BLOCKER.
Thank you Mamta for tracking down this issue.

I see three  parts to the fix:
1) Do a better job of cleaning up XA Connections.  For local transactions we can rollback,
but we need to be more careful to do the right thing if a global transaction is in progress.
 We cannot simply rollback a prepared transaction.

2) Make sure an exception during shutdown processing does not prevent the remaining shutdown
tasks, like closing the server socket from occurring.

3) Make sure any exceptions that occur in shutdown processing are reported to the console.

> 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, Test
>    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