Core bridges and guaranteed delivery

[lostvicking]

Hi,

We've implemented a core bridge and I would like to find out more about guaranteed delivery when using bridges. I couldn't find much on this topic in the docs -- at least not in the context of bridging, Ideally I would like a message that has been taken off the source queue to be returned to it in the event that it is not delivered to the source queue for any reason, be it that the target queue does not exist or the target server instance is down or whatever. Is this a reasonable expectation to have for core bridges -- we have a requirement that messages cannot be lost for any reason.

Regards and thanks

Victor

[ataylor]

as per my other post, messages are routed to an address not a queue. if the server is down then the message will be held in the store and forward queue of the bridge itself.

[lostvicking]

Thanks, Andy. So in my understanding then I loose the benefit of guaranteed delivery when using bridges because as you say it's routed to an address instead of a queue?

[ataylor]

no you don't lose any guarantees. the guarantee is between a source queue and a target address, if there were 2 queues bound to this address then they would both receive the message as part of the guarantee, this is how a core bridge works. Try not to think JMS this is our own core API.