Hi, I am considering ActiveMQ for data delivery in a setup where client and server exchange data. I would like to place ActiveMQ between the client and server. The requirements are as follows
1) both clients and servers need to send and receive data 2) client needs to be able to produce messages even when not connected to the network 3) messages sent by one side need to be received by the other side in order (considering priorities) 4) messages should not get lost (system is able to recover from small message loss but it is better to avoid it) Now first thing that comes to mind is that every client and server will have queue which it will consume from and when it will want to send message to someone it will simply place message to the queue consumed by the recipient. There would be single ActiveMQ server (with persistence enabled) running and everyone would connect to it. This addresses everything except for second requirement. To address the requirement no2 I am thinking about adding embedded persistent broker (vm:// protocol) on the client side. Considered it to be only failover but then I am not sure about order of messages at the time when client gets online (queued in broker vs. new ones) Now the questions are: * is this a proper way to do it? * if it is the way to go then what is the best way to get data from the vm broker to the server? Should I configure it as a network of brokers? Would that be stable enough? I would like to avoid having thread to copy data between the brokers thanks Tono -- View this message in context: http://activemq.2283324.n4.nabble.com/Offline-message-producers-tp4685011.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
