db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4326) hang on winvista with IBM 1.6 SR5 in NSSecurityMechanismTest
Date Wed, 05 Aug 2009 04:25:14 GMT

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

Myrna van Lunteren updated DERBY-4326:
--------------------------------------

    Attachment: mamtapatch1result.jar

Attaching a jar-ed up of the results directory (minus system\wombat) from running with mamta's
not-for-commit patch (ran with modified sane trunk jars, and ibm1.6). The test fails, but
at least the hang is gone.
Apparently, judging from derby.log I'm getting 'invalid authentication' - or is that expected
with this test?

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