[AMQ-6927] Unix Shell Script "stop" doesn't work out-of-box

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.15.3
• Component/s: JMX

Environment

Amazon Linux distro. Java OpenJDK JRE 1.8.0_161.

• Assignee: Unassigned
• Reporter: Mitchell Hentges
• Created: 14/Mar/18 17:52
• Updated: 12/Oct/20 18:53

Description

I followed the "Unix Shell Script" documentation, but once I was done, when I'd stop activemq with the init script (service activemq stop) it would delay for a long time with the following output:

Connecting to pid: 23553
INFO: failed to resolve jmxUrl for pid:23553, using default JMX url
Connecting to JMX URL: service:jmx:rmi:///jndi/rmi://localhost:61099/jmxrmi
INFO: Broker not available at: service:jmx:rmi:///jndi/rmi://localhost:61099/jmxrmi
...............................
INFO: Regular shutdown not successful,  sending SIGKILL to process
INFO: sending SIGKILL to pid '23553'

I found out that this is because, by default, JMX isn't started - in conf/activemq.xml, createConnector is false:

        <managementContext>
            <managementContext createConnector="false"/>
        </managementContext>

---

In summary: Out of the box, the activemq stop script functionality doesn't work as expected. Either JMX should be enabled by default (there's probably a reason why it isn't), or activemq shouldn't try to connect to JMX on-stop by default.

I tried to edit the documentation to add a note, but fresh JIRA accounts don't have permissions.