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] [Comment Edited] (DERBY-5991) SSLTest timed out waiting for network server to start
Date Wed, 05 Dec 2012 00:08:58 GMT

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

Myrna van Lunteren edited comment on DERBY-5991 at 12/5/12 12:07 AM:
---------------------------------------------------------------------

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.




                
      was (Author: myrna):
    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 endings, 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 pid is getting killed? We need to
somehow gather more info in case this happens again.




                  
> SSLTest timed out waiting for network server to start
> -----------------------------------------------------
>
>                 Key: DERBY-5991
>                 URL: https://issues.apache.org/jira/browse/DERBY-5991
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.8.3.0
>         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)
>            Reporter: Knut Anders Hatlen
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message