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] Commented: (DERBY-4326) hang on winvista with IBM 1.6 SR5 in NSSecurityMechanismTest
Date Tue, 13 Oct 2009 17:25:31 GMT

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

Mamta A. Satoor commented on DERBY-4326:
----------------------------------------

Thanks for running the tests on winvista, Myrna. both derbyall and junit suite ran fine on
windows xp machine too with IBM 16. Have committed the merged changes into 10.5 codeline using
revision 824850. Will go ahead and resolve the issue

> 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: 10.5.2.0
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>             Fix For: 10.6.0.0
>
>         Attachments: DERBY4326_notForCommit_patch1_diff.txt, DERBY4326_printExceptions_patch2_diff.txt,
javacore.20090728.095131.5196.0001.txt, javacore.20090728.114939.5640.0001.txt, mamtapatch1result.jar,
run.out
>
>
> 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:
setsockopt
> 	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.


Mime
View raw message