[JBoss JIRA] Created: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
6:48 p.m.
XTS BA coordinator drops completed as per spec but causes long delay for web service
compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://jira.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.6.1.CP08, 4.13.0
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.14.0, 4.6.1.CP09
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:15 p.m.
New subject: [JBoss JIRA] Commented: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://jira.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.sys...
]
Andrew Dinn commented on JBTM-802:
----------------------------------
This is ok to do so long as the participant is known to be a JBoss participant. So, we
need to check the participant id and respond accordingly.
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://jira.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.14.0, 4.6.1.CP09
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://jira.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.sys...
]
Mark Little updated JBTM-802:
-----------------------------
Component/s: XTS
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://jira.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.14.0, 4.6.1.CP09
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:59 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn updated JBTM-802:
-----------------------------
Fix Version/s: 4.15.0
(was: 4.14.0)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.15.0, 4.6.1.CP09
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn updated JBTM-802:
-----------------------------
Fix Version/s: (was: 4.6.1.CP09)
This needs to be factored back into 4.6.1.CPXX at some point but not for CP09.
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.15.0
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:27 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Jonathan Halliday updated JBTM-802:
-----------------------------------
Fix Version/s: 4.6.1.CP10
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.15.0, 4.6.1.CP10
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:13 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Jonathan Halliday updated JBTM-802:
-----------------------------------
Fix Version/s: 4.6.1.CP11
(was: 4.6.1.CP10)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.15.0, 4.6.1.CP11
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:02 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Jonathan Halliday updated JBTM-802:
-----------------------------------
Fix Version/s: 4.6.1.CP12
(was: 4.6.1.CP11)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.15.0, 4.6.1.CP12
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Jonathan Halliday updated JBTM-802:
-----------------------------------
Fix Version/s: 4.15.1
(was: 4.15.0)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.6.1.CP12, 4.15.1
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:25 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn updated JBTM-802:
-----------------------------
Assignee: (was: Andrew Dinn)
Fix Version/s: 4.6.1.CP12
5.0.0.M1
(was: 4.15.2)
Punting this to next AS7 and EAP5 releases and deassigning until Paul arrives to take it
over
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Fix For: 4.6.1.CP12, 5.0.0.M1
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:08 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Jonathan Halliday updated JBTM-802:
-----------------------------------
Fix Version/s: 4.6.1.CP13
5.0.0.M2
(was: 5.0.0.M1)
(was: 4.6.1.CP12)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Fix For: 4.6.1.CP13, 5.0.0.M2
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:14 p.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson updated JBTM-802:
-------------------------------
Assignee: Paul Robinson
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Fix For: 4.6.1.CP13, 5.0.0.M2
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:09 p.m.
New subject: [JBoss JIRA] Commented: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-802:
------------------------------------
Andrew,
{quote}
This needs to be factored back into 4.6.1.CPXX at some point but not for CP09.
{quote}
By this do you mean that the work has been completed for trunk but needs back porting, or
are you simply reminding the resolver that it's not just trunk that needs the fix?
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Fix For: 4.6.1.CP13, 5.0.0.M2
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:17 p.m.
New subject: [JBoss JIRA] Commented: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn commented on JBTM-802:
----------------------------------
The latter i.e. the fix version needs to include both a 5.XXX and 4.6.1.YYY value.
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Fix For: 4.6.1.CP13, 5.0.0.M2
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson updated JBTM-802:
-------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M2)
(was: 4.6.1.CP13)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Fix For: 5.0.0.Final
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
New subject: [JBoss JIRA] Updated: (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-802:
-------------------------------
Fix Version/s: 4.6.1.CP13
4.15.x
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Fix For: 4.6.1.CP13, 4.15.x, 5.0.0.Final
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:23 p.m.
New subject: [JBoss JIRA] (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Paul Robinson commented on JBTM-802:
------------------------------------
Andrew,
You marked this as a bug. I'm not so sure it is a bug, it sounds like we are doing
what the spec states we should do. What you propose in this issue is an improvement on
what the spec provides. Is this correct?
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Fix For: 4.6.1.CP13, 4.15.x, 5.0.0.Final
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
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
6:28 p.m.
New subject: [JBoss JIRA] (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Andrew Dinn commented on JBTM-802:
----------------------------------
No, strictly it is not a bug as we are doing what is expected in the spec and it is
functional. The problem raised here is a performance issue.
When the coordinator goes down before closing or cancelling a BA there may still be
completed participants running. Those participants keep on sending completed notifications
with an increasing timeout until at some point they decide to resend a getStatus message.
The coordinator will no longer know about the BA after it reboots but is only allowed to
reject the getStatus request so the web service can spend a long time waiting before it
detects that it is game over for the BA (with our default timeout it takes about 600
seconds befoe the web service gets fed up and pings a getStatus()). If we break the spec
and send invalidTX in response to completed then this will make the TX exit quicker.
Having thought about this a little more I am not sure this is necessarily the best way to
achieve this. The web service is always allowed to send getStatus whenever it wants. So,
we could consider change the behaviour on the web service side to make it detect the
failure condition earlier without breaking the spec e.g. we could gradually increase the
timeout resending, alternately, first a completed message and then a getStatus message.
This is maybe a better solution but it needs some careful adjusting. Currently, a
successful response to getStatus resets the resend timeout to the minimum. But the whole
point of gradually increasing the timeout is to avoid flooding the coordinator with
'and me' messages when it is waiting for another participant to complete before
closing. This needs thinking through.
Whatever we implement we ought to implement it in trunk as well as in the EAP5 branch. The
reason the fix was initially slated for there was that the problem arose with an EAP5
customer but that was not meant to indicate that we don't want a fix in trunk.
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Fix For: 4.6.1.CP13, 4.15.x, 5.0.0.Final
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
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:46 a.m.
New subject: [JBoss JIRA] (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-802:
-------------------------------
Priority: Minor (was: Major)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Priority: Minor
Fix For: 4.6.1.CP13, 4.15.x, 5.0.0.Final
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
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
7:45 p.m.
New subject: [JBoss JIRA] (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson updated JBTM-802:
-------------------------------
Fix Version/s: 4.16.1
(was: 4.16.x)
I have updated the 4.16.x version to 4.16.1, feel free to drop it from this version if you
want to but I want to kill 4.16.x as a version
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Priority: Minor
Fix For: 4.6.1.CP13, 4.16.1, 5.0.0.Final
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
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:21 a.m.
New subject: [JBoss JIRA] (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-802:
-------------------------------
Fix Version/s: (was: 4.6.1.CP13)
(was: 4.16.1)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Priority: Minor
Fix For: 5.0.0.Final
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
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:21 a.m.
New subject: [JBoss JIRA] (JBTM-802) XTS BA coordinator drops completed as per spec but causes long delay for web service compensation
[
https://issues.jboss.org/browse/JBTM-802?page=com.atlassian.jira.plugin.s...
]
Paul Robinson updated JBTM-802:
-------------------------------
Comment: was deleted
(was: I have updated the 4.16.x version to 4.16.1, feel free to drop it from this version
if you want to but I want to kill 4.16.x as a version)
XTS BA coordinator drops completed as per spec but causes long delay
for web service compensation
-------------------------------------------------------------------------------------------------
Key: JBTM-802
URL: https://issues.jboss.org/browse/JBTM-802
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: XTS
Affects Versions: 4.13.0, 4.6.1.CP08
Reporter: Andrew Dinn
Assignee: Paul Robinson
Priority: Minor
Fix For: 5.0.0.Final
The WSBA spec requires a coordinator to drop completed requests from a web service
belonging to an unknown transaction. The idea is that the web service eventually gets
bored and sends a getstatus message to see if the transacton is still valid at which point
the coordinator dispatches an invalid state fault initiating compensation at the web
service end. The problem is that timeing out the resending of completed and switching to
sending getstatus is a tricky business. Done too early it can cause ping-ponging back and
forth from completed to getstatus. Too late and it means it takes a long time before
compensation is done.
It is not clear from the spec that completed cannot also legitimately send an invalid
state fault when it sees completed from an unknown participant. If so then doing this
would significantly speed up recovery. This needs investigating to check that it will not
cause interop problems and, if it is permissible, should be implemented.
--
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
4732
days inactive
5195
days old
jbossts-issues@lists.jboss.org
21 comments
8 participants
participants (8)
-
Andrew Dinn (Commented) (JIRA) -
Andrew Dinn (JIRA)
-
Jonathan Halliday (JIRA)
-
Mark Little (JIRA)
-
Paul Robinson (Commented) (JIRA)
-
Paul Robinson (JIRA)
-
Paul Robinson (Updated) (JIRA)
-
Tom Jenkinson (JIRA)