[
https://issues.apache.org/jira/browse/DERBY-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719001#action_12719001
]
Kathey Marsden commented on DERBY-4053:
---------------------------------------
My gut instinct is that this is some sort of shutdown timing problem with all
the server side cleanup that starts about line 807 in NetworkServerControlImpl
or perhaps a problem with bring it up in the first place. The key thing I
notice is there is no ClientThread running which normally accepts new requests,
but it does not seem the server socket was closed because there is one
DRDAConnThread that is blocked on a read and one ping thread blocked on read
that would terminate if the server.socket were closed.
It would be interesting to trace when this occurs.
1) calls to shutdown and start
2) Entry into the for (;;) loop in ClientThread
3) returns out of the ClientThread loop
4) Remove the if(!parent.getShudown()) in this code so we always print the
IOException if it occurs. Perhaps there is an exception we are not seeing.
if (!parent.getShutdown()) {
parent.consoleExceptionPrintTrace(ioe);
if (clientSocket != null)
clientSocket.close();
}
> 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: 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.
