You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2009/10/06 02:23:31 UTC

[jira] Commented: (DERBY-4326) hang on winvista with IBM 1.6 SR5 in NSSecurityMechanismTest

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

Myrna van Lunteren commented on DERBY-4326:
-------------------------------------------

I tested patch2 on my winvista machine and ran into no failures except for unit/T_RawStoreFactory.unit.

I don't think that failure is related, although it appears consistent...

I have 1 nit: it seems the patch has 1 unnecessary white-character change.
 +1 for commit from me.

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