[
https://issues.apache.org/jira/browse/AMQ-8471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487868#comment-17487868
]
shrihari edited comment on AMQ-8471 at 2/7/22, 4:53 AM:
--------------------------------------------------------
Hi [~jbonofre]
PFA the output with and without the backquot character, the problem is that it
takes extra 30 seconds and also throws that the process doesn't exist.
With the backquot, the process remains as a stale, after issuing stop command,
the process still exists.
but without backquot it kills the process consuming extra 30 seconds, but it
says specified process doesn't exist which is the cause of concern to us.
!image-2022-02-07-10-21-19-913.png!
!image-2022-02-07-10-21-39-782.png!
was (Author: JIRAUSER284694):
Hi [~jbonofre]
PFA the output with and without the backquot character, the problem is with the
error message.
With the backquot, the process remains as a stale, but without backquot it
kills the process consuming extra 30 seconds, but it says specified process
doesn't exist.
!image-2022-02-07-10-21-19-913.png!
!image-2022-02-07-10-21-39-782.png!
> 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
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Attachments: image-2022-02-07-10-21-19-913.png,
> image-2022-02-07-10-21-39-782.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 AIX/linux 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 -eo "pid,args" | grep "\s*$activemq_pid\s.java"`" to RET="ps -eo
> "pid,args" | grep "\s$activemq_pid\s.*java""
> This will be inside checkRunning() function.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
