You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Ole Solberg (JIRA)" <ji...@apache.org> on 2008/04/18 12:28:25 UTC
[jira] Created: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication replication commands.
Replication tests must ensure stable replication state has been reached before attempting further connection or new replication replication commands.
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: DERBY-3632
URL: https://issues.apache.org/jira/browse/DERBY-3632
Project: Derby
Issue Type: Bug
Components: Replication, Test
Affects Versions: 10.4.1.4, 10.5.0.0
Environment: All
Reporter: Ole Solberg
Assignee: Ole Solberg
Priority: Minor
When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603415#action_12603415 ]
V.Narayanan commented on DERBY-3632:
------------------------------------
The issue seems straightforward to me, will commit this issue
if my tests pass. Starting test runs now.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3632:
---------------------------------
Issue Type: Task (was: Bug)
I make this issue a task since it is now a meta-issue, c.f the links to individual issues
of instabilities.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Task
> Components: Replication, Test
> Affects Versions: 10.4.2.0, 10.5.1.1
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Fix For: 10.4.2.1
>
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DERBY-3632) Replication tests must
ensure stable replication state has been reached before attempting further
connection or new replication commands.
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603415#action_12603415 ]
narayanan edited comment on DERBY-3632 at 6/8/08 10:53 AM:
-------------------------------------------------------------
The patch for the issue seems straightforward to me, will commit this patch
if my tests pass. Starting test runs now.
was (Author: narayanan):
The issue seems straightforward to me, will commit this issue
if my tests pass. Starting test runs now.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603463#action_12603463 ]
V.Narayanan commented on DERBY-3632:
------------------------------------
I ran tests on this patch and noticed multiple failures.
1) I had a "java.net.SocketException: Connection reset" initially
2) A whole lot of java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: org.apache.derby:type=NetworkServer,system=c013800d-011a-69a4-8c8a-ffff861961bb
3) And quite a few Failed to start database 'singleUse/oneuse49', see the next exception for details.
These might as well be because I missed a runic option while starting the tests. I will run the tests again and shall report back with the test results.
I am careful with this patch because it primarily a timing change in starting the replication master. The failures might also be due to timing changes induced by this patch (Not sure about this one!).
Ole, Can you please confirm that the tests passed for you with the attached patch?
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600959#action_12600959 ]
Dag H. Wanvik commented on DERBY-3632:
--------------------------------------
Looks like this change will make the test more stable.
Just a question.. currently the test sleeps for only 200 milliseconds before trying to see if fail-over occurred (loops max 100 times, i.e. 20 seconds). Is it expected that failover will take so long here?
If the expectation is in the order of several seconds, why is the sleep increment that small (200ms) ?
If this is all as expected, +1 to commit.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Solberg updated DERBY-3632:
-------------------------------
Derby Info: (was: [Patch Available])
Patch has been applied (trunk and merged to 10.4).
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601039#action_12601039 ]
Ole Solberg commented on DERBY-3632:
------------------------------------
"Normally" failover does not take that long. But I have seen cases, with other load on the test host, when both startmaster and failover can take time.
It would be good to see if this change do make the test more stable.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Solberg updated DERBY-3632:
-------------------------------
Derby Info: [Patch Available]
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603551#action_12603551 ]
V.Narayanan commented on DERBY-3632:
------------------------------------
Committed to 10.4 branch also, ran tests,
Sending java/testing/org/apache/derbyTesting/functionTests/tests/replicationTests/ReplicationRun.java
Transmitting file data .
Committed revision 664684.
Found two failures, unrelated to this issue or the patch submitted
1) testAttributeAccumulatedConnectionCount(org.apache.derbyTesting.functionTests.tests.management.NetworkServerMBeanTest)java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: org.apache.derby:type=NetworkServer,system=c013800d-011a-6ce8-6aa1-ffffae960ebe
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.derbyTesting.functionTests.tests.management.MBeanTest.getAttribute(MBeanTest.java:379)
at org.apache.derbyTesting.functionTests.tests.management.NetworkServerMBeanTest.testAttributeAccumulatedConnectionCount(NetworkServerMBeanTest.java:93)
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:101)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
Caused by: javax.management.InstanceNotFoundException: org.apache.derby:type=NetworkServer,system=c013800d-011a-6ce8-6aa1-ffffae960ebe
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:662)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
at org.apache.derbyTesting.functionTests.tests.management.MBeanTest$4.run(MBeanTest.java:382)
... 41 more
2) testAttributeActiveConnectionCount(org.apache.derbyTesting.functionTests.tests.management.NetworkServerMBeanTest)java.security.PrivilegedActionException: javax.management.InstanceNotFoundException: org.apache.derby:type=NetworkServer,system=c013800d-011a-6ce8-6aa1-ffffae960ebe
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.derbyTesting.functionTests.tests.management.MBeanTest.getAttribute(MBeanTest.java:379)
at org.apache.derbyTesting.functionTests.tests.management.NetworkServerMBeanTest.testAttributeActiveConnectionCount(NetworkServerMBeanTest.java:103)
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:101)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
Caused by: javax.management.InstanceNotFoundException: org.apache.derby:type=NetworkServer,system=c013800d-011a-6ce8-6aa1-ffffae960ebe
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:662)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
at org.apache.derbyTesting.functionTests.tests.management.MBeanTest$4.run(MBeanTest.java:382)
... 41 more
FAILURES!!!
Tests run: 9328, Failures: 0, Errors: 2
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603483#action_12603483 ]
V.Narayanan commented on DERBY-3632:
------------------------------------
In addition to the 7 failures in tinderbox, I had Derby-3689 recurring. These don't seem to be
related to the patch.
I am going to commit this patch.
Thanks for the patch Ole.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-3632:
---------------------------------
Fix Version/s: 10.4.2.0
Marking Fix Version 10.4.2 because this work has been ported to 10.4.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Fix For: 10.4.2.0
>
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603500#action_12603500 ]
Ole Solberg commented on DERBY-3632:
------------------------------------
Thanks for committing the patch Narayanan!
And, yes, the tests passed for me - on several platforms....
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-3632:
---------------------------------
Fix Version/s: (was: 10.4.2.0)
10.4.2.1
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Fix For: 10.4.2.1
>
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619895#action_12619895 ]
Rick Hillegas commented on DERBY-3632:
--------------------------------------
Can this issue be marked as resolved?
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Fix For: 10.4.2.0
>
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619909#action_12619909 ]
Ole Solberg commented on DERBY-3632:
------------------------------------
We are still seeing this intermittent failure, although not as frequent. But it apparently needs further work.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Fix For: 10.4.2.0
>
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "V.Narayanan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603485#action_12603485 ]
V.Narayanan commented on DERBY-3632:
------------------------------------
Thank you for the diagnosis on the issue and the patch Ole!
Sending java/testing/org/apache/derbyTesting/functionTests/tests/replicationTests/ReplicationRun.java
Transmitting file data .
Committed revision 664639.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication replication commands.
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Solberg updated DERBY-3632:
-------------------------------
Description:
When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
This causes intermittent errors in replication tests.
was:
When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Solberg updated DERBY-3632:
-------------------------------
Summary: Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands. (was: Replication tests must ensure stable replication state has been reached before attempting further connection or new replication replication commands.)
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3632) Replication tests must ensure stable
replication state has been reached before attempting further connection or
new replication commands.
Posted by "Ole Solberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Solberg updated DERBY-3632:
-------------------------------
Attachment: derby-3632_p1.stat.txt
derby-3632_p1.diff.txt
Patch derby-3632_p1 increases the timeout for starting the master and slave servers and the timeout for a successfull "startmaster=true".
Now allows up to 120s before giving up.
> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3632
> URL: https://issues.apache.org/jira/browse/DERBY-3632
> Project: Derby
> Issue Type: Bug
> Components: Replication, Test
> Affects Versions: 10.4.1.4, 10.5.0.0
> Environment: All
> Reporter: Ole Solberg
> Assignee: Ole Solberg
> Priority: Minor
> Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.