davsclaus wrote: > > Welcome to the Camel community. > > The WARN message > WARN | Execution of JMS message listener failed, and no ErrorHandler has > been set. > > Is in fact not about the Camel error handler. Its about JMS exception > listener you can set on the Activemq/JMS component > http://camel.apache.org/jms > > Yes I think the WARN message could be refined to better reflect this. Its > this interface from the JMS spec > http://download.oracle.com/javaee/5/api/javax/jms/ExceptionListener.html >
I'm a bit confused through your response... I think the warning: Execution of JMS message listener failed, and no ErrorHandler has been set. has nothing to do with the ExceptionListener of the standard JMS-API but with the spring's own proprietary abstraction org.springframework.util.Errorhandler. This warning comes through AbstractMessageListenerContainer.invokeErrorHandler() method invocation while consuming the jms messages. Question: what about org.apache.camel.component.jms.JmsMessageListenerContainer setting such a Errorhandler on it's own (a default one), or that org.apache.camel.component.jms.JmsConfiguration would expose a setter/getter API, so that we (camel-users) can inject a Errorhandler from outside while working with the jms endpoints. Note: Spring provides already 3 implementations of the Errorhandler interface (LoggingErrorHandler, PropagatingErrorHandler and MessagePublishingErrorHandler)-- View this message in context: http://camel.465427.n5.nabble.com/error-handling-on-Http-POST-from-ActiveMQ-to-PHP-application-tp4347185p4358624.html Sent from the Camel - Users mailing list archive at Nabble.com.
