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] Commented: (DERBY-4053) suites.All hang with message java.net.BindException: Address already in use: NET_Bind in derby.log
Date Tue, 14 Jul 2009 21:59:14 GMT

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

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

With the diag patch, XATest, and the change to check unordered results for checkXATransactionView,
and running jdbcapi._Suite  I can reproduce the error on shutdown described here: https://issues.apache.org/jira/browse/DERBY-4155?focusedCommentId=12731086&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12731086

followed later by an InvalidReply and the hang with bind exception in the derby.log
 


I also see the following issue shutting down  which does not cause problems restarting the
server because the JMX cleanup comes after serverSocket.close()
testSystemShutdown used 406 ms java.lang.NullPointerException
        at org.apache.derby.impl.services.jmx.JMXManagementService.unregisterMBean(JMXManagementService.java:286)
        at org.apache.derby.impl.services.jmx.JMXManagementService.unregisterMBean(JMXManagementService.java:277)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart(NetworkServerControlImpl.java:864)
        at sun.reflect.GeneratedMethodAccessor596.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:599)
        at org.apache.derby.iapi.jdbc.DRDAServerStarter.run(DRDAServerStarter.java:236)
        at java.lang.Thread.run(Thread.java:735)
.
testPoolDS used 5234 ms .


In general ur failure to report and handle errors on shutdown has been masking other issues.

I think we should proceed as follows:
1) Change the title of DERBY-4053 to: Network Server does not rollback local transactions
on XAConnections  on shutdown causing hang on restart with message java.net.BindException:
Address already in use: NET_Bind in derby.log 

2) File two new issues described above.

3)Continue work on DERBY-4304 to expose additonal issues and eliminate the bind error on other
circumstances.
 
4) Add the unordered result set check as part of the DERBY-4155


I don't think these tasks should hold up 10.5.2



> 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_diag_diff.txt, 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