Note that what you're asking for is not a fix, but rather an enhancement. Nothing's broken: the failover transport is successfully connecting to the first responsive URI in the list, it's just that that's not the behavior you actually want. Which simply means that the failover transport isn't the appropriate way to try to achieve this, even if it did happen to work in previous versions of ActiveMQ.
I personally don't know if anyone has implemented the capability you're hoping for, though you could easily go through all the resolved JIRA entries in each of the versions between your current one and the one you're planning to upgrade to, to determine whether the new version will have the capability. Tim On Jan 14, 2016 1:46 AM, "ruffp" <prx.l...@gmail.com> wrote: > 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 migrate our ActiveMQ to 5.10.x but in the meantime is there any > fix for the activemqweb on version 5.7? > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Issues-with-stand-alone-web-console-in-5-7-using-a-master-slave-architecture-tp4661538p4705980.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
