You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2010/10/09 14:35:31 UTC
[jira] Commented: (ARIES-442) Downgrade exception logging from
error to debug within TxInterceptorImpl
[ 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.