[
https://issues.apache.org/jira/browse/ARIES-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919811#action_12919811
]
Craig Muchinsky commented on ARIES-442:
---------------------------------------
My $0.02, take a similar approach to what you did with the Collaborator class
and log it as "discarded" at the warn level.
> 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.
