[
https://issues.apache.org/jira/browse/AMQ-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud BRAND updated AMQ-3303:
------------------------------
Attachment: RemoteJMXBrokerFacade.patch
This patch modifies findBrokers to only return brokers that are not slaves.
I don't know wether this is the ideal way of fixing the problem (in case the
RemoteJMXBrokerFacade is used elsewhere), but at least it fixes the webconsole.
> Standalone Webconsole crashes when accessing master-slave failover activeMQ
> ---------------------------------------------------------------------------
>
> Key: AMQ-3303
> URL: https://issues.apache.org/jira/browse/AMQ-3303
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMX
> Affects Versions: 5.5.0
> Environment: Webconsole running on tomcat 6 on ubuntu 10.04LTS with
> sun jdk.
> Options : webconsole.type=properties,
> webconsole.jms.url=failover:(tcp://activemq-1:61616,tcp://activemq-2:61616),
> webconsole.jms.user=xxxxxxxxxx, webconsole.jms.password=xxxxxxxxx,
> webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://activemq-1:11099/jmxrmi,service:jmx:rmi:///jndi/rmi://activemq-2:11099/jmxrmi,
> webconsole.jmx.user=xxxxxxxxxxx, webconsole.jmx.password=xxxxxxxxxxxxxxxx
> Reporter: Arnaud BRAND
> Priority: Minor
> Attachments: RemoteJMXBrokerFacade.patch
>
>
> Null pointer exception when accessing the JSPs if the first jmx server (here
> activemq-1) in the jmx url is the slave.
> findBrokers in RemoteJMXBrokerFacade finds the slave broker but accessing
> some of its attributes results in a NullPointerException.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
