The Reaper thread calls javax.transaction.Synchronization, which only has beforeCompletion() and afterCompletion(status), on the timeout. In order for us to know that the Reaper rolled back the transaction (for whatever reason), we would need one of the following:

1.) Somehow keep track of threads
2.) JTA would need an additional status (STATUS_TIMEDOUT, STATUS_SOMETHING_BAD_HAPPENED, etc.)
3.) JTA's Synchronization would need an additional method (timeout()).

But since none of that exists, I don't see how we can do anything other than change the exception message to be more descriptive.

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