Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Message-ID: <19312127.54401286627731670.JavaMail.jira@thor>
Date: Sat, 9 Oct 2010 08:35:31 -0400 (EDT)
From: "Valentin Mahrwald (JIRA)" <jira@apache.org>
To: aries-dev@incubator.apache.org
Subject: [jira] Commented: (ARIES-442) Downgrade exception logging from
 error to debug within TxInterceptorImpl
In-Reply-To: <14971039.26781286468371711.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ARIES-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919489#action_12919489 ] 

Valentin Mahrwald commented on ARIES-442:
-----------------------------------------

Logging in the normal return case got downgraded to debug in #1006142. The error level in the postCallWithException seems more appropriate, since the TransactionRollback exception does not thrown on. Does that sound reasonable?

> Downgrade exception logging from error to debug within TxInterceptorImpl
> ------------------------------------------------------------------------
>
>                 Key: ARIES-442
>                 URL: https://issues.apache.org/jira/browse/ARIES-442
>             Project: Aries
>          Issue Type: Improvement
>          Components: Transaction
>    Affects Versions: 0.3
>            Reporter: Craig Muchinsky
>            Assignee: Valentin Mahrwald
>            Priority: Minor
>
> Exception logging within the TxInterceptorImpl class is currently done at error level, however in many cases these exceptions are expected and shouldn't be cause for concern. For example, I have an application that gracefully handles txn rollbacks due to database deadlocks and retries them, so I don't want the log file to get filled with stack traces unnecessarily. Currently the only workaround is to turn off logging for TxInterceptorImpl specifically.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.