[ 
https://issues.apache.org/jira/browse/KARAF-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul McCulloch updated KARAF-7828:
----------------------------------
    Description: 
Originally reported as "Karaf slave instance does not write pid or port file 
until it becomes master" KARAF-5798

Testing and a look at the code only the issue with the pid file was fixed. The 
port file is still only written (InstanceHelper#setupShutdown) from 
org.apache.karaf.main.Main - KarafLockCallback#lockAcquired 

The impact of this is that the "stop" command fails with the error "shutdown 
port file doesn't exist. The container is not running" if the node doesn't have 
the lock.

  was:
Originally reported as "Karaf slave instance does not write pid or port file 
until it becomes master" KARAF-5798 

Testing and a look at the code only the issue with the pid file was fixed. The 
port file is still only written (InstanceHelper#setupShutdown) from 
KarafLockCallback#lockAcquired 

The impact of this is that the "stop" command fails with the error "shutdown 
port file doesn't exist. The container is not running" if the node doesn't have 
the lock.


> Karaf slave instance does not write port file until it becomes master
> ---------------------------------------------------------------------
>
>                 Key: KARAF-7828
>                 URL: https://issues.apache.org/jira/browse/KARAF-7828
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.4.4, 4.4.5
>            Reporter: Paul McCulloch
>            Priority: Major
>
> Originally reported as "Karaf slave instance does not write pid or port file 
> until it becomes master" KARAF-5798
> Testing and a look at the code only the issue with the pid file was fixed. 
> The port file is still only written (InstanceHelper#setupShutdown) from 
> org.apache.karaf.main.Main - KarafLockCallback#lockAcquired 
> The impact of this is that the "stop" command fails with the error "shutdown 
> port file doesn't exist. The container is not running" if the node doesn't 
> have the lock.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to