karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-4330) Instance script doesn't return correct PID number if root instance is started two times
Date Tue, 16 Feb 2016 15:10:18 GMT

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

Jean-Baptiste Onofré commented on KARAF-4330:
---------------------------------------------

This change breaks the following use case (that I already fixed).

Let say, you rename the root instance, changing the name property in etc/system.properties.

Then, you start the root instance, you will see:

{code}
karaf@test()> instance:list
SSH Port | SSH Host | RMI Registry | RMI Registry Host | RMI Server | RMI Server Host | State
  | PID | Name
------------------------------------------------------------------------------------------------------------
    8101 |  0.0.0.0 |         1099 |           0.0.0.0 |      44444 |         0.0.0.0 | Stopped
| 0   | root
{code}

1. the name is not correct (it's not root, it's test for instance)
2. the status is not correct (it's not stopped, but started)

> Instance script doesn't return correct PID number if root instance is started two times
> ---------------------------------------------------------------------------------------
>
>                 Key: KARAF-4330
>                 URL: https://issues.apache.org/jira/browse/KARAF-4330
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 3.0.5, 4.0.4
>            Reporter: Andrea Cosentino
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: 4.1.0, 4.0.5, 3.0.7
>
>
> Use case:
> - Run a first Karaf root instance 
> - Check the PID with instance script
> - Run a second Karaf root instance, the script will hang as expected
> - Check the PID with the instance script. The PID will be the one from the second instance
even if it's not started correctly and it's hanging.
> - Kill the second instance
> - Check the PID with the instance script. The PID is now 0 and the status is stopped,
but we have the first instance currently running.
> This is not a normal workflow, I see. Starting two times the root instance or two instances
with the same instance name is not correct, but anyway it's something we should consider to
manage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message