Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <587017819.141961268082927478.JavaMail.jira@brutus.apache.org>
Date: Mon, 8 Mar 2010 21:15:27 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4564) Replication tests do not pick up
 derby.tests.networkServerStartTimeout setting
In-Reply-To: <823163256.465911266947428311.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-4564?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-4564:
----------------------------------

    Attachment: derby-4564_useseconds_diff.txt

Here is the updated patch that uses seconds and not milliseconds.

> Replication tests do not pick up derby.tests.networkServerStartTimeout se=
tting
> -------------------------------------------------------------------------=
-----
>
>                 Key: DERBY-4564
>                 URL: https://issues.apache.org/jira/browse/DERBY-4564
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.5.3.0
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>         Attachments: derby-4564_diff.txt, derby-4564_throwfinalexception_=
diff.txt, derby-4564_useseconds_diff.txt
>
>
> The property derby.tests.networkServerStartTimeout is sometimes used with=
 testing to extend the wait for network server when JVM options are specifi=
ed that make the start very slow, for example, for IBM JVM testing, -Xnoqui=
ckstart=C2=A0 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 s=
econds.
> testReplication_Local_StateTest_part1_1(org.apache.derbyTesting.functionT=
ests.tests.replicationTests.ReplicationRun_Local_StateTest_part1_1)java.lan=
g.Exception: Could not ping in 150 * 500ms.: DRDA_NoIO.S
> :Could not connect to Derby Network Server on host 127.0.0.1, port 1527: =
Connection refused
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.R=
eplicationRun.ping(ReplicationRun.java:2804)
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.R=
eplicationRun.pingServer(ReplicationRun.java:2776)
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.R=
eplicationRun.startServer(ReplicationRun.java:2453)
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.R=
eplicationRun_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(NativeMethodAccess=
orImpl.java:63)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth=
odAccessorImpl.java:43)
>         at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCas=
e.java:109)
>         at org.apache.derbyTesting.functionTests.tests.replicationTests.R=
eplicationRun.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)

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