You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/02/02 16:02:00 UTC
[jira] [Work logged] (ARTEMIS-4630) AMQ Service status is not validating if the pid is from Artemis
[ https://issues.apache.org/jira/browse/ARTEMIS-4630?focusedWorklogId=903372&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903372 ]
ASF GitHub Bot logged work on ARTEMIS-4630:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Feb/24 16:01
Start Date: 02/Feb/24 16:01
Worklog Time Spent: 10m
Work Description: angelogalvao opened a new pull request, #4801:
URL: https://github.com/apache/activemq-artemis/pull/4801
In rare cases the status is returning 'running' to a process that is not Artemis. It was create a extra level of verification by validating if the running process working directory is the
same of ${ARTEMIS_INSTANCE}.
Issue Time Tracking
-------------------
Worklog Id: (was: 903372)
Remaining Estimate: 0h
Time Spent: 10m
> AMQ Service status is not validating if the pid is from Artemis
> ---------------------------------------------------------------
>
> Key: ARTEMIS-4630
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4630
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.32.0
> Reporter: Angelo Galvão
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In a rare condition, an old artemis.pid file is pointing to an existing process that is not Artemis, causing the provisioning tools to believe that Artemis process is running.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)