[JBoss JIRA] (JBTM-1289) XTS participant completion tests should use a rendezvous to delay close until participant has completed
4:55 p.m.
Paul Robinson created JBTM-1289:
-----------------------------------
Summary: XTS participant completion tests should use a rendezvous to delay
close until participant has completed
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 4.17.1, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
12:26 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Paul Robinson resolved JBTM-1289.
---------------------------------
Resolution: Won't Fix
After talking to Andrew Dinn, we decided that introducing Byteman would probably be an
over-engineered solution and that the Thread.sleep (adequately documented) is sufficient.
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 4.17.1, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
12:31 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1289:
-------------------------------------
This problem only really happens when all parties (participants, coordinator and client)
are running in the same VM. Also, when it does happen, it just causes transactions to be
aborted that otherwise would have completed successfully. Therefore we don't yet see
the need ofr a feature in XTS to prevent this. Maybe one day the community might report
this problem, if so we can tackle it then.
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 4.17.1, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
7:52 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Paul Robinson reopened JBTM-1289:
---------------------------------
As I suspected the AS team would prefer that I used Byteman to solve this problem, rather
than the Thread.sleep: https://github.com/jbossas/jboss-as/pull/3212
Re-opening.
Remember to apply this fix to the affected WSAT tests too.
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 4.17.1, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
1:15 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Work on JBTM-1289 started by Paul Robinson.
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 4.17.1, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
2:22 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Paul Robinson updated JBTM-1289:
--------------------------------
Fix Version/s: 4.17.2
(was: 4.17.1)
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 4.17.2, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
3:28 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Paul Robinson updated JBTM-1289:
--------------------------------
Fix Version/s: 4.17.3
(was: 4.17.2)
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 5.0.0.M2, 4.17.3
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
9:05 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1289:
--------------------------------
Component/s: Testing
XTS
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Testing, XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.7, 5.0.0.M2, 4.17.3
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
12:38 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1289:
--------------------------------
Priority: Minor (was: Major)
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Testing, XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Priority: Minor
Fix For: 4.16.7, 4.17.3, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
2:54 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1289:
-------------------------------------
See AS7-5700 for fix in the AS7 XTS integration tests.
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Testing, XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Priority: Minor
Fix For: 4.16.7, 4.17.3, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
3:39 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1289:
-------------------------------------
The affected tests are as follows:
{code}
./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/Cancel.java
./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/Close.java
./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/Compensate.java
./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/Exit.java
./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/MultiCancel.java
./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/MultiClose.java
./XTS/localjunit/WSTX/src/main/java/com/arjuna/wst11/tests/arq/ba/MultiCompensate.java
./txframework/src/test/java/org/jboss/narayana/txframework/functional/BAParticipantCompletionTest.java
{code}
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Testing, XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Priority: Minor
Fix For: 4.16.7, 4.17.3, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
5:18 p.m.
[
https://issues.jboss.org/browse/JBTM-1289?page=com.atlassian.jira.plugin....
]
Paul Robinson updated JBTM-1289:
--------------------------------
Fix Version/s: 4.17.4
(was: 4.17.3)
XTS participant completion tests should use a rendezvous to delay
close until participant has completed
-------------------------------------------------------------------------------------------------------
Key: JBTM-1289
URL: https://issues.jboss.org/browse/JBTM-1289
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Testing, XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Priority: Minor
Fix For: 4.16.7, 4.17.4, 5.0.0.M2
The problem is that the participant's notification of completion (sent to the coord)
is asynchronous. This can be overtaken by the client's "close" message,
resulting in the coordinator cancelling the activity, due to not all participants being
completed.
The hack is to add a delay before the client calls 'close'. We have that on the
tests in TS, as a stop gap. I am reluctant to apply this hack to the AS test suite as
it's embarrassing and likely to be rejected ;-)
This issue is to resolve the problem properly. Maybe by using a Byteman Rendezvous.
Alternatively there may be some XTS feature that we can use to poll the coordinator. Or
maybe we can add it, as the client API is not standardized.
This issue is not urgent for the TS tests as the hack seems to be holding out at present.
However, we do occasionally see this issue on the XTS AS integration testsuite, which
increases the priority.
--
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
4162
days inactive
4214
days old
jbossts-issues@lists.jboss.org
11 comments
2 participants
participants (2)
-
Paul Robinson (JIRA) -
Tom Jenkinson (JIRA)