[
https://issues.apache.org/jira/browse/ARTEMIS-4630?focusedWorklogId=903897&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903897
]
ASF GitHub Bot logged work on ARTEMIS-4630:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Feb/24 15:27
Start Date: 06/Feb/24 15:27
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4811:
URL:
https://github.com/apache/activemq-artemis/pull/4811#issuecomment-1930048938
After further investigation I don't think this solution is valid. The
problem is that `lsof -a -d cwd -p <pid>` will report the directory from which
the `artemis-service` script _was executed_. However, this script can be
invoked from *any* directory. Therefore, it's very easy to break the script
with this change such that it actually starts the broker but reports that it
didn't and then continues to report the wrong status.
I will revert these commits soon.
Issue Time Tracking
-------------------
Worklog Id: (was: 903897)
Time Spent: 1h 40m (was: 1.5h)
> 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
> Fix For: 2.33.0
>
> Time Spent: 1h 40m
> 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)
