Re: TransportListerner onCommand

As you know, I am using broker network + failover for DR. I use transportListerner such that I can get some info when failover happens. I can understand transportResumed, onException stuff, but have no idea why onCommand is there. What's it supposed to do? Anything I need to take care of after mes

Re: TransportListerner onCommand

Thank you very much, this really helps me -- View this message in context: http://activemq.2283324.n4.nabble.com/TransportListerner-onCommand-tp4680911p4681046.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

TransportListerner onCommand

Hi guys. I am using failover protocol with static discovery, along with TransportListerner for transfer/failover detection. There is an onCommand() method. I understand this method delivers transport info and on consumer side is used to count messages received. Are there some typical usage beyo

Re: delay failover transfer

Thanks Petter. I tried the configs and they work as supposed. What I am worrying is, when the main broker is down for some reason, and clients are transferring to the backup one. During the transfer, if I start the main again, the clients begin to come back to the main one. In such a case, lag cou

Re: delay failover transfer

The network of my firm was built a couple of years ago, whose bandwidth is limited. We are afraid there could be some lag/jam in data transmission. Say, a client losses contact with the broker due to an occasional network lag, but the connection could come to life after 2/3 seconds. In this case, w

Re: delay failover transfer

I tried that one, but it didnt make a difference. With my observation, this configuration controls how many times a client tries to reconnect to the main broker after it already transfers to the backup one. Did I miss anything? I just add startupMaxReconnectAttempts right after failover urls on cli

delay failover transfer

Hi guys. I am using failover + broker network for disaster transfer. So i config two brokers using static network and on client side i specifies failover like this. failover:(tcp://localhost:61617,tcp://localhost:61618)?randomize=false) My question is, when i kill the main broker, I may need the

Re: Persist Last Image

Thanks for the reply. Shall i use persist + durable subs. After the broker failover and restarts, the subs should send a query to the broker for the last image? -- View this message in context: http://activemq.2283324.n4.nabble.com/Persist-Last-Image-tp4680193p4680300.html Sent from the Activ

Persist Last Image

Hi all. Recently we have such a need in our project. We would like to always persist the last sent message. So in case of a system failure, we would be able to recover the message and resend to the consumer once they are reconnected. My plan was to save the message right after it was sent and by d

recover last image after broker failover

hi there. i just run into such a problem. when the broker failover and after i restart it, i would like the broker to recover all the topics it held and the last image it sent. It would be like this. broker starts... M0, M1, M2, shut down broker for sometime restart broker and recover topics an