So you can always register an http-callback in the garb of a message listener during the time of msg publication. When the client execs your listener and runs the callback, it can do http post/get, etc to whatever other broker url you want to route the msg to.
I am not sure what multiple brokers are buying you. Ideally, in a distributed system, you do not want to disperse components with HA requirements, like that. Destinations and listeners are much cheaper than brokers and ActiveMQ has great jmx support to manipulate them at runtime. Also, if you can describe your use cases for msgng, that might help too. Sent from my iPhone On Aug 20, 2012, at 9:28, zackhasit <zackha...@gmail.com> wrote: > I looked at > http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html > > However I have a question on this. I have multiple clients and a servers. > Each have their own local broker. Client needs to send message to server's > broker and setJMSreply to it's own (client's) local broker. > > Idea being that receives by client and servers are done on their local > brokers but sending is done to remote brokers. That way clients do not have > to check responses from multiple server brokers in round robin manner. > > Example: > 1. Client sends message to servers broker setting up response dest to be > client's broker's ip > client (IP:xx.xx.xx.xx) --------->server's > broker(IP:yy.yy.yy.yy)--->server(IP:yy.yy.yy.yy) > > 2. Server responds back to client's local broker. > client (IP:xx.xx.xx.xx) <----client' > broker(IP:xx.xx.xx.xx)<---------server(IP:yy.yy.yy.yy) > > Is it possible today ? How is this achieved via code in example above? I > don't want brokers to talk to each other because I would like to know when > other side is down right away. > > Thanks > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Implementing-Request-Response-mechanism-tp4655304.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
