[JBoss JIRA] Created: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
12:30 a.m.
Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.6.1
Reporter: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior to
work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
3:39 a.m.
New subject: [JBoss JIRA] Commented: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://jira.jboss.org/jira/browse/JBTM-649?page=com.atlassian.jira.plugi...
]
Andrew Dinn commented on JBTM-649:
----------------------------------
Depending upon timings a 60 second timeout may not be enough time to allow recovery to be
performed. By default the recovery manager thread kicks in every 120 seconds. You should
either lower the recovery period or increase your timeout. If the test fails after that
then maybe there is an issue here.
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.6.1
Reporter: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
4:20 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://jira.jboss.org/jira/browse/JBTM-649?page=com.atlassian.jira.plugi...
]
Mark Little updated JBTM-649:
-----------------------------
Component/s: Recovery
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
4:26 a.m.
New subject: [JBoss JIRA] Commented: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://jira.jboss.org/jira/browse/JBTM-649?page=com.atlassian.jira.plugi...
]
Mark Little commented on JBTM-649:
----------------------------------
Plus transactions in a heuristic state are not resolved automatically by the recovery
manager. The fact that something is marked as heuristic means that there is a non-atomic
outcome (depending upon the type of heuristic we may be able to say in which
"direction" that occurs). But regardless, a heuristic is not something that can
be resolved automatically: it required manual intervention.
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
6:27 a.m.
New subject: [JBoss JIRA] Commented: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://jira.jboss.org/jira/browse/JBTM-649?page=com.atlassian.jira.plugi...
]
Howard Gao commented on JBTM-649:
---------------------------------
Thanks Andrew and Mark.
I think I'll try to give a longer timeout (>120) and try the test again. If it
works I think I can drop this issue.
If not, I'll think about Mark's comment and mark this test invalid (and write down
this in the next JBM release note).
Thanks again!
Howard
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
6:29 a.m.
New subject: [JBoss JIRA] Assigned: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://jira.jboss.org/jira/browse/JBTM-649?page=com.atlassian.jira.plugi...
]
Howard Gao reassigned JBTM-649:
-------------------------------
Assignee: Howard Gao
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
10:31 p.m.
New subject: [JBoss JIRA] Closed: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://jira.jboss.org/jira/browse/JBTM-649?page=com.atlassian.jira.plugi...
]
Howard Gao closed JBTM-649.
---------------------------
Resolution: Done
Adding timeout doesn't help. It's clear that TX manager no longer support this. I
remove the test from the JBM testsuite for new TX manager.
I'm closing this now.
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
10:33 p.m.
New subject: [JBoss JIRA] Reopened: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://jira.jboss.org/jira/browse/JBTM-649?page=com.atlassian.jira.plugi...
]
Howard Gao reopened JBTM-649:
-----------------------------
reopen it and re close it with different state
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
10:33 p.m.
New subject: [JBoss JIRA] Closed: (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://jira.jboss.org/jira/browse/JBTM-649?page=com.atlassian.jira.plugi...
]
Howard Gao closed JBTM-649.
---------------------------
Resolution: Rejected
change to rejected.
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://jira.jboss.org/jira/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
8:14 a.m.
New subject: [JBoss JIRA] (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://issues.jboss.org/browse/JBTM-649?page=com.atlassian.jira.plugin.s...
]
Clebert Suconic commented on JBTM-649:
--------------------------------------
Howard: this is really a bug. I'm hitting the same issue at HornetQ
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://issues.jboss.org/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
8:37 a.m.
New subject: [JBoss JIRA] (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://issues.jboss.org/browse/JBTM-649?page=com.atlassian.jira.plugin.s...
]
Yong Hao Gao commented on JBTM-649:
-----------------------------------
Hi Clebert I don't think it's a bug. A Heuristic transaction is not supposed to be
recovered automatically. It has to be manually resolved.
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://issues.jboss.org/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
11:14 a.m.
New subject: [JBoss JIRA] (JBTM-649) Support XAException.XA_RETRY in 2 phase commit -- Backward Compatibility issue
[
https://issues.jboss.org/browse/JBTM-649?page=com.atlassian.jira.plugin.s...
]
Clebert Suconic commented on JBTM-649:
--------------------------------------
The issue I was having was different. The XID1 was prepared/committed, XID2 was
prepared/Retry
At this point no matter what happens XID2 has to be committed on recovery.
Recovery on my case was not working.. but it was a configuration issue.
So, this was not a bug indeed.
Support XAException.XA_RETRY in 2 phase commit -- Backward
Compatibility issue
------------------------------------------------------------------------------
Key: JBTM-649
URL: https://issues.jboss.org/browse/JBTM-649
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Recovery
Affects Versions: 4.6.1
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
Fix For: 4.6.1.CP04
After upgrading from 4.4.0 to 4.6.1 (release for AS5), one of the JBoss Messaging test
starts to fail. The scenario is:
1. We have two XAResources res1 and res2. Both are enlisted in a Transaction.
2. res1 sends a message to Queue1 (server1), res2 sends a message to Queue2 (server2).
3. delist res1 and res2 and commit the transaction.
4. During the commit process, we simulate a failure on res2.commit() so that the
res1.prepare(), res2.prepare() and res1.commit() are all successful but res2.commit() will
throw XAException.XA_RETRY exception -- eventually leaving the transaction in a Heuristic
state.
5. Then we restore res2 back to normal, hoping that the Recovery Manager will kick in and
recover the transaction. So we expect that the two sent messages will be received by the
receiver. To allow the recovery to happen we give a 60 second timeout to receive the
second message. But the result is the first message is received but the second message
isn't.
We know that it is not JTA compliant. But some users may still rely on the old behavior
to work.
Suggestion: a system property can be provided to enable the old behavior if specified by
user.
--
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
4390
days inactive
5296
days old
jbossts-issues@lists.jboss.org
11 comments
5 participants
participants (5)
-
Andrew Dinn (JIRA) -
Clebert Suconic (JIRA)
-
Howard Gao (JIRA)
-
Mark Little (JIRA)
-
Yong Hao Gao (JIRA)