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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/07/12 21:05:31 UTC

[jira] Commented: (DERBY-3777) SecureServerTest, SSLTest are failed on Zos with exit code 143 starting network server

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

Kathey Marsden commented on DERBY-3777:
---------------------------------------

extending  WAIT_TIME in NetworkServerTestSetup to 60000 from 10000 seems to correct this failure.  Perhaps a smaller number would work, I haven't experimented too much.  It seems to me there was some discussion about this number and the importance of keeping it low.   The comments still say.

    /** Setting maximum wait time to 300 seconds.   For some systems it looks
     *  like restarting a server to listen on the same port is blocked waiting
     *  for a system specific interval.  This number looks to be something
     *  like 240 seconds on XP.  Waiting shorter than this time causes
     *  intermittent failures on a laptop running XP with a software firewall
     *  and a VPN.  Increasing the wait time should not adversely affect those
     *  systems with fast port turnaround as the actual code loops for 
     *  SLEEP_TIME intervals, so should never see WAIT_TIME.
     */



> SecureServerTest, SSLTest are failed on Zos with exit code 143 starting network server
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-3777
>                 URL: https://issues.apache.org/jira/browse/DERBY-3777
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server, Test
>    Affects Versions: 10.4.1.4
>         Environment: 9) 
> testSSLBasicDSPlainConnect(org.apache.derbyTesting.functionTests
> .tests.derbynet.SSLTest)junit.framework.AssertionFailedError: 
> Timed out waiting for network server to start:Spawned 
> SpawnedNetworkServer exitCode=143
> 	at 
> org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(Netwo
> rkServerTestSetup.java:203)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> 	at 
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.ja
> va:57)
> 	at 
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> 	at 
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> 	at 
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> 	at 
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
>            Reporter: Kathey Marsden
>            Priority: Minor
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.