[
https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602613#action_12602613
]
V.Narayanan commented on DERBY-3709:
------------------------------------
I remember while working on 3617 thinking that this might be because the
tests call failover immediately after a start master, this results in failover
being called before replication can be booted completely. I will take a closer
look at this over the weekend, unless someone beats me to it.
> Exception printed by replication test: Could not perform operation because
> the database is not in replication master mode.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3709
> URL: https://issues.apache.org/jira/browse/DERBY-3709
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure, Replication
> Affects Versions: 10.5.0.0
> Environment: Java Version: 1.6.0_04
> Java Vendor: Sun Microsystems Inc.
> OS name: SunOS
> OS architecture: x86
> OS version: 5.10
> Reporter: Knut Anders Hatlen
>
> I saw the following exception printed when I ran suites.All on trunk
> (revision 663064). None of the tests failed.
> java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE07,
> SQLERRMC: Could not perform operation because the database is not in
> replication master mode.
> at
> org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:96)
> at
> org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362)
> at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:149)
> at java.sql.DriverManager.getConnection(DriverManager.java:582)
> at java.sql.DriverManager.getConnection(DriverManager.java:207)
> at
> org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver_direct(ReplicationRun.java:1286)
> at
> org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.failOver(ReplicationRun.java:1220)
> at
> org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local.testReplication_Local(ReplicationRun_Local.java:148)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:164)
> at junit.framework.TestCase.runBare(TestCase.java:130)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:104)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:120)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at junit.textui.TestRunner.doRun(TestRunner.java:121)
> at junit.textui.TestRunner.start(TestRunner.java:185)
> at junit.textui.TestRunner.main(TestRunner.java:143)
> Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: SQLCODE:
> -1, SQLSTATE: XRE07, SQLERRMC: Could not perform operation because the
> database is not in replication master mode.
> at
> org.apache.derby.client.am.Connection.completeSqlca(Connection.java:2068)
> at
> org.apache.derby.client.net.NetConnectionReply.parseRdbAccessFailed(NetConnectionReply.java:537)
> at
> org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(NetConnectionReply.java:430)
> at
> org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(NetConnectionReply.java:294)
> at
> org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(NetConnectionReply.java:121)
> at
> org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(NetConnection.java:831)
> at
> org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(NetConnection.java:755)
> at
> org.apache.derby.client.net.NetConnection.flowUSRIDONLconnect(NetConnection.java:588)
> at
> org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:395)
> at
> org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:219)
> at
> org.apache.derby.client.net.NetConnection40.<init>(NetConnection40.java:77)
> at
> org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(ClientJDBCObjectFactoryImpl40.java:269)
> at org.apache.derby.jdbc.ClientDriver.connect(ClientDriver.java:140)
> ... 31 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
