[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=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.
[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=12765127#action_12765127 ] Myrna van Lunteren commented on DERBY-4326: --- I merged the fix to 10.5, built, then ran suites.All and derbyall on my winvista machine with ibm16 and there were no failures nor errors. > 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.
[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=12764154#action_12764154 ] Mamta A. Satoor commented on DERBY-4326: Committed changes into 823659 in trunk. Will merge into 10.5 codeline next > 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.
[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=12762471#action_12762471 ] Myrna van Lunteren commented on DERBY-4326: --- just to confirm that the T_RawStoreFactory failure is unrelated, I rebuilt without any patches and I get the same failure. The failure is indicating there is still an observer when it expects 0 observers, and that failure we have seen before (e.g. DERBY-3993) > 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.
[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.
[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=12747478#action_12747478 ] Myrna van Lunteren commented on DERBY-4326: --- Forgot to mention, that I did get a full-no-failures-run of suites.All on my vista machine - but I can no longer remember if this was with ibm 16 and -Xmx1024M -Xms1024M or sun jdk 1.6 with -XX:MaxPermSize=256M. I'm guessing it was the ibm 1.6. > 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.
[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=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.
[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=12739759#action_12739759
]
Kathey Marsden commented on DERBY-4326:
---
I did not apply but looked briefly at Mamta's patch. I think in the shutdown
case we should not log the interrupt exception as it is an expected part of the
shutdown.
In the code:
+if (parent.getShutdown()) {
+ clientSocket.close();
+ return;
}
We should probably also check that clientSocket != null.
Otherwise it looks ok except for some comment cleanup.
> 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.
[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=12739224#action_12739224 ] Myrna van Lunteren commented on DERBY-4326: --- As an aside...I thought I'd try to run suites.All with junit.textui.TestRunner with only embedded. First I tried without derbynet.jar and derbyclient.jar in my classpath, but they still got picked up by sysinfo, so I then removed them physically from the dir where the other derby jars lived. This resulted in this error: Failed to invoke suite():java.lang.NoClassDefFoundError: org.apache.derby.jdbc.ClientConnectionPoolDataSource So apparently, there's no way to do this... > 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 > > > 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.
[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=12739026#action_12739026 ] Myrna van Lunteren commented on DERBY-4326: --- The last successful run on this machine was with 10.3 and ibm's 1.4.2.(!) The test has undergone some changes since that time... grabbed this issue while I will do the experiments suggested by Kathey and try out Mamta's patch. I did finally try this test on this machine with Sun's 1.6 JDK and the test had been going for up to 1 hour - (on my windows XP the networkserver fixture testNetworkServerSecurityMechanism takes about 2703 ms). So, looks like the same problem and it doesn't look like a jvm 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 > Attachments: DERBY4326_notForCommit_patch1_diff.txt, > javacore.20090728.095131.5196.0001.txt, javacore.20090728.114939.5640.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: 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.
[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=12738506#action_12738506 ] Tiago R. Espinha commented on DERBY-4326: - I might be experiencing this same issue under Ubuntu with Sun's 1.6 JDK. My NSSecurityMechanismTest is taking around 22 minutes to run which seems to be a lot. > 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 > Attachments: DERBY4326_notForCommit_patch1_diff.txt, > javacore.20090728.095131.5196.0001.txt, javacore.20090728.114939.5640.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: 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.
[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=12736756#action_12736756 ] Myrna van Lunteren commented on DERBY-4326: --- re 1) I didn't run deryball/suites.All on this machine for 10.5.1.1 testing. I'll try to figure out what combination the last successful testing cycle on this machine used. > 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 > Attachments: javacore.20090728.095131.5196.0001.txt, > javacore.20090728.114939.5640.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: 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.
[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=12736751#action_12736751 ] Kathey Marsden commented on DERBY-4326: --- While there is clearly a Network Server bug in its handling of the exception, I wonder if the setKeepAlive() error is a JVM regression. Maybe that socket is getting cleaned up too early on the client with the new service release. Myrna could you try two things: 1) Try with the jdk version you used with 10.5.1.1 testing? 2) Try with the jvm where you are getting the hang with the following test change. Instead of: DriverManager.getConnection(dbUrl).close(); do Conection conn = getConnection(dbUrl). conn.close(); > 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 > Attachments: javacore.20090728.095131.5196.0001.txt, > javacore.20090728.114939.5640.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: 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.
[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=12736721#action_12736721 ] Myrna van Lunteren commented on DERBY-4326: --- I also got the same hang with 10.5.1.1. As others have tested on winvista successfully, I'm not complaining about this much, but it does prevent me from running the test suite. For now, I'll see if there's something peculiar with the machine. > 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 > Attachments: javacore.20090728.095131.5196.0001.txt, > javacore.20090728.114939.5640.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: 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.
[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=12736355#action_12736355
]
Kathey Marsden commented on DERBY-4326:
---
The thread dump in the javacore reveals that this exception causes our
ClientThread to go away, but the server stays up blocked in blockingStart() but
has no ClientThread to handle new requests. I think typically the error
Connection reset by peer would happen if the client closed the socket. Even
though the client does do a quick close:
DriverManager.getConnection(dbUrl).close();
I don't think the getConnection() should return until we are well through this
setKeepAlive code. Regardless of why it happened I don't think such an error
should cause loss of the ClientThread. Currently we have:
clientSocket.setKeepAlive(parent.getKeepAlive());
// Set time out: Stops DDMReader.fill() from
// waiting indefinitely when timeSlice is set.
if (timeSlice > 0)
clientSocket.setSoTimeout(timeSlice);
//create a new Session for this socket
parent.addSession(clientSocket);
} catch (PrivilegedActionException e) {
// Just throw the underlying exception
throw e.getException();
} // end inner try/catch block
> 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
> Attachments: javacore.20090728.095131.5196.0001.txt,
> javacore.20090728.114939.5640.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: 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.
[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=12736349#action_12736349 ] Myrna van Lunteren commented on DERBY-4326: --- In the run of the test by itself, the socket reset appears to end up in logs/serverConsoleOutput.log: 2009-07-28 17:04:06.967 GMT : Apache Derby Network Server - 10.5.2.0 - (794445) started and ready to accept connections on port 1527 2009-07-28 17:04:37.169 GMT : Connection reset by peer: setsockopt java.net.SocketException: Connection reset by peer: setsockopt 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) > 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 > Attachments: javacore.20090728.095131.5196.0001.txt, > javacore.20090728.114939.5640.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: 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.
