Message redelivery and transports...

[noelo]

Just a question regarding message redelivery over different transports.

Consider the scenario where you have multiple instances of the same service running on different machines in a cluster.
Each instance is configured to use a different transport i.e JMS, FTP, SQL....
If a client invokes the service using a async call and the service instance chosen is using the FTP transport but there is a problem with FTP, will the message be immediately written to the DLQ (assuming its configured), or will other services instances be tried first.

Also if the message is put on the DLQ, when the retry happens, is the initial call re-attempted or is a new service endpoint chosen ?

thanks for your help...
regards
Noel

[marklittle]

This will depend upon the "load balancer" policy that you're using, but if you go with the ones that ship with the esb then it'll try to send to the other instances if the initial send fails.

[noelo]

Hi Mark,
Apologies but I am still a bit confused. Will it go to the DLQ first or will the other service instances be tried first and then message the moved to the DLQ to await further retries.

[marklittle]

It goes to the DLQ after all possible options have been tried. Check out the docs and if you think they are not clear then please raise a JIRA against them.