[
https://issues.apache.org/jira/browse/AMQ-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085504#comment-15085504
]
ASF subversion and git services commented on AMQ-6089:
------------------------------------------------------
Commit 16bc0f0d750530643333695ba20f6a736704271c in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=16bc0f0 ]
https://issues.apache.org/jira/browse/AMQ-6089 - support TMNOFLAGS as a scan
end to allow looping calls to recover to terminate
> org.apache.activemq.TransactionContext.recover(int flag) should return null
> or an empty array when it receives the flag XAResource.TMNOFLAGS as it has
> return all transactions when called with XAResource.TMSTARTRSCAN. or
> XAResource. TMENDRSCAN.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-6089
> URL: https://issues.apache.org/jira/browse/AMQ-6089
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.12.1
> Reporter: Chris
> Assignee: Gary Tully
> Labels: newbie
> Attachments: AMQRecoveryTester.java, XAHandlerXid.java, activemq
> 5.12.patch
>
>
> org.apache.activemq.TransactionContext implements XAResource. The recover
> method currently ignores the flag parameter, returning all transaction
> regardless of flags passed to it. This behaviour cause our transaction
> manager (IIB) to go into an indefinite loop. It is expecting to get an empty
> array or null when XAResource.TMNOFLAGS is passed as all transactions where
> returned by the prior XAResource.TMSTARTRSCAN call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)