Red Hat Bugzilla – Bug 1029499
Add a troubleshooting chapter to transactions subsection
Last modified: 2014-08-14 11:21:33 EDT
Title: Transactions Configuration Overview
I want to ask for creating a troubleshooting section for Transaction subsystem in documentation. We were solving one bz (https://bugzilla.redhat.com/show_bug.cgi?id=1009981) which causes a log being filled with warning messages.
Information about configuration of the AS server should be documented.
The text came from the bz1009981
When machine is under bigger load of the receiving messages there could happen the server log would contain XAException from Periodic Recovery of rollbacking a transaction.
We hit this for HornetQ but this is supposed to happen for any messaging system used under EAP.
The transaction is in fact not rollbacked at all. The commit is done but meanwhile the Periodic Recovery process comes into play. The scenario is described by Tom in the comment:
The transaction handling and periodic recovery are two independent threads which access a same transaction record.
The RAR informs periodic recovery about not commited transaction and tries to recover it but meanwhile the RAR procceed with the commit.
Log could contains XAException which informs about fail to rollback a transaction by Periodic Recovery. But in fact there was no rollback and all messages were correctly received and commited.
There isn't any generic fix possible being done in Narayana code. When the problem occurs it's recommended to increase interval between the two phases of the recovery process. Use property
at the start of the EAP server and set it to the bigger number than the 10000 milliseconds which is default value.
Use com.arjuna.ats.jta.orphanSafetyInterval property when problem occurs.
I'm not quite sure just what you're asking be added to the Admin & Config Guide. When I read over this BZ ticket and BZ1009981 it looks as if this is something that should be mentioned in the Release Notes. Perhaps I misunderstand and the issue is more complex.
Can you please explain further?
you are right. This should be put to Release Notes.
My prior intention (or the reason why I asked to add it to config guide) was to inform user about some configuration option that could solve some problems.
But I agree with you that this should be put rather to release notes.
I'm sorry for confusions
I've slightly changed the doc text in the https://bugzilla.redhat.com/show_bug.cgi?id=1009981
I have closed this BZ ticket as Ondrej and I have agreed that a release notes entry is all that is required. The RN entry has been made in the parent of this BZ ticket, BZ1009981.