[
https://issues.apache.org/jira/browse/KARAF-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050181#comment-16050181
]
ASF subversion and git services commented on KARAF-5206:
--------------------------------------------------------
Commit be9e2719ed0be8c30faf01237b29c83d4ea40bcd in karaf's branch
refs/heads/karaf-4.1.x from [~valdar]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=be9e271 ]
[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
> Assignee: Andrea Cosentino
> Fix For: 4.2.0, 4.1.2
>
>
> 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)
