[
https://issues.apache.org/jira/browse/ARTEMIS-4630?focusedWorklogId=903907&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903907
]
ASF GitHub Bot logged work on ARTEMIS-4630:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Feb/24 16:11
Start Date: 06/Feb/24 16:11
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #4811:
URL:
https://github.com/apache/activemq-artemis/pull/4811#issuecomment-1930180134
(I actually only cherry-picked the second commit earlier, I thought the
first was the same as yesterdays.)
Reverting seems reasonable based on what you just said. FWIW past 'check the
process' stuff I have seen tended to just add something as a marker to the
command run originally, so it could be looked for later.
Issue Time Tracking
-------------------
Worklog Id: (was: 903907)
Time Spent: 1h 50m (was: 1h 40m)
> 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 50m
> 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)
