[
https://issues.apache.org/jira/browse/TEPHRA-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873301#comment-15873301
]
Albert Shau commented on TEPHRA-209:
------------------------------------
As part of this, it would be nice to clean up logging that happens for various
errors. For example, if the tx service can't be discovered,
AbstractClientProvider logs an error 'Unable to discover tx service.'.
Throwing a good exception should be enough, with the caller deciding whether it
should be logged as an error or not.
> Improve exception handling in TransactionSystemClient
> -----------------------------------------------------
>
> Key: TEPHRA-209
> URL: https://issues.apache.org/jira/browse/TEPHRA-209
> Project: Tephra
> Issue Type: Improvement
> Reporter: Albert Shau
> Assignee: Poorna Chandra
>
> The TransactionSystemClient API does not define very many exceptions that may
> happen during failures. For example, the start methods don't throw any
> checked exceptions, so the user just has to know that if the transaction
> service is not available, a RuntimeException wrapping a TException is thrown.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
