Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <392312840.1240598610301.JavaMail.jira@brutus>
Date: Fri, 24 Apr 2009 11:43:30 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-4186) After failover, test fails when it
 succeeds in connecting early to failed over slave
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

After failover, test fails when it succeeds in connecting early to failed over slave
------------------------------------------------------------------------------------

                 Key: DERBY-4186
                 URL: https://issues.apache.org/jira/browse/DERBY-4186
             Project: Derby
          Issue Type: Bug
          Components: Replication
            Reporter: Dag H. Wanvik


Occasionally I see this error in ReplicationRun_Local_3_p3:

1) testReplication_Local_3_p3_StateNegativeTests(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_3_p3)junit.framework.AssertionFailedError: Expected SQLState'08004', but got connection!
	at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.waitForSQLState(ReplicationRun.java:332)
	at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local_3_p3.testReplication_Local_3_p3_StateNegativeTests(ReplicationRun_Local_3_p3.java:170)
	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:105)
	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)

In the code, after a fail-over given to the master:
the tests expects to see CANNOT_CONNECT_TO_DB_IN_SLAVE_MODE (08004.C.7), which will only succeed if
the tests gets to try to connect before the failover has started. This seems wrong. If the failover has completed, it should expect a successful
connect (which boots the database, btw, since its shut down after auccessful failover).

Quote from code:

waitForSQLState("08004", 100L, 20, // 08004.C.7 - CANNOT_CONNECT_TO_DB_IN_SLAVE_MODE
                slaveDatabasePath + FS + slaveDbSubPath + FS + replicatedDb,
                slaveServerHost, slaveServerPort); // _failOver above fails...

There is a race between the failover on the slave and the test here I think.


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