[
https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285246#comment-13285246
]
Dag H. Wanvik commented on DERBY-4269:
--------------------------------------
Saw this again:
http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.5/testing/testlog/lin/1343305-suitesAll_diff.txt
A bit more of the stack shows the error cause is
DERBY SQL error: SQLCODE: -1, SQLSTATE: 08004, SQLERRMC: Connection refused to
database
'/export/home/tmp/jagtmp/autoderbyN_derbyall/suitesAll_1/log/db_slave/wombat'
because it is in replication slave mode.
Looking in the master's derby.log I see these two lines:
Tue May 29 04:40:11 CEST 2012 Thread[DRDAConnThread_3,5,main] Cleanup action
starting
ERROR XRE20: Failover performed successfully for database
'/export/home/tmp/jagtmp/autoderbyN_derbyall/suitesAll_1/log/db_master/wombat',
the database has been shutdown.
note the time: 04:40:11. In the client's derby.log I see:
Tue May 29 04:40:12 CEST 2012 Thread[DRDAConnThread_3,5,main] (DATABASE =
/export/home/tmp/jagtmp/autoderbyN_derbyall/suitesAll_1/log/db_slave/wombat),
(DRDAID = {5}), Connection refused to database
'/export/home/tmp/jagtmp/autoderbyN_derbyall/suitesAll_1/log/db_slave/wombat'
because it is in replication slave mode.
Tue May 29 04:40:12 CEST 2012 Thread[DRDAConnThread_3,5,main] Cleanup action
starting
java.sql.SQLException: Connection refused to database
'/export/home/tmp/jagtmp/autoderbyN_derbyall/suitesAll_1/log/db_slave/wombat'
because it is in replication slave mode.
so I wonder if this can be a simple race. In the test, the call to connectPing
happens directly after the call to failOver, and I cannot see any provision for
waiting and/or trying until it succeeds.
> Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
> ----------------------------------------------------------------------------
>
> Key: DERBY-4269
> URL: https://issues.apache.org/jira/browse/DERBY-4269
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.6.1.0
> Environment: OS:
> Microsoft© Windows VistaT Ultimate - 6.0.6001 Service Pack 1 - WindowsNT 0 6
> JVM:
> Sun Microsystems Inc.
> java version "1.4.2_16"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)
> Java HotSpot(TM) Client VM (build 1.4.2_16-b05 mixed mode 32-bit)
> Reporter: Ole Solberg
> Priority: Minor
> Labels: derby_triage10_5_2
>
> Failover did not succeed.
> 2)
> testReplication_Local_3_p6_autocommit_OK(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_3_p6)junit.framework.AssertionFailedError:
> Failover did not succeed.
> at
> org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.connectPing(ReplicationRun.java:270)
> at
> org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_3_p6.derby_3896(ReplicationRun_Local_3_p6.java:200)
> at
> org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_3_p6.testReplication_Local_3_p6_autocommit_OK(ReplicationRun_Local_3_p6.java:86)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:106)
> 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)
> See
> http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/testlog/vista-64/782274-suitesAll_diff.txt
--
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
