]
Tom Jenkinson updated JBTM-1482:
--------------------------------
Assignee: Gytis Trikleris (was: Tom Jenkinson)
If a naughty afterCompletion sync throws an exception, log the
exception call stack
-----------------------------------------------------------------------------------
Key: JBTM-1482
URL:
https://issues.jboss.org/browse/JBTM-1482
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Transaction Core
Reporter: Scott Marlow
Assignee: Gytis Trikleris
Priority: Minor
Fix For: 5.0.0.M3
Currently, when this happens with AS, I see:
{quote}
2013-02-18 16:24:43,837|WARN |[com.arjuna.ats.jta]|(ThreadId: Transaction Reaper Worker
221)|ARJUNA016029: SynchronizationImple.afterCompletion - failed for
org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization@634ef5a7 with
exception: java.lang.NullPointerException
{quote}
From a related email conversation:
{quote}
Here's our Logger code:
@Message(id = 16029, value = "SynchronizationImple.afterCompletion - failed for
{0} with exception", format = MESSAGE_FORMAT)
@LogMessage(level = WARN)
public void warn_resources_arjunacore_SynchronizationImple(String arg0, @Cause()
Throwable arg1);
Here is where we call our logger:
jtaLogger.i18NLogger.warn_resources_arjunacore_SynchronizationImple(_theSynch.toString(),
e);
Maybe the message should have the {1} in it, i.e. it change it like so:
"SynchronizationImple.afterCompletion - failed for {0} with exception {1}"
{quote}
--
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: