[
https://issues.jboss.org/browse/JBTM-1943?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on JBTM-1943:
-----------------------------------------------
tom.jenkinson(a)redhat.com made a comment on [bug
1009981|https://bugzilla.redhat.com/show_bug.cgi?id=1009981]
Hi Ondra,
The text was broadly correct to me, I reworded the initial few sentences:
"When a machine is under heavy load it may happen that the server log contains
XAExceptions caused by the Recovery Manager attempting to rollback a resource that has
already committed. The transaction is in fact not rolled back at all, the commit is done
but meanwhile the Periodic Recovery process comes into play and potentially sees now stale
resources"
If you want the default time changing that is easy, but we should raise a different BZ I
think.
Tom
Allow the safety interval for RecoveryXids to be configurable
-------------------------------------------------------------
Key: JBTM-1943
URL:
https://issues.jboss.org/browse/JBTM-1943
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: JTA
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 4.17.11, 5.0.0.M5
Currently it is hard coded to 10 seconds. It is possible that under load this could be
possible to breach. Allow the setting to be configurable.
Breaching the threshold does not pose data integrity issues as the scenario where it
becomes an issue is when the transaction has completed during a recovery scan. It will
result in calling rollback(xid1) on the RM but as that RM is guaranteed to have had
commit(xid1) (or rollback) on it already during transaction completion the only impact is
an unsightly stack trace.
--
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