[
https://issues.apache.org/jira/browse/QPID-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561232#comment-13561232
]
Keith Wall commented on QPID-4541:
----------------------------------
Hi Rajith, Weston,
I've spent sometime looking at the patch tonight, but I'm lacking some
background to review the patch properly.
I need some more details about the sequence of events that allow this defect to
occur. Perhaps if you could summarise what is happening (at protocol level)
between the client and the two brokers (the original broker and the failover).
Also, how does this defect manifest itself to the end-user application? What
are they seeing? If there is a stack trace please attach it here.
Thanks, Keith.
> Messages are replayed after XA commit in a failover scenario
> ------------------------------------------------------------
>
> Key: QPID-4541
> URL: https://issues.apache.org/jira/browse/QPID-4541
> Project: Qpid
> Issue Type: Bug
> Components: Java Client, JCA
> Affects Versions: Future
> Environment: All supported OS platforms, all supported JEE platforms
> Reporter: Weston M. Price
> Assignee: Rajith Attapattu
>
> Currently we are seeing an issue in failover scenarios where messages that
> are received and the XA transaction completes are replayed on the nth node of
> a cluster when failover is invoked. This appears to be similar to QPID-2294
> in the violation of transaction atomicity.
--
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: [email protected]
For additional commands, e-mail: [email protected]
