You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "shrihari (Jira)" <ji...@apache.org> on 2022/02/04 09:03:00 UTC

[jira] [Created] (AMQ-8471) activemq stop command fails with no or outdated process id

shrihari created AMQ-8471:
-----------------------------

             Summary: activemq stop command fails with no or outdated process id
                 Key: AMQ-8471
                 URL: https://issues.apache.org/jira/browse/AMQ-8471
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.16.2
            Reporter: shrihari


In some AIX/Linux environments, the activemq stop command fails with the below error. 

bash-4.4# ./activemq stop
INFO: Loading '/AMQ/message-broker/bin/env'
INFO: Using java '/usr/java8_64/bin/java'
ERROR: No or outdated process id in '/AMQ/message-broker//data/activemq.pid'

INFO: Removing /AMQ/message-broker//data/activemq.pid

 

The fix provided in https://issues.apache.org/jira/browse/AMQ-8425 doesn't work in such environments as the issue is not due to the user/terminal instance.

 

Workaround: 

Some linux/AIX environments are highly sensitive to the *acute/backquot* *character `* 

Backquot character reference : [https://www.computerhope.com/jargon/b/backquot.htm]

Update the file <AMQ_HOME>/message-broker/bin/activemq as below :

Change the line by removing backquot character :

RET="`ps -p "${ACTIVEMQ_PID}"|grep java`" to RET="ps -p ${ACTIVEMQ_PID}|grep java"

This will be inside checkRunning() function.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)