Jms uses a socket, but it sends an ack to the client that the message was sent, and that's that's guaruntees that if delivery fails, an exception is thrown. Requesting and waiting for a response message is a lot trickier, but there are a few different patterns for using JMS in RPC situations. I use a heartbeat pattern which allows a client to timeout if there's no service handling messages.
Now that there's a fully async client in Java, I may figure out how to take advantage of that. -- Jeff DeCew On Jul 25, 2010 7:05 PM, "Qing Yan" <[email protected]> wrote: hum..doesn't the jms transport need a thrift like reliable comm mechanism beneath it? On 7/25/10, Jeffrey DeCew <[email protected]> wrote: > JMS can provide delivery guaruntees. I wr...
