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] Commented: (DERBY-4326) hang on winvista with IBM 1.6 SR5 in NSSecurityMechanismTest
Date Wed, 05 Aug 2009 22:19:14 GMT

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

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

With a build with mamta's patch applied I ran derbyall and suites.All on my winvista box and
on my XP.
On winvista, this time I ran with sun's jdk 1.6 but forgot to set -XX:MaxPermSize=128M for
suites.All and ran out of memory during the upgrade tests...
However, I did see a couple of java.net.socketExceptions logged, in the following tests:
- derbyall: derbyNetAutoStart. (both XP & my winvista).
The diff is like this: 
--------------------
1a2
> java.net.SocketException: socket closed
2a4
> java.net.SocketException: socket closed
-------------------
As we're now logging SocketExceptions, I think this can be expected. If indeed it is expected,
we can filter this out again using a _sed.properties file.
- suites.All: 
on both XP & netvista: 
  - DerbyNetNewServer. (test passed anyway), 
  - ttestSetPortPriority (4x. test passed anyway).
The difference is in fixture ttestNetworkServerSecurityMechanism; both have 3 identical stack
traces, but the first one is different on my winvista box vs. XP:
winvista:
----------------------
testNetworkServerSecurityMechanism java.net.SocketException: Connection reset by peer: setsockopt
	at java.net.PlainSocketImpl.socketSetOption(Native Method)
	at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:264)
	at java.net.Socket.setKeepAlive(Socket.java:1160)
	at org.apache.derby.impl.drda.ClientThread.run(ClientThread.java:79)
----------------------
xp:
----------------------
testNetworkServerSecurityMechanism java.net.SocketException: socket closed
	at java.net.PlainSocketImpl.socketAccept(Native Method)
	at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:414)
	at java.net.ServerSocket.implAccept(ServerSocket.java:464)
	at java.net.ServerSocket.accept(ServerSocket.java:432)
	at org.apache.derby.impl.drda.ClientThread$1.run(ClientThread.java:67)
	at java.security.AccessController.doPrivileged(AccessController.java:251)
	at org.apache.derby.impl.drda.ClientThread.run(ClientThread.java:62)
----------------------
Even so, it now looks as though this test now passes on both OSs.


> 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