[
https://issues.apache.org/jira/browse/AMQ-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Lumpkin updated AMQ-4925:
--------------------------------
Description:
The 'JMXConnectorFactory(url, null).connect() ' request returns as if it is
successful; however, it is not.
The RMI stub is being returned, even though this broker is not the master, in a
master-slave relationship.
Basically, a JMXConnection request against a slave broker returns as if the
request were successfull, even though subsequent JMXConnection requests,
followed by MBeanServerConnnection will fail.
Is this due to the RMI stub being returned even though the the broker is a
slave, and not able to service any requests?
In other words, the JMX console is active before the server is a master, as
determined by message a (below) appearing in the log prior to message b:
a: | INFO | JMX consoles can connect to service
b: | INFO | Becoming the master on dataSource.....
My question is should the JMX activation logic be moved to a point after a
broker is a master?
was:
The 'JMXConnectorFactory(url, null).connect() 'requestreturns as if it is
successful; however, it is not.
I have a master/slave relationship and when the normal master is the slave, and
not satisfying requests, the above command returns as if all is well and then
later fails on an 'MBeanServerConnection' request.
Is this due to the RMI stub being returned even though the the broker is a
slave, and not able to service any requests?
I was wondering if a check should be made so that the connection, in this
instance, is an exception?
> JMXConnectorFactory Returns Remote RMI Stub Even When Message Broker Is Not
> The Master
> --------------------------------------------------------------------------------------
>
> Key: AMQ-4925
> URL: https://issues.apache.org/jira/browse/AMQ-4925
> Project: ActiveMQ
> Issue Type: Wish
> Components: JMX
> Affects Versions: 5.9.0
> Environment: Linux
> Reporter: Jerome Lumpkin
> Priority: Minor
>
> The 'JMXConnectorFactory(url, null).connect() ' request returns as if it is
> successful; however, it is not.
> The RMI stub is being returned, even though this broker is not the master, in
> a master-slave relationship.
> Basically, a JMXConnection request against a slave broker returns as if the
> request were successfull, even though subsequent JMXConnection requests,
> followed by MBeanServerConnnection will fail.
> Is this due to the RMI stub being returned even though the the broker is a
> slave, and not able to service any requests?
> In other words, the JMX console is active before the server is a master, as
> determined by message a (below) appearing in the log prior to message b:
> a: | INFO | JMX consoles can connect to service
> b: | INFO | Becoming the master on dataSource.....
> My question is should the JMX activation logic be moved to a point after a
> broker is a master?
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
