[
https://issues.apache.org/jira/browse/ARTEMIS-4630?focusedWorklogId=903923&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903923
]
ASF GitHub Bot logged work on ARTEMIS-4630:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Feb/24 17:21
Start Date: 06/Feb/24 17:21
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4811:
URL:
https://github.com/apache/activemq-artemis/pull/4811#issuecomment-1930411947
These commits have been reverted.
@angelogalvao, I think if we want to address this problem we need to
determine _how_ the wrong pid made it into `artemis.pid` in the first place.
Issue Time Tracking
-------------------
Worklog Id: (was: 903923)
Time Spent: 2h (was: 1h 50m)
> 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: 2h
> 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)
