You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Petr Šrůtka (JIRA)" <ji...@apache.org> on 2014/06/03 09:11:02 UTC
[jira] [Created] (JCR-3785) Not logged exception.
Petr Šrůtka created JCR-3785:
--------------------------------
Summary: Not logged exception.
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, commit and rollback 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
(v6.2#6252)