activemq stop can fail if the broker is not using the default JMX port 1099
---------------------------------------------------------------------------
Key: AMQ-2976
URL: https://issues.apache.org/activemq/browse/AMQ-2976
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.0
Reporter: Adrian Trenaman
If I run ActiveMQ on my local Linux box using the Sun JDK, I note that when I
stop the broker with 'activemq stop' then it stops OK - it uses the stored PID
from the pidfile to connect to the broker (presumably using JMX!) and do a
graceful shutdown.
{code}
Connecting to pid: 13175
Stopping broker: amq01
{code}
However, I have a colleague using ActiveMQ with the IBM JDK, When he does
'activemq stop', it doesn't attempt to use the PID. Instead, it uses the
default JMX RMI connector string.
{code}
Connecting to JMX URL:
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
{code}
Problem is that this broker is listening for JMX on a different port number!
So, the attempt to stop the broker fails with a java.rmi.ConnectionException.
Just wondering if anyone has seen anything like this?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
