JMS Proxy to Web Service Problem

Question

Hi All,
I have a JMS proxy that routes messages to a web service. I have set the delivery failure parameters on the JMS queue. When a message is put onto the queue and there is a problem within the message flow proper, the message is retried the appropriate number of times and put onto the Error Destination queue as necessary. However, if there is a problem calling the web service, message delivery is NOT retried, the message is NOT put onto the Error Destination queue, and the message is lost. The web service itself isn't throwing a SOAP Fault, but the business service can't reach the web service (firewall issue). My Route Error Handler in the message flow is hit and it performs a Reply With Failure.
Can anyone please explain to me if this is by design and, if so, why? Also, how does a person work around this? I need the message to be retried. I understand that a web service cannot participate in an XA transaction, but it seems to me any failure within the message flow should cause a retry on the JMS queue.
Thanks.
Edited by mvcg at 06/11/2008 1:57 PM

Answer 1

You should remove the Route Node since it should only be used in HttpProxy.
Instead use just the request pipeline for your routing.
if (condition1)
Service Callout (or publish) to Service1
else if (condition2)
Service Callout (or publish) to Service2
else
Rasie error?
You shouldn't need to reply with failure. Any errors in the service callout or publish should go to exception handling if you use QoS exactly-once.