[
https://issues.apache.org/jira/browse/DERBY-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4201:
--------------------------------------
Attachment: repro.diff
Using the sleep-repro.diff patch attached to DERBY-5194, I'm able to reproduce
the failure reported here too. Not when running SecureServerTest alone, but
when running as part of a suite so that there is a network server from an
earlier test case that's only partially shut down when SecureServerTest starts.
See the attached repro.diff that combines the changes in the DERBY-5194 repro
patch with adding NetHarnessJavaTest at the beginning of the test suite
returned by SecureServerTest.suite(). With that patch, SecureServerTest fails
when running alone.
The suspected cause of this intermittent failure is that the server used in an
earlier test case might not be fully shut down when a new test case starts. The
server shutdown command doesn't return until the server has stopped responding
to ping. That works most of the time, but since it stops responding to ping
before it actually releases the server socket, there is a possibility that the
new server is started too early and fails to start listening on the port.
> SecureServerTest AssertionFailedError: Timed out waiting for network server
> to start
> ------------------------------------------------------------------------------------
>
> Key: DERBY-4201
> URL: https://issues.apache.org/jira/browse/DERBY-4201
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.5.2.0, 10.7.1.1, 10.8.2.2
> Environment: java version "1.4.2"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
> Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20061124 (SR7) (JIT
> enabled: jitc))
> SUSE linux running on vmware.
> Reporter: Kathey Marsden
> Priority: Minor
> Labels: derby_triage10_8
> Attachments: repro.diff
>
>
> I saw this failure in the nightly run on 4/27 on the 10.5 branch - 10.5.1.2
> - (769232). I have not seen it in previous runs on the same machine. There
> were actually two failures in the test. I think the second one failed because
> of the first so am not reporting a separate issue for that.
> There were 2 failures:
> 1) SecureServerTest( Opened = false, Authenticated= false,
> CustomDerbyProperties= null, WildCardHost= null
> )junit.framework.AssertionFailedError: Timed out waiting for network server
> to start:Spawned SpawnedNetworkServer exitCode=0
> at
> org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:200)
> 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)
> 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)
> 2) SecureServerTest( Opened = false, Authenticated= false,
> CustomDerbyProperties=
> functionTests/tests/derbynet/SecureServerTest.derby.properties, WildCardHost=
> null )junit.framework.AssertionFailedError: directory trace does not exist
> at
> org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.setTraceDirectory(SecureServerTest.java:386)
> at
> org.apache.derbyTesting.functionTests.tests.derbynet.SecureServerTest.testServerStartup(SecureServerTest.java:358)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled
> Code))
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)
> 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
> 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)
> 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)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
