Handling Failed delivery ...

[Omar Atia <om...@its.ws>]

Dear All,

I have tcp end point that send messags to activemq , in turn activemq has one network element to update and another WS to update as well , if the request failed on the network element ,  then it will update the WS that operation failed , but in case WS server down and the system failed, a request updates on Network element and failed to update WS .

can we keep the message in the queue or later update the WS alone ?.

Note : result from Network element should update WS .

How can i handle such error using onexception handler to direct the messages in another activemq repository and re-update WS after exception disappeared .

thanks,
Omar Atia

Re: Handling Failed delivery ...

[Ashwin Karpe <ak...@fusesource.com>]

Hi, 

This is possible only if there is a queue that fronts the Web Service and
the service is transaction-aware. The Web Service needs to be a JMS Web
Service i.e. the WSDL Port instantiates a JMS Queue Listener and consumes
from a Queue that receives soap messages.  The result of the failure to
process a message by the web service should result in the message being
restored on the queue for future re-delivery, handled via a dead letter
queue or handled in a different way via an exception handler...

Hope this helps.

Cheers,

Ashwin...

-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com 

Blog: http://opensourceknowledge.blogspot.com 
---------------------------------------------------------
--
View this message in context: http://camel.465427.n5.nabble.com/Handling-Failed-delivery-tp5521828p5526326.html
Sent from the Camel - Users mailing list archive at Nabble.com.