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
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.
That method, onCommand(), is called for every transport "command"; commands
are the unit of the ActiveMQ openwire protocol (not sure what happens with
non-openwire). So, it is called with tremendous detail that is very highly
activemq-internal-specific. And it is called with high frequency on bus
onCommand is used to process command messages after they've been
unmarshalled off the wire... what are you trying to do specifically?
On Mon, May 5, 2014 at 10:31 PM, Charels_Li wrote:
> Hi guys.
>
> I am using failover protocol with static discovery, along with
> TransportListerner for transfer/
