You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2022/01/10 16:04:00 UTC
[jira] [Commented] (AMQ-8383) ActiveMQ status command - 5.16.2 version
[ https://issues.apache.org/jira/browse/AMQ-8383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472123#comment-17472123 ]
Jean-Baptiste Onofré commented on AMQ-8383:
-------------------------------------------
It's already fixed and it will be included in AMQ 5.16.4.
> ActiveMQ status command - 5.16.2 version
> ----------------------------------------
>
> Key: AMQ-8383
> URL: https://issues.apache.org/jira/browse/AMQ-8383
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.16.2
> Environment: UNIX
> Reporter: Dhanasekar
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.17.0, 5.16.4
>
>
> activeMQ status command is not working as expected in 5.16.2 version
>
> Earlier or working version (before 5.16 version) -> {color:#ff0000}ps -p $ACTIVEMQ_PID]"{color} | grep java
> with V5.1.6.2 version command changed like below - > {color:#ff0000}ps -o "pid,arg"{color} .....
>
> as per UNIX ps command documentation ps -o command will show current terminal process only.
>
> Problematic scenario: (steps to recreate issue)
>
> Step 1 : open UNIX Terminal 1
> Step 2 : Start activeMQ from terminal 1, activemq started successfully and status shows correctly (RUNNING) in terminal 1
> Step 3 : open UNIX terminal 2
> Step 4 : Check status from terminal 2, activemq status command will show as activemq is down.
> Step 5 : Can start activemq again from terminal 2, this is causing levedb corruption and other issue because multiple process
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)