[
https://issues.apache.org/activemq/browse/AMQ-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60252#action_60252
]
David Bresson commented on AMQ-2785:
------------------------------------
If I could set that with a java property, I suppose.
The crux of problem is that if you provide the web console with a list of jmx
urls in a cluster, and the first in that list is up as a jdbc slave, the web
console is useless and returns 500 errors.
> RemoteJMXBrokerFacade does not intelligently choose the correct URL when
> brokers use jdbcPersistenceAdapter failover
> --------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2785
> URL: https://issues.apache.org/activemq/browse/AMQ-2785
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.1
> Reporter: David Bresson
>
> createConnection() from RemoteJMXBrokerFacade takes a collection of jmx urls,
> connecting to them in order, querying for brokers, and returning the first to
> have a broker (optionally requiring a matching name).
> With a jdbcPersistenceAdapter cluster of brokers, this does not distinguish
> between the fully initialized master and the waiting slaves.
> Each broker discovered should be queried for a value or values that only a
> fully functional broker has.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
