db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (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, 10 Jul 2009 21:53:14 GMT

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

Mamta A. Satoor updated DERBY-4053:
-----------------------------------

    Attachment: DERBY4053_patch3_stat_July102009.txt
                DERBY4053_patch3_diff_July102009.txt

Posting an updated patch DERBY4053_patch3_diff_July102009.txt. It has changes suggested by
Kathey on the previous patch. I will run the entire junit suite and derbyall. This is on trunk.

> 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: 10.5.1.1
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>         Attachments: derby-4053_repro_dont_commit_diff.txt, derby.log, DERBY4053_patch1_diff_July092009.txt,
DERBY4053_patch2_diff_July102009.txt, DERBY4053_patch2_stat_July102009.txt, DERBY4053_patch3_diff_July102009.txt,
DERBY4053_patch3_stat_July102009.txt, javacore-20090420-1735.txt, javacore.20090211.123031.4000.0001.txt,
mamtaDerby4053.java, suites.All.out
>
>
> Running suites.All with IBM 1.5  on 10.5.0.0 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.


Mime
View raw message