[ https://issues.jboss.org/browse/JBTM-1444?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1444: --------------------------------------- That's what happens when exceptions are thrown from WS-AT participant: *WrongStateException in WS-AT commit* {quote} Only trace logging is printed after exception is thrown: "Unexpected exception from participant commit". Coordinator tries to commit and prints warning once it is timed out. This causes heuristic hazard. {quote} *SystemException in WS-AT commit* {quote} Only trace logging is printed after exception is thrown: "Unexpected exception from participant commit". Coordinator tries to commit and prints warning once it is timed out. This causes heuristic hazard. {quote} *RuntimeException in WS-AT commit* {quote} Only trace logging is printed after exception is thrown: "Unexpected exception from participant commit". Coordinator tries to commit and prints warning once it is timed out. This causes heuristic hazard. {quote} *WrongStateException in WS-AT rollback* {quote} Only trace logging is printed after exception is thrown: "Unexpected exception from participant rollback". Transaction is rolledback successfully {quote} *SystemException in WS-AT rollback* {quote} No logging about the exception. Coordinator tries to rollback but times out. This causes heuristic hazard. {quote} *RuntimeException in WS-AT rollback* {quote} Undertow froze while shutting down. Only trace logging is printed after exception is thrown: "Unexpected exception from participant rollback". Transaction is rolledback successfully {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: http://www.atlassian.com/software/jira