Derby
  1. Derby
  2. DERBY-5991

SSLTest timed out waiting for network server to start

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 10.8.3.0
    • Fix Version/s: None
    • Component/s: Test
    • Labels:
      None
    • Environment:
      SUSE Linux Enterprise Server 10 (x86_64)
      java version "1.6.0_24"
      Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
      Java HotSpot(TM) Server VM (build 19.1-b02, mixed mode)
    • Bug behavior facts:
      Regression Test Failure

      Description

      Seen when testing the 10.8.3.0 RC:

      http://dbtg.foundry.sun.com/derby/test/10.8.3.0_RC/logs/jvm1.6/sles/suitesAll/report.txt

      There was 1 failure:
      1) testSSLBasicDSConnect(org.apache.derbyTesting.functionTests.tests.derbynet.SSLTest)junit.framework.AssertionFailedError: Timed out waiting for network server to start:Spawned SpawnedNetworkServer exitCode=143
      STDOUT:
      Sat Nov 10 04:15:01 CET 2012 : Security manager installed using the Basic server security policy.

      at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:210)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
      at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
      at junit.extensions.TestSetup.run(TestSetup.java:25)
      at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
      at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
      at junit.extensions.TestSetup.run(TestSetup.java:25)

      There was no fail directory containing more detailed logs.

        Issue Links

          Activity

          Hide
          Myrna van Lunteren added a comment - - edited

          We have a report of this error occurring with 10.8.2.3 (built at revision 1326460) with an ibm jvm.
          I think the slightly earlier version explains the different line numbers, it looks like a similar problem otherwise...

          The reported error happens in 6 different tests:
          1) JMXTest:client
          2) ManagementMBeanTest:client
          3) InactiveManagementMBeanTest:client
          4) VersionMBeanTest:client
          5) JDBCMBeanTest:client
          6) NetworkServerMBeanTest:client

          The stack trace is like this (this one is from JMXTest, but the stack traces are the same for each test):
          1) JMXTest:clientjunit.framework.AssertionFailedError: Timed out waiting for network server to start:Spawned SpawnedNetworkServer exitCode=143
          STDOUT:
          Wed Nov 28 11:22:23 GMT 2012 : Security manager installed using the Basic server security policy.

          at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:210)
          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.java: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)

          A quick search shows that exit code 143 "corresponds to SIGTERM, which is the signal sent by default when you run kill <pid>".

          So, perhaps there is a hang of some sort, and the server process is getting killed? We need to somehow gather more info in case this happens again.

          Show
          Myrna van Lunteren added a comment - - edited We have a report of this error occurring with 10.8.2.3 (built at revision 1326460) with an ibm jvm. I think the slightly earlier version explains the different line numbers, it looks like a similar problem otherwise... The reported error happens in 6 different tests: 1) JMXTest:client 2) ManagementMBeanTest:client 3) InactiveManagementMBeanTest:client 4) VersionMBeanTest:client 5) JDBCMBeanTest:client 6) NetworkServerMBeanTest:client The stack trace is like this (this one is from JMXTest, but the stack traces are the same for each test): 1) JMXTest:clientjunit.framework.AssertionFailedError: Timed out waiting for network server to start:Spawned SpawnedNetworkServer exitCode=143 STDOUT: Wed Nov 28 11:22:23 GMT 2012 : Security manager installed using the Basic server security policy. at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:210) 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.java: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) A quick search shows that exit code 143 "corresponds to SIGTERM, which is the signal sent by default when you run kill <pid>". So, perhaps there is a hang of some sort, and the server process is getting killed? We need to somehow gather more info in case this happens again.
          Hide
          Myrna van Lunteren added a comment -

          I checked past results of my test runs (at IBM) and do not see an occurrence of this test failure in 2014. I'm marking it as cannot reproduce at this time.

          Show
          Myrna van Lunteren added a comment - I checked past results of my test runs (at IBM) and do not see an occurrence of this test failure in 2014. I'm marking it as cannot reproduce at this time.

            People

            • Assignee:
              Unassigned
              Reporter:
              Knut Anders Hatlen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development