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] [Resolved] (KARAF-3564) bin/stop fails for slave in case of Lock strategies
Date Tue, 31 Mar 2015 05:58:54 GMT

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

Jean-Baptiste Onofré resolved KARAF-3564.
-----------------------------------------
    Resolution: Fixed

> bin/stop fails for slave in case of Lock strategies
> ---------------------------------------------------
>
>                 Key: KARAF-3564
>                 URL: https://issues.apache.org/jira/browse/KARAF-3564
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 2.3.7
>            Reporter: Paolo Antinori
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.4.2, 2.3.11
>
>
> {{bin/stop}} invokes {{org.apache.karaf.main.Stop}}
> https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Stop.java
> {{Stop}} reads the socket port it has to connect to from a file: {{data/port}} is the
default.
> But when a Lock strategy is in place, and the instance is the one that could not obtain
the lock, the shutdown socket is never started:
> https://github.com/apache/karaf/blob/karaf-2.3.x/main/src/main/java/org/apache/karaf/main/Main.java#L1411-L1415
> {code}
>  if (lock.lock()) {
>     if (lockLogged) {
>        LOG.info("Lock acquired.");
>     }
>     setupShutdown(props);
> {code}
> and the Shutdown socket is created only in {{setupShutdown()}}
> A workaround is to use {{bin/client -u admin -p admin 'shutdown --force'}}
> It should be safe to move the invocation of {{setupShutdown}} outside the {{if(lock.lock())}}
branch
> cross reference: https://issues.jboss.org/browse/ENTESB-2417



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

Mime
View raw message