[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406634#comment-13406634 ] Dag H. Wanvik commented on DERBY-4269: -- Backported fix-ignored-runtime-exceptions-b to 10.8 at svn 1357343. Will close issue when DERBY-5830 is backported, too. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Fix For: 10.7.1.4 > > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, > fix-ignored-runtime-exceptions-a.diff, fix-ignored-runtime-exceptions-b.diff, > fix-ignored-runtime-exceptions-instr.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406595#comment-13406595 ] Dag H. Wanvik commented on DERBY-4269: -- Backported fix-ignored-runtime-exceptions-b to 10.9 at svn 1357310. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Fix For: 10.7.1.4 > > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, > fix-ignored-runtime-exceptions-a.diff, fix-ignored-runtime-exceptions-b.diff, > fix-ignored-runtime-exceptions-instr.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405946#comment-13405946 ] Dag H. Wanvik commented on DERBY-4269: -- Committed fix-ignored-runtime-exceptions-b as svn 1356766, resolving. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, > fix-ignored-runtime-exceptions-a.diff, fix-ignored-runtime-exceptions-b.diff, > fix-ignored-runtime-exceptions-instr.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405710#comment-13405710 ] Knut Anders Hatlen commented on DERBY-4269: --- The patch looks fine to me. Minor nit: Since SlaveDatabaseBootThread is a non-static inner class of SlaveDatabase, the fields and methods of the parent SlaveDatabase instance can be accessed directly from the SlaveDatabaseBootThread instance. So it should be possible to read the value of the dbname field in SlaveDatabaseBootThread.run() without introducing an accessor method and a new field. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, > fix-ignored-runtime-exceptions-a.diff, > fix-ignored-runtime-exceptions-instr.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[
https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401339#comment-13401339
]
Dag H. Wanvik commented on DERBY-4269:
--
I instrumented all calls to propertyNames while in the slave boot code running
ReplicationRun_Local_3_p6-sb1. It turns out the only place where
DoubleProperties#propertyNames
is called is here in BaseMonitor#getImplementations (cf also the original
backtrace above):
nextModule:
for (Enumeration e = moduleList.propertyNames(); e.hasMoreElements(); ) {
String key = (String) e.nextElement();
// module tagged name in the modules.properties file.
// used as the tag for dependent properties.
String tag;
// Dynamically loaded code is defined by a property of
// the form:
// derby.module.=
// or
// derby.subSubProtocol.=
if (key.startsWith(Property.MODULE_PREFIX)) {
tag = key.substring(Property.MODULE_PREFIX.length());
} else if (key.startsWith(Property.SUB_SUB_PROTOCOL_PREFIX)) {
tag = key.substring(Property.MODULE_PREFIX.length());
} else {
continue nextModule;
}
This means that all properties that do not start with MODULE_PREFIX
("derby.module.") or SUB_SUB_PROTOCOL_PREFIX ("derby.subProtocol.") are
skipped. None of those are legal URL properties, and could t
hus stem from the contested info properties object acclocated int
EmbedConnection.
I therefore believe we can avoid doing the explicit synchronization when
DERBY-5830 goes in.
I'll run the instrumented versions on all the replication tests for good
measure before I conclude, though.
> 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0,
> 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2
> 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
> Labels: derby_triage10_5_2
> Attachments: 4269-client-jstack.txt, 4269-master.txt,
> 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff,
> DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log,
> db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff,
> derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status,
> derby-4269-explicit-synch.diff, derby-4269-typo.diff, keys-only.diff
>
>
> 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400431#comment-13400431 ] Dag H. Wanvik commented on DERBY-4269: -- Thanks for filing DERBY-5830. I added some code in my patch to log errors to derby.log if SlaveDatabaseBootThread fails in 3). How graceful it is is another matter, but we should at least learn what the error is. Under normal operation the boot should not fail, one would hope. As for checking usages, I have already made a Derby specific version of Properties to find the original race, so I can use that for tracking down usages of getProperties. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399922#comment-13399922 ] Knut Anders Hatlen commented on DERBY-4269: --- I logged DERBY-5830 for fixing DoubleProperties.propertyNames(), so we can separate that issue from any changes that need to be done to the slave boot code. So far, I think we have discussed three areas that potentially need fixing: 1) Lack of thread-safety in DoubleProperties - now handled in DERBY-5830. 2) Boot code not prepared for being multi-threaded. The fix for (1) may be sufficient, but there may be other hidden bugs caused by the slave boot process breaking assumptions made in existing code. 3) SlaveDatabaseBootThread silently ignores runtime exceptions and leaves the process hanging. The fix for (1) may remove the cause for the hang we've seen, but SlaveDatabaseBootThread still doesn't handle unexpected failures gracefully. I'm not sure what's the best way to approach (2). It's difficult to see from the code exactly which places the Properties instance in question is used. Maybe we could make EmbedConnection.filterProperties() return an instrumented sub-class of Properties that logs the stack trace of all calls to getProperty(), run some subset of the regression tests, and then manually inspect the call sites to see if they would handle the disappearance of a property? > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399808#comment-13399808 ] Dag H. Wanvik commented on DERBY-4269: -- Knut: Part of the problem here is that the old (i.e. pre-replication code) might not be prepared for thread concurrency on the Properties object, viz the fact the buggy overload wasn't detected before. Still, I am tempted to go for your solution (modulo the weakness you pointed out) to get rid of the ugly explicit synchronization, and wrong use issues if/when they surface. My fear is, though, that could be hard to track down.. so the explicit synch is safer if we can't be sure how this is used. I'' try to analyze the usages of the overloaded propertyNames.. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399728#comment-13399728 ] Knut Anders Hatlen commented on DERBY-4269: --- By the way, I don't think the keys-only patch is quite correct. Now that it's using a Vector, there's no elimination of duplicates, and it might return duplicate keys if the read and write fields contain overlapping properties. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399698#comment-13399698 ] Knut Anders Hatlen commented on DERBY-4269: --- FWIW, all the regression tests ran cleanly with the keys-only.diff patch. Even if it doesn't fix the bug, I think it's an improvement as it slightly simplifies the code. > But do we have any guarantee that the returned keys aren't used to access > values (and if so tat those are assumed to be non-null) elsewhere? I don't know. However, what caused this particular bug, was that the override of Properties.propertyNames() itself wasn't safe to use, so that it didn't give the thread-safety guarantees that one would normally expect from Properties' methods. Callers of Properties' methods should already be aware of the limitations of the synchronization guarantees provided by Properties (for example that there is a possibility that getProperty() returns null, as there is no synchronization preventing the property from getting removed after a check for the existence of a key). If they don't take that into consideration, it's a bug that needs to be fixed. But in cases where the actual bug lies in the override of a Properties method, like in this case, one cannot reasonably expect the callers to handle the problem gracefully. So although I cannot guarantee that all users of Properties instances in the engine are free from bugs, I believe that the Properties class does provide the functionality to be used in a thread-safe way, even without adding a semaphore that guards the call to info.clear(). > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399631#comment-13399631 ] Dag H. Wanvik commented on DERBY-4269: -- Yes, it would remove the NPE, I agree. But do we have any guarantee that the returned keys aren't used to access values (and if so tat those are assumed to be non-null) elsewhere? It may well be that that is not the case, and that this solution is ok. Still, I think the shared use of the properties is unsafe... > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch-3.diff, derby-4269-explicit-synch-3.status, > derby-4269-explicit-synch.diff, derby-4269-typo.diff, keys-only.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13397993#comment-13397993 ] Dag H. Wanvik commented on DERBY-4269: -- Attaching derby-4269-explicit-synch-3. This uses a binary semaphore to avoid concurrent aaccess of the "info" Properties object by the two contending threads. EmbedConnection#bootDatabase grabs the semaphore before doing the call on "info.clear" and releases it after. The SlaveDatabaseBootThread grabs it immediately after recovery has been successfully completed after a fail-over (in LogToFile#recover) and releases it when the SlaveDatabaseBootThread is done. This patch passes regressions and also works with my instrumented version of Derby which reliably reproduces the NPE seen in this issue. Unfortunately, it adds a bit for clutter since we need to add the P&V operations through three levels: SlaveDatabase SlaveFactory/SlaveController LogToFile but I didn't find a better way. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch.diff, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396015#comment-13396015 ] Dag H. Wanvik commented on DERBY-4269: -- After this point in the SlaveController it is unsafe to access the properties iff they are being cleared: SlaveController#startSlave, line 254: "startupSuccessful = true;" because past that point, the connection thread is free to proceed and clear the properties, since the last criterion of verifySuccessfulBoot (boot waits for slave operation to be initiated here) is fulfilled. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch.diff, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396009#comment-13396009 ] Dag H. Wanvik commented on DERBY-4269: -- Yes, apparently I did. Here it is for completeness. Unfortunately, explicit synchronization breaks other replication tests. The new extra waiting in "verifySuccessfulboot" makes the boot of the slavedatabase (minus the actual fail-over part to make it a new master) incomplete until fail-over time, cf. the call to startPersistentService mentioned above will now wait longer. This makes other connection attempts to the slave hang (the service isn't started, so the new thread tries to start it again), whereas previously a new thread returned an error indicating that the slave was still in slave state. So, I am back to the first patch, which skips the clearing of the properties for slave databases. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch-2.diff, > derby-4269-explicit-synch.diff, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395454#comment-13395454 ] Knut Anders Hatlen commented on DERBY-4269: --- Did you forget to upload the patch? I don't see it. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch.diff, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13296051#comment-13296051 ] Dag H. Wanvik commented on DERBY-4269: -- Yup, that's even better. Uploading rev #2 of this patch, "derby-4269-explicit-synch-2" using that idea. Rerunning all regressions. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch.diff, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295663#comment-13295663 ] Knut Anders Hatlen commented on DERBY-4269: --- I agree that a fix that's local to SlaveDatabase is cleaner. To reduce the amount of state we need to maintain in the class, we could perhaps pass sdbThread as an argument to verifySuccessfulBoot(), and call isAlive() on it instead of checking the new volatile flag. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch.diff, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295418#comment-13295418 ] Dag H. Wanvik commented on DERBY-4269: -- By way of explanation: the analysis in a comment above is slightly wrong, sml the call to Monitor.startPersistentService (footnote [1] above). This call will actually hang till the failover is *almost* done, but not quite, as evidenced in the bug. The reason the new patch wprks is that it makes sure the boot thread is really finished before allowing the call [1] in the initiating thread to complete. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-explicit-synch.diff, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295365#comment-13295365 ] Dag H. Wanvik commented on DERBY-4269: -- Thanks, Knut. Yes, you are right, we'd need some new mechanism for synchronizing this since the access is to the bottom-most property list. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294935#comment-13294935 ] Knut Anders Hatlen commented on DERBY-4269: --- Looks like a reasonable workaround for the bug, as the call to clear() seems not to be strictly required in any of the cases. The alternative approach of adding extra synchronization may be difficult, unless the Properties objects are replaced with some other data structure. At least the straightforward fix of enclosing the loop in DoubleProperties in a synchronized block on "write" would probably not suffice, because the multi-level nesting of Properties objects would still make it possible for other threads to access one of the underlying Properties objects directly and bypass the top-level synchronization. > 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.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, > 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2 > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294450#comment-13294450 ] Dag H. Wanvik commented on DERBY-4269: -- Regressions passed. Please review. > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, DERBY-4269b.diff, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293714#comment-13293714 ] Dag H. Wanvik commented on DERBY-4269: -- This may not be a problem in production, but it may make several of our replication tests fail, so I am changing priority to Major. > 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 > Labels: derby_triage10_5_2 > Attachments: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz, > derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[
https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293709#comment-13293709
]
Dag H. Wanvik commented on DERBY-4269:
--
Yes, that was my conclusion too. The usage of property lists is extremely
convoluted in the Derby boot process, and it was very hard to understand what's
going on. And since this goes on in a forked VM, using a debugger is tricky
without affecting the timing... I replaced all usages of java.util.Properties
with a specialized version (DerbyProperties), so I could track all allocations
and modifications of properties. Adding to the problem is the fact that
Properties can have default Properties lists recursively, and this is being
used. In addition Derby adds two layers of specializations:
UpdateServiceProperties and DoubleProperties.
Mostly, property lists are passed into constructors without any cloning of them
so the number of live aliases is high.
It turns out the layering at the time of the NPE in the boot is like this:
DoubleProperties#write instance of
UpdateServiceProperties#defaults instance of
Properties#defaults instance of
Properties (no default) <- race on this one
The bottom one is the one that's being changed under our feet in these lines in
EmbedConnection#bootDatabase:
:
// clear these values as some modules hang onto
// the properties set corresponding to service.properties
// and they shouldn't be interested in these JDBC attributes.
info.clear();
It is initially allocated in EmbedConnection#filterProperties:
private Properties filterProperties(Properties inputSet) {
Properties limited = new org.apache.derby.iapi.util.DerbyProperties();
:
assigning it to "info".
The thread that is doing this is the thread that initially started the slave
operation (cf. URL "startSlave=true"). This thread hangs until the master has
been started and replication is underway. When the master comes online this
thread the connect returns with XRE08 ("REPLICATION_SLAVE_STARTED_OK").
The failover happens in this test almost immediately, and the
SlaveDatabaseBootThread then starts moving again (it i waiting for more log
records to replay or failover).
Unfortunately, in the current scenario, the thread doing "startSlave=true" is
still active, normally it would have finished long before
SlaveDatabaseBootThread starts moving again.
The Property default at the 4th level above would normally be empty, since its
being cleared by the "startSlave=true" thread in the "info.clear". Bit since
it's lagging behind, it only does this "clear" when the SlaveDatabaseBootThread
has started its boot, leading to the contention.
> 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: 4269-client-jstack.txt, 4269-master.txt,
> 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff,
> DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz,
> derby-4269-typo.diff
>
>
> 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.derbyTes
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[
https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292712#comment-13292712
]
Knut Anders Hatlen commented on DERBY-4269:
---
The failing code in DoubleProperties.propertyNames():
66if (write != null) {
67
68for (Enumeration e = write.propertyNames(); e.hasMoreElements();
) {
69String key = (String) e.nextElement();
70p.put(key, write.getProperty(key));
71}
72}
One of the arguments to Hastable.put() is null. I think this can only happen if
some other thread is modifying the "write" instance at the same time as this
code runs.
> 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: 4269-client-jstack.txt, 4269-master.txt,
> 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff,
> DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz,
> derby-4269-typo.diff
>
>
> 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291963#comment-13291963 ] Dag H. Wanvik commented on DERBY-4269: -- I caught the exception, and this is what I see, it was an NPE allright: BEGIN REPLICATION ERROR MESSAGE (6/8/12 9:07 PM) Slave recovery: Unexpected exception, thread dies : [0] /export/home/tmp/dag/zb/derby-4269-keepwaiting-replicationTe\ sts.ReplicationRun_Local_3_p6-sb1.jars.sane-1.7.0_04-11053/db_slave/wombat java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:432) at org.apache.derby.iapi.util.DoubleProperties.propertyNames(DoubleProperties.java:70) at org.apache.derby.impl.services.monitor.BaseMonitor.getImplementations(BaseMonitor.java:1065) at org.apache.derby.impl.services.monitor.BaseMonitor.loadInstance(BaseMonitor.java:718) at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:323) at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(BaseMonitor.java:542) at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Monitor.java:427) at org.apache.derby.impl.db.BasicDatabase.bootClassFactory(BasicDatabase.java:731) at org.apache.derby.impl.db.BasicDatabase.boot(BasicDatabase.java:193) at org.apache.derby.impl.db.SlaveDatabase.bootBasicDatabase(SlaveDatabase.java:446) at org.apache.derby.impl.db.SlaveDatabase.access$000(SlaveDatabase.java:72) at org.apache.derby.impl.db.SlaveDatabase$SlaveDatabaseBootThread.run(SlaveDatabase.java:314) at java.lang.Thread.run(Thread.java:722) END REPLICATION ERROR MESSAGE - > 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: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz, > derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291817#comment-13291817 ] Dag H. Wanvik commented on DERBY-4269: -- Yes, I considered that, but was afraid any earlier printing might change the timing, so I opted for a minimum change which only kicks in after the error has happened ;-) We'll see if I catch any fish.. > 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: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz, > derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291733#comment-13291733 ] Knut Anders Hatlen commented on DERBY-4269: --- If you set derby.tests.repltrace to true, the output from the sub-processes will be printed (see ReplicationRun.processDEBUGOutput(), called from runUserCommandLocally()). I assume an uncaught RuntimeException would have been printed to stderr in the sub-process, so it should be possible to see it with the tracing property set. > 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: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz, > derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[
https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291349#comment-13291349
]
Dag H. Wanvik commented on DERBY-4269:
--
In SlaveDataBase, the variable "inReplicationSlaveMode" holds the state. The
error message 08004.C.7 ("Connection refused to database '{0}' because it is in
replication slave mode") i only every issued in two locations, both inside
SlaveDataBase, in methods "setupConnection" and "getAuthenticationService".
In both cases, they test the variable inReplicationSlaveMode. Looking at the
booting (recovery) thread, the variable is reset to false ca line 317, inside
the thread SlaveDatabaseBootThread:
try {
:
bootBasicDatabase(create, params); // will be blocked
// if we get here, failover has been called and the
// database can now be connected to
inReplicationSlaveMode = false;
:
} catch (StandardException se) {
// We get here when SlaveController#stopSlave has been
// called, or if a fatal exception has been thrown.
handleShutdown(se);
}
Now, the thread is gone, but in our cae the variable is still true, so I
believe the boot must have thrown a (runtime?) exception for this to occur.
Notice we only catch StandardException, but any runetime exception would go
unnoticed and the thread would terminate.
I'll try to instrument this code to log any exceptions on derby.log before the
thread dies.
> 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: 4269-client-jstack.txt, 4269-master.txt,
> 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff,
> DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz,
> derby-4269-typo.diff
>
>
> 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291312#comment-13291312 ] Dag H. Wanvik commented on DERBY-4269: -- In a successful failover, I see that the SlavePingThread lives on even after a successful connect, so thas was a red herring. More interesting i the fact that the thread doing recovery has gone, but apparently, the database still thinks it's in a slave state. I'll have a look at that phase transition. > 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: 4269-client-jstack.txt, 4269-master.txt, > 4269-slave-jstack-before-failover.txt, 4269-slave.txt, DERBY-4269.diff, > DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz, > derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291295#comment-13291295 ] Dag H. Wanvik commented on DERBY-4269: -- Trying to connect to the slave maually via ij, i get confirmation it hasn't recovered: ij> connect 'jdbc:derby://localhost:1531/wombat'; ERROR 08004: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08004, SQLERRMC: Connection refused to database '/export/home/tmp/dag/zb/derby-4269-keepwaiting-replicationTests.ReplicationRun_Local_3_p6-sb1.jars.sane-1.7.0_04-25804/db_slave/wombat' because it is in replication slave mode. > 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: 4269-client-jstack.txt, 4269-master.txt, 4269-slave.txt, > DERBY-4269.diff, DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz, > derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291290#comment-13291290 ] Dag H. Wanvik commented on DERBY-4269: -- The only thing that strikes me at first blush is that the slave still has a "ping" thread running: "derby.slave.ping-/export/home/tmp/dag/zb/derby-4269-keepwaiting-replicationTests.ReplicationRun_Local_3_p6-sb1.jars.sane-1.7.0_04-25804/db_slave/wombat" daemon prio=3 tid=0x0873c400 nid=0x13 in Object.wait() [0xd409e000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xf0ff2508> (a java.lang.Object) at java.lang.Object.wait(Object.java:503) at org.apache.derby.impl.store.replication.net.ReplicationMessageReceive$SlavePingThread.run(ReplicationMessageReceive.java:535) - locked <0xf0ff2508> (a java.lang.Object) but I am not sure that is relevant. > 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: 4269-client-jstack.txt, 4269-master.txt, 4269-slave.txt, > DERBY-4269.diff, DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz, > derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291286#comment-13291286 ] Dag H. Wanvik commented on DERBY-4269: -- After a couple of more days, I made it hang by not timing out the ping if it doesn't succeed. Uploading jstacks of the three involved processes: - test client, master and slave > 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: 4269-client-jstack.txt, 4269-master.txt, 4269-slave.txt, > DERBY-4269.diff, DERBY-4269.stat, db_master-derby.log, db_slave-derby.log.gz, > derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288574#comment-13288574 ] Dag H. Wanvik commented on DERBY-4269: -- Did tight runs of this test over the week-end. I was able to reproduce in 2 of 13000 attempts. > 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, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287532#comment-13287532 ] Dag H. Wanvik commented on DERBY-4269: -- FWIW, I was able to boot the slave database without incident. > 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, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287529#comment-13287529 ] Dag H. Wanvik commented on DERBY-4269: -- The call to LogToFile.failoverSlave does the following: flushed received log records to disk, and then does a notify on slaveRecoveryMonitor, i.e. it doesn't wait for the recovery to finish. So it seems the slave has gotten stuck in the recovery somehow, thus making connection attempts fail for two minutes. > 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, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287523#comment-13287523 ] Dag H. Wanvik commented on DERBY-4269: -- Committed typo patch as svn 1345272. > 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, db_master-derby.log, > db_slave-derby.log.gz, derby-4269-typo.diff > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287472#comment-13287472 ] Dag H. Wanvik commented on DERBY-4269: -- The message "Failover perfomed successfully" (sic) is issued after a call in the slave to LogToFile.failoverSlave, cf line 301 in SlaveController#doFailover, so that's how far we know the slave got. > 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, db_master-derby.log, > db_slave-derby.log.gz > > > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286993#comment-13286993 ] Dag H. Wanvik commented on DERBY-4269: -- Thanks, Kristian & Knut! I did notice other place which did not use this pattern, too. Making pincConnect more resilient might be good, unless there are use cases where changed behavior is not desired. I'll have a look. > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285684#comment-13285684 ] Knut Anders Hatlen commented on DERBY-4269: --- It looks good to me too. Do we need similar changes for the other occurrences of this pattern too? Maybe we could make pingConnect() as tolerant as waitForConnect(), so that no changes are needed in the test cases themselves? (The former only tolerate 08004 errors while waiting for the server to come up, whereas the latter accepts all errors.) > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285652#comment-13285652 ] Kristian Waagan commented on DERBY-4269: Thanks, Dag. The change looks good to me, +1. I see that two different values are used for the number of retries; 10 (as in your patch) and 200. I haven't checked if the test is waiting for something it knows takes a long time when the higher number of retries is used. > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285644#comment-13285644 ] Dag H. Wanvik commented on DERBY-4269: -- Thanks, Kristian. Fixed. > 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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285525#comment-13285525 ] Kristian Waagan commented on DERBY-4269: Hi Dag, Is the patch itself missing? > 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.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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[
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
[jira] [Commented] (DERBY-4269) Failover did not succeed in 2 min.: testReplication_Local_3_p6_autocommit_OK
[ https://issues.apache.org/jira/browse/DERBY-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102784#comment-13102784 ] Myrna van Lunteren commented on DERBY-4269: --- I saw this in nightly testing, with the trunk tree (10.9.0.0 alpha) synced to revision 1167430, on Windows XP with ibm 1.6 (sr9fp1). > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
