[jbossts-issues] [JBoss JIRA] (JBTM-1198) REST-AT does not expose transactions that only exist in the logs
Michael Musgrove (JIRA)
jira-events at lists.jboss.org
Mon Jul 9 16:38:12 EDT 2012
[ https://issues.jboss.org/browse/JBTM-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Musgrove updated JBTM-1198:
-----------------------------------
Summary: REST-AT does not expose transactions that only exist in the logs (was: REST-AT participants should not be able to update recovery urls if there is no log )
Description:
The (REST_AT) coordinator does not include transactions that only exist in the logs. Thus on restart after a crash it does not report their status, nor does it include them in requests for all transactions.
Also the (REST_AT) spec provides a mechanism for participants to tell the coordinator that they are listening for termination requests on a different endpoint. If the associated transaction has gone (ie there is no log for it) then this method should return an error response.
was:The (REST_AT) spec provides a mechanism for participants to tell the coordinator that they are listening for termination requests on a different endpoint. If the associated transaction has gone (ie there is no log for it) then this method should return an error response.
> REST-AT does not expose transactions that only exist in the logs
> ----------------------------------------------------------------
>
> Key: JBTM-1198
> URL: https://issues.jboss.org/browse/JBTM-1198
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST
> Affects Versions: 5.0.0.M1
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M2
>
>
> The (REST_AT) coordinator does not include transactions that only exist in the logs. Thus on restart after a crash it does not report their status, nor does it include them in requests for all transactions.
> Also the (REST_AT) spec provides a mechanism for participants to tell the coordinator that they are listening for termination requests on a different endpoint. If the associated transaction has gone (ie there is no log for it) then this method should return an error response.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list