[
https://issues.apache.org/jira/browse/QPID-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170956#comment-13170956
]
Keith Wall commented on QPID-3683:
----------------------------------
This is a Broker side problem that only manifests itself when Broker is
co-located with the testing framework.
Investigation shows that on the occasions that fail, the
QpidBrokerTestCase#tearDown is underway whilst the QueueDeclare is being
processed (the QueueDeclate is part of the client's resubscribe activity after
failover).
The tearDown reverts changes to system properties. The QueueDeclare uses the
Configuration object to create a QueueConfiguration for the new queue. There
is an unlucky timing where thread processing the QueueDeclare can be interating
the configuration keys whilst in the main thread, #tearDown is removing the
test system properties. As the Configuration is formed from a composite
configuration comprising config.xml + system properties, the modification to
the system properties can give rise to the ConcurrentModificationException.
The underlying problem here is QPID-3691. The client should not proceed (i.e
report failover complete) until it knows the resubscribe activity is complete
(i.e. synch'd).
> FailoverBehaviourTest.testPublishClientAcknowledgedWithFailoverMutex/testPublishTransactedAcknowledgedWithFailoverMutex
> failing regularly on Jenkins.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3683
> URL: https://issues.apache.org/jira/browse/QPID-3683
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: 0.15
>
>
> We are seeing the following tests
> org.apache.qpid.client.failover.FailoverBehaviourTest.testPublishClientAcknowledgedWithFailoverMutex
>
> org.apache.qpid.client.failover.FailoverBehaviourTest.testPublishTransactedAcknowledgedWithFailoverMutex
> fail very regularly on Jenkins.
--
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
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
