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-4326) hang on winvista with IBM 1.6 SR5 in NSSecurityMechanismTest
Date Mon, 03 Aug 2009 19:07:14 GMT

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

Mamta A. Satoor updated DERBY-4326:

    Attachment: DERBY4326_notForCommit_patch1_diff.txt

Attaching a patch DERBY4326_notForCommit_patch1_diff.txt. This patch is not ready for commit.

I changed the code so that we don't simply return from the ClientThread when we run into InterruptedException
or IOException. For InterruptedException, after putting something into the log about the exception,
I check if the server has been shutdown and if so, then we should leave the ClientThread otherwise,
we simply close the client socket. For IOException, I made changes to log it and then close
the client socket and resume the loop of waiting for the next client request. Running derbyall
with these changes made derbynet/DerbyNetAutoStart.java to fail. It appears that the test
get SocketException which is a kind of IOException which I guess you can get if the server
is down. I am not 100% about the cause but just printing and closing client socket for a SocketException
is making the test to fail. I am going to have to stop working on this jira for a while until
I look at DERBY-4331.

> hang on winvista with IBM 1.6 SR5 in NSSecurityMechanismTest
> ------------------------------------------------------------
>                 Key: DERBY-4326
>                 URL: https://issues.apache.org/jira/browse/DERBY-4326
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions:
>            Reporter: Myrna van Lunteren
>         Attachments: DERBY4326_notForCommit_patch1_diff.txt, javacore.20090728.095131.5196.0001.txt,
> This is stopping my platform testing on winvista with ibm 1.6 SR5.
> During the initial run of suites.All, I got:
> --------------------------------
> 		testNetworkServerSecurityMechanism java.net.SocketException: Connection reset by peer:
> 	at java.net.PlainSocketImpl.socketSetOption(Native Method)
> 	at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:283)
> 	at java.net.Socket.setKeepAlive(Socket.java:1171)
> 	at org.apache.derby.impl.drda.ClientThread.run(Unknown Source)
> --------------------------------
> Rerunning suites.All gave the same error.
> There is only 1 java process active & hanging.
> Running just the test itself also results in a hang but there was (so far - it's been
sitting unchanged for 4 hours) java.net.SocketException.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message