db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
Date Fri, 01 Jun 2012 14:49:23 GMT

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

Dag H. Wanvik commented on DERBY-4269:
--------------------------------------

Looking again, I think my first analysis have been wrong, perhaps I looked at the wrong derby.log
files. 

Attaching here 

fail/Embedded_30/ReplicationRun_Local_3_p6/testReplication_Local_3_p6_autocommit_OK/db_slave-derby.log
and
fail/Embedded_30/ReplicationRun_Local_3_p6/testReplication_Local_3_p6_autocommit_OK/db_master-derby.log

which show:

- Master sees successful failover at time Tue May 29 04:37:03 (line 1175 i master log).
- Slave reports "Failover perfomed successfully" at time Tue May 29 04:37:03 (line 28 in slave
log).

The we see two minutes of failed connection attempt in slave log of this type:

  "Connection refused to database '.... db_slave/wombat' because it is in replication slave
mode"

Finally at time Tue May 29 04:39:08, i.e. two minutes later, the slave
and master are shut down:

  "Shutting down Derby engine\nReplication slave role was stopped for database '... /db_slave/wombat'
  "Shutting down Derby engine" (master)

because the two minutes of attempts in connectPing to connect to the
slave, supposedly failed over, bails out (replicationRun, line 379).

So the question becomes, why can't the client connect to the failed
over slave after two minutes? Both the master and the slave have
reported on their logs that failover happened, as far as I understand
the logs.


                
> 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
>            Assignee: Dag H. Wanvik
>            Priority: Minor
>              Labels: derby_triage10_5_2
>         Attachments: DERBY-4269.diff, DERBY-4269.stat
>
>
> 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

       

Mime
View raw message