db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4564) Replication tests do not pick up derby.tests.networkServerStartTimeout setting
Date Thu, 25 Feb 2010 00:09:27 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kathey Marsden updated DERBY-4564:

    Attachment: derby-4564_throwfinalexception_diff.txt

I noticed the exception printed to the console has happened before in the nightlies for this
test, e.g.
The test actually prints out the stack trace and then creates and throws a new exception if
the start time expires and this is the only place I see it printing out an exception.  I don't
understand though why the test would not fail if this happened.    This is the relevant code
from ReplicationRun

 String msg = "Could not ping in " 
                + iterations + " * " + PINGSERVER_SLEEP_TIME_MILLIS + "ms.: "
                + finalException.getMessage();
        util.DEBUG( msg );
        finalException.printStackTrace(); // REMOVE?
        throw new Exception(msg);

In the attached patch I changed this code to just throw finalException instead of creating
a new exception and verified the test does fail with a setting of derby.tests.networkServerStartTimeout=500
and doesn't with it set to 5000 on my machine.

I'll do one more full test run and then check in this change.



> Replication tests do not pick up derby.tests.networkServerStartTimeout setting
> ------------------------------------------------------------------------------
>                 Key: DERBY-4564
>                 URL: https://issues.apache.org/jira/browse/DERBY-4564
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>         Attachments: derby-4564_diff.txt, derby-4564_throwfinalexception_diff.txt
> The property derby.tests.networkServerStartTimeout is sometimes used with testing to
extend the wait for network server when JVM options are specified that make the start very
slow, for example, for IBM JVM testing, -Xnoquickstart  is used for some runs.  The replication
tests do not seem to pick up this property.  Even when set to 90000 the tests wait only for
75 seconds.
> testReplication_Local_StateTest_part1_1(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1_1)java.lang.Exception:
Could not ping in 150 * 500ms.: DRDA_NoIO.S
> :Could not connect to Derby Network Server on host, port 1527: Connection refused
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.ping(ReplicationRun.java:2804)
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.pingServer(ReplicationRun.java:2776)
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.startServer(ReplicationRun.java:2453)
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_StateTest_part1_1.testReplication_Local_StateTest_part1_1(ReplicationRun_Local_StateTest_part1_1.java:86)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:63)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:109)
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.runBare(ReplicationRun.java:199)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>         at junit.extensions.TestSetup.run(TestSetup.java:16)

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

View raw message