[
https://jira.jboss.org/jira/browse/JBMESSAGING-147?page=com.atlassian.jir...
]
Tim Fox closed JBMESSAGING-147.
-------------------------------
Fix Version/s: Unscheduled
(was: 2.0.0 Beta)
Resolution: Duplicate Issue
This is handled by implementing xa timeouts
Make jms local transactions in doubt
------------------------------------
Key: JBMESSAGING-147
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-147
Project: JBoss Messaging
Issue Type: Task
Components: Messaging Core
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: Unscheduled
Original Estimate: 2 days
Remaining Estimate: 2 days
When 2PC is used, jms server "transactions" (i.e. not JTA transactions -
internal server side tx) can be left "hanging" in prepared state by badly
behaved or crashed clients.
However we don't want to remove them since we do not know that recovery will not
occur in the future therefore we should flag them as in doubt so the administrator can
come in and deal with them heuristically
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira