The arjuna code uses pattern e.printStackTrace() on several places in the code. This would be better to be changed for a logger would be used.
For ArjunaJTA I counted 28 (excluding tests) places where the logger is not used and I suppose it should be.
Secondary. It would be nice in case of the XAException the error code would be printed together with the exception stacktrace. I have one example where I would appreciated it for example.
method handleOrphan where after the xares.rollback(xid) is called the exception is printed to stdout + log does not contain the error code.
Is this being reported as an enhancement or bug. If its an enhancement I think it might be better to tackle it as an upstream Jira?
First time I thought this being a bug but there is no problem for me to consider it as a feature request. And postpone it for the next EAP6 release.
As a feature request I'm moving this issue to TM JIRA feature request and closing this issue.
Agreed with Tom to leave this bz as community issue. Closing this one.