Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <893712848.1246888934810.JavaMail.jira@brutus>
Date: Mon, 6 Jul 2009 07:02:14 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4053) suites.All hang with message
 java.net.BindException: Address already in use: NET_Bind in derby.log
In-Reply-To: <751230752.1234391399777.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden commented on DERBY-4053:
---------------------------------------

I think that sounds fine for item #1 in my list above. Perhaps we need a new method in the EngineConnection interface (inLocalTransaction()) to determine the transaction state?  Then we also need to take care of the other two items I listed above so we don't have problems in the future with errors in shutdown causing this kind of difficult to track down problem.


> 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
>         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 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.