In fact in case I was not clear enough, the activemqweb application now
behave correctly (meaning does not say "slave" whichever node I am querying
but forwards to the active one) with the new servicemix (5.1.4) which use
ActiveMQ 5.10.
Now I don't even know where are the real source code of this
We have a serviceMix 4.3 which use the same ActiveMQ (embedded) and we also
have the issue.
In another deployment, we use ActiveMQ 5.10.x and apparently the activemqweb
is working better (still few bugs when you browse queue from the slave
instance) but quite more stable anyway.
We plan to migrat
