Thanks Bruce,
If I put this configuration
public void configure() {
from(SERVICE_IN).errorHandler(deadLetterChannel(ERROR_IN).maximumRedeliveries(0)).to(BEAN_IN);
}
instead of this
public void configure() {
errorHandler(deadLetterChannel(ERROR_IN));
from(SERVICE_IN).to(BEAN_IN);
}
then it works.
I looked into wiretap pattern but I think it won't fulfill my requirements.
What I want is if any error comes while delivering the message then that
message should be sent to an error queue.
Cant we have something like this:
1)A kind of listener say errorListener which listen to each and every
message which flow through NMR
2)If everything goes fine the message will be sent to its destination
3)If any error occurs the error will be analyzed to see what kind of error
it is.
a)If it is an error occurred because the destination application where the
message was supposed to be sent is down, then the request message will be
put in a queue say queue:requestpendingQueue. So that it can be processed
later.
b)Every application is up and and running. The message moves from source to
destination safely. If the error occurred because the message content is not
as expected (fault in message) by the destination, then the error message
should be analyzed. If the destination for the message is say application1
the the message should be sent to queue:application1.
If the destination for the message is say application2 the the message
should be sent to queue:application2
Is there a way to do this. Please help
Regard,
-Pratibha
--
View this message in context:
http://www.nabble.com/Does-Servicemix-provides-any-error-handling-mechanism--tp17271816p17355863.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
