You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2020/05/04 14:50:00 UTC

[jira] [Updated] (JCR-3785) TransactionContext: exception not logged

     [ https://issues.apache.org/jira/browse/JCR-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated JCR-3785:
--------------------------------
    Summary: TransactionContext: exception not logged  (was: Not logged exception.)

> TransactionContext: exception not logged
> ----------------------------------------
>
>                 Key: JCR-3785
>                 URL: https://issues.apache.org/jira/browse/JCR-3785
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: transactions
>    Affects Versions: 2.6.5, 2.8
>            Reporter: Petr Šrůtka
>            Priority: Minor
>
> In TransactionContext.java, methods prepare and commit catch TransactionException and then use it as init cause for XAException. XAException then logs only 
> {code}
> 2014-06-02 17:06:02,500 [http-172.18.4.39-8080-5] WARN  [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] [com.arjuna.ats.internal.jta.resources.arjunacore.rollbackxaerror] XAResourceRecord.rollback - xa error XAException.XA_RBOTHER
> {code}
> and the initial cause is lost.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)