The following part of my camel routing intercepts X3SClientException
java exception and put message (= collection of Audit objects) it in a
reporting queue :
<camel:doCatch>
<camel:exception>com.xpectis.x3s.exception.X3SClientException</camel:exception>
<camel:bean ref="serviceHelper"
method="processException" />
<camel:to
ref="queueReportingEndpoint" />
</camel:doCatch>
A)
I don't see the messages generated in the queue x3s://queue:reporting
using jconsole
QUESTION : Do we have an issue between mbeans and Camel 2.1-SNAPSHOT /
activemq ?
B)
The trace generated in the log mentions that the message has been put
in the destination queue x3s://queue.request after an exception
occurs.
I have the impression that this information comes from what happens at
the beginning of the routing when we receive the files and put it in
the request queue.
What surprise me is that I don't see information about the message
that is put in the reporting queue.
QUESTION : Is there an issue with try/catch explaining why this info
is not put by the tracer in the log or the fact that we use a POJO
before to call the activemq placing the message in a queue ?
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
