You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/15 08:26:00 UTC

[jira] [Commented] (KARAF-5206) Karaf doesn't start after not clean reboot, because stored PID corresponds to running process

    [ https://issues.apache.org/jira/browse/KARAF-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050149#comment-16050149 ] 

ASF GitHub Bot commented on KARAF-5206:
---------------------------------------

GitHub user valdar opened a pull request:

    https://github.com/apache/karaf/pull/319

    [KARAF-5206] modified karaf and karaf.bat scripts to check pid and pr…

    …ocess name upon cheking for already running instances

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/valdar/karaf KARAF-5206

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/karaf/pull/319.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #319
    
----
commit c5941764ee5db731e24ad3949a14db5f60537d82
Author: Andrea Tarocchi <at...@redhat.com>
Date:   2017-06-15T08:12:01Z

    [KARAF-5206] modified karaf and karaf.bat scripts to check pid and process name upon cheking for already running instances

----


> Karaf doesn't start after not clean reboot, because stored PID corresponds to running process
> ---------------------------------------------------------------------------------------------
>
>                 Key: KARAF-5206
>                 URL: https://issues.apache.org/jira/browse/KARAF-5206
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 4.1.1
>            Reporter: Andrea Tarocchi
>
> If Karaf is shut down in a disorderly way – a VM is terminated for example, or there is a power failure, then on occasion it will fail to restart when the host starts. The problem is that the stored PID in instance.properties might correspond to that of a process that is already running but is not the karaf one.
> step to reproduce it:
> - Find a PID from an already running process (which is not the karaf one) and place it in *instances/instance.properties* file as value of *item.0.pid* key
> - Try to start karaf with *bin/karaf* (or bin karaf.bat) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)