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

["Mitchell Hentges (JIRA)" <ji...@apache.org>]

Mitchell Hentges created AMQ-6927:
-------------------------------------

             Summary: Unix Shell Script "stop" doesn't work out-of-box
                 Key: AMQ-6927
                 URL: https://issues.apache.org/jira/browse/AMQ-6927
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMX
    Affects Versions: 5.15.3
         Environment: Amazon Linux distro. Java OpenJDK JRE 1.8.0_161.
            Reporter: Mitchell Hentges


I followed the ["Unix Shell Script"|http://activemq.apache.org/unix-shell-script.html] 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:


{noformat}
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'
{noformat}

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

{noformat}
        <managementContext>
            <managementContext createConnector="false"/>
        </managementContext>
{noformat}

-----

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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)