[jbossts-issues] [JBoss JIRA] (JBTM-2879) JTS before_completion in SynchronizationImple swallows and hides exceptions

Tom Jenkinson (JIRA) issues at jboss.org
Thu Apr 6 09:24:00 EDT 2017


    [ https://issues.jboss.org/browse/JBTM-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13390199#comment-13390199 ] 

Tom Jenkinson commented on JBTM-2879:
-------------------------------------

The interface is here to explain the UNKNOWN: https://github.com/jbosstm/narayana/blob/781ace284d840805282e037e9c10c8de6f2de472/ArjunaJTS/idl/src/main/idl/omg/CosTransactions.idl#L228

But yes, logging the exception would be beneficial I feel.

> JTS before_completion in SynchronizationImple swallows and hides exceptions
> ---------------------------------------------------------------------------
>
>                 Key: JBTM-2879
>                 URL: https://issues.jboss.org/browse/JBTM-2879
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: JTS
>            Reporter: David Lloyd
>            Assignee: Ondra Chaloupka
>             Fix For: 5.next
>
>
> In [SynchronizationImple|https://github.com/jbosstm/narayana/blob/781ace284d840805282e037e9c10c8de6f2de472/ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/resources/jts/orbspecific/SynchronizationImple.java#L93], if the user's synchronization fails, the exception is swallowed and never logged.  Instead a descriptionless {{UNKNOWN}} is thrown.
> The exception should at least be logged to aid in troubleshooting.
> Later in the same file, {{after_completion}} is using {{e.printStackTrace()}} to log the stack, which is also less than ideal.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbossts-issues mailing list