[
https://issues.apache.org/jira/browse/CAMEL-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4958.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.9.1
Is now less verbose, and Spring no longer complains about no error handler
configured. Added options to tweak logging levels and verbosity.
> camel-jms - JmsConsumer make it less verbose logging in case of an exception
> or TX rollback
> -------------------------------------------------------------------------------------------
>
> Key: CAMEL-4958
> URL: https://issues.apache.org/jira/browse/CAMEL-4958
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.1, 2.10.0
>
>
> When using a JMS route, and an exception occurs, then you get a WARN logging
> from Spring JMS that there is no error handler configured.
> And you get the stacktrace etc.
> {code}
> 2012-01-31 07:27:51,628 [sConsumer[okay]] WARN
> ultJmsMessageListenerContainer - Execution of JMS message listener failed,
> and no ErrorHandler has been set.
> org.apache.camel.RuntimeCamelException: ...
> {code}
> However Camel itself will also by default log the stacktrace, so we have it
> logged twice. We should make this less verbose.
> And allow end users to more easily customize the logging level and/or whether
> stracktraces should be included.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
