You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2012/09/25 11:13:08 UTC
[jira] [Created] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failure not begin
Keith Wall created QPID-4344:
--------------------------------
Summary: FailoverTest.testP2PFailover 0-9 - failure not begin
Key: QPID-4344
URL: https://issues.apache.org/jira/browse/QPID-4344
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.19
Reporter: Keith Wall
We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
{preformat}
Error Message
failover did not complete
Stacktrace
junit.framework.AssertionFailedError: failover did not complete
at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
{noformat}
Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4344:
--------------------------------
Assignee: Philip Harvey
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Philip Harvey
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467658#comment-13467658 ]
Keith Wall commented on QPID-4344:
----------------------------------
I see the test fail about 1 time in 7 on my machine.
Further investigation shows that:
* it was commit QPID-4284 that exposes the issue. Prior to this commit point the test runs reliably (in a loop for hours). The changes to virtualhosts-systests-settings.xml and virtualhosts-systests-bdb-settings.xml alone (i.e. removal of localhost and development) are sufficient to start seeing the failure.
* I cannot reproduce the problem before QPID-4289 (Fix 0-8/0-9/0-9-1 failover issues) even with the virtualhosts changes of QPID-4284. I therefore conclude that QPID-4289 has introduced a new issue, or made an existing issue more likely happen.
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4344:
--------------------------------
Attachment: QPID-4344-failover-race-condition.jpg
attached my sketch of a flow diagram showing how this problem occurs.
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Philip Harvey
> Attachments: QPID-4344-failover-race-condition.jpg, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4344:
-----------------------------
Comment: was deleted
(was: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-JDK1.7/lastCompletedBuild/testReport/org.apache.qpid.client.failover/FailoverBehaviourTest/testPublishAutoAcknowledgedWithFailoverMutex/)
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464662#comment-13464662 ]
Keith Wall commented on QPID-4344:
----------------------------------
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-JDK1.7/lastCompletedBuild/testReport/org.apache.qpid.client.failover/FailoverBehaviourTest/testPublishAutoAcknowledgedWithFailoverMutex/
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Comment Edited] (QPID-4344) FailoverTest.testP2PFailover
0-9 - failover not begun by client
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490038#comment-13490038 ]
Robbie Gemmell edited comment on QPID-4344 at 11/3/12 3:33 PM:
---------------------------------------------------------------
I have applied the patch, but with some further changes. Looking over the patch I came to think that although it would indeed make the test pass it may not be the solution and could potentially lead to the client failing over twice (first due to the new TransportException == connectionProblem check, then potentially again when the IoReciever running that check then completed its run and called closed()).
Considering the diagram you atached and looking at what we changed on QPID-4289 that could have caused this issue it appears that we removed use of a catch block that would have prevented the SenderException propagating as far as it now does, and that seems to be the real issue so I have put a similar catch block in place in CCMH to achieve the same effect. In doing that I realsied that the AMQPH.exception() method was susceptable to similar exceptions being thrown from its attempt to close the network connection so I also added a catch block there.
Since the changes in QPID-4289 appear to be the cause of this issue and those changes are within the current release cycle I am closing this JIRA out and we can continue things over on the reopened QPID-4289.
was (Author: gemmellr):
I have applied the patch, but with some further changes. Looking over the patch I came o think that although it would indeed make the test pass it may not be the solution and could potentially lead to the client failing over twice (first due to the new TransportException == connectionProblem check, then potentially again when the IoReciever running that check then completed its run and called close()).
Considering the diagram you atached and looking at what we changed on QPID-4289 that could have caused this issue it appears that we removed use of a catch block that would have prevented the SenderException propagating as far as it now does, and that seems to be the real issue so I have put a similar catch block in place in CCMH to achieve the same effect. In doing that I realsied that the AMQPH.exception() method was susceptable to similar exceptions being thrown from its attempt to close the network connection so I also added a catch block there.
Since the changes in QPID-4289 appear to be the cause of this issue and those changes are from within the current dev cycle I am closing this JIRA out and we can continue things over on the reopened QPID-4289.
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Attachments: 0001-QPID-4344-now-including-TransportException-in-the-se.patch, QPID-4344-failover-race-condition.jpg, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462596#comment-13462596 ]
Keith Wall commented on QPID-4344:
----------------------------------
I can see from the logs that the client has decided (incorrectly) not to begin the failover process. It appears that the client has become confused and incorrectly believes that the application has closed the connection rather than the client.
{noformat}
012-09-24 18:15:59,583 DEBUG [qpid.client.protocol.AMQProtocolHandler] Session closed called by client
{noformat}
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4344:
-----------------------------
Attachment: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-4344:
---------------------------------
Status: Ready To Review (was: In Progress)
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Attachments: 0001-QPID-4344-now-including-TransportException-in-the-se.patch, QPID-4344-failover-race-condition.jpg, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4344:
--------------------------------
Attachment: 0001-QPID-4344-now-including-TransportException-in-the-se.patch
Attached patch.
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Philip Harvey
> Attachments: 0001-QPID-4344-now-including-TransportException-in-the-se.patch, QPID-4344-failover-race-condition.jpg, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-4344:
---------------------------------
Status: Open (was: Ready To Review)
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Attachments: 0001-QPID-4344-now-including-TransportException-in-the-se.patch, QPID-4344-failover-race-condition.jpg, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Resolved] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-4344.
----------------------------------
Resolution: Duplicate
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Attachments: 0001-QPID-4344-now-including-TransportException-in-the-se.patch, QPID-4344-failover-race-condition.jpg, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490038#comment-13490038 ]
Robbie Gemmell commented on QPID-4344:
--------------------------------------
I have applied the patch, but with some further changes. Looking over the patch I came o think that although it would indeed make the test pass it may not be the solution and could potentially lead to the client failing over twice (first due to the new TransportException == connectionProblem check, then potentially again when the IoReciever running that check then completed its run and called close()).
Considering the diagram you atached and looking at what we changed on QPID-4289 that could have caused this issue it appears that we removed use of a catch block that would have prevented the SenderException propagating as far as it now does, and that seems to be the real issue so I have put a similar catch block in place in CCMH to achieve the same effect. In doing that I realsied that the AMQPH.exception() method was susceptable to similar exceptions being thrown from its attempt to close the network connection so I also added a catch block there.
Since the changes in QPID-4289 appear to be the cause of this issue and those changes are from within the current dev cycle I am closing this JIRA out and we can continue things over on the reopened QPID-4289.
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Attachments: 0001-QPID-4344-now-including-TransportException-in-the-se.patch, QPID-4344-failover-race-condition.jpg, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4344:
--------------------------------
Attachment: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
we saw another failure of this test today on our CI server.
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Philip Harvey
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4344:
-----------------------------
Description:
We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
{preformat}
Error Message
failover did not complete
Stacktrace
junit.framework.AssertionFailedError: failover did not complete
at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
{noformat}
Log attached.
was:
We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
{preformat}
Error Message
failover did not complete
Stacktrace
junit.framework.AssertionFailedError: failover did not complete
at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
{noformat}
Log attached.
Summary: FailoverTest.testP2PFailover 0-9 - failover not begun by client (was: FailoverTest.testP2PFailover 0-9 - failure not begin)
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {preformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4344:
-----------------------------
Description:
We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
{noformat}
Error Message
failover did not complete
Stacktrace
junit.framework.AssertionFailedError: failover did not complete
at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
{noformat}
Log attached.
was:
We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
{preformat}
Error Message
failover did not complete
Stacktrace
junit.framework.AssertionFailedError: failover did not complete
at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
{noformat}
Log attached.
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Assigned] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey reassigned QPID-4344:
-----------------------------------
Assignee: Robbie Gemmell (was: Philip Harvey)
please can you review the patch
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Attachments: 0001-QPID-4344-now-including-TransportException-in-the-se.patch, QPID-4344-failover-race-condition.jpg, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out, TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4344) FailoverTest.testP2PFailover 0-9 -
failover not begun by client
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476036#comment-13476036 ]
Philip Harvey commented on QPID-4344:
-------------------------------------
I've been trying to reproduce this on my laptop using the head of trunk and profile java-bdb.0-9, and haven't seen it fail after 60 runs. Will try again using the specific commits Keith referred to. For future reference, these are:
* QPID-4289 (various failover fixes): git commit 35e75488ec3f1b0048f2948701bcfdc8106d760e, SVN rev 1382799, 10 September
* QPID-4284 (systest virtualhost.xml changes): git commit f972745a94f0f0bf47faca29c0697783408c7ce0, SVN rev 1386864, 17 September
> FailoverTest.testP2PFailover 0-9 - failover not begun by client
> ---------------------------------------------------------------
>
> Key: QPID-4344
> URL: https://issues.apache.org/jira/browse/QPID-4344
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Reporter: Keith Wall
> Assignee: Philip Harvey
> Attachments: TEST-org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover.out
>
>
> We saw a failure on FailoverTest.testP2PFailover test last night a Jenkins CI instance.
> {noformat}
> Error Message
> failover did not complete
> Stacktrace
> junit.framework.AssertionFailedError: failover did not complete
> at org.apache.qpid.test.client.failover.FailoverTest.causeFailure(FailoverTest.java:252)
> at org.apache.qpid.test.client.failover.FailoverTest.runP2PFailover(FailoverTest.java:227)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:190)
> at org.apache.qpid.test.client.failover.FailoverTest.testP2PFailover(FailoverTest.java:155)
> at org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:242)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> {noformat}
> Log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org