You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Fabian Lange (JIRA)" <ji...@apache.org> on 2017/11/13 21:22:00 UTC
[jira] [Created] (KARAF-5481) NullPointer when invoking
Karaf.stop()
Fabian Lange created KARAF-5481:
-----------------------------------
Summary: NullPointer when invoking Karaf.stop()
Key: KARAF-5481
URL: https://issues.apache.org/jira/browse/KARAF-5481
Project: Karaf
Issue Type: Bug
Reporter: Fabian Lange
customer sees this when they run a package upgrade of our karaf distribution
```Nov 12 04:15:54 karaf[21250]: Exception in thread "main" java.lang.NullPointerException
Nov 12 04:15:54 karaf[21250]: at org.apache.karaf.main.Stop.main(Stop.java:60)```
https://github.com/apache/karaf/blob/master/main/src/main/java/org/apache/karaf/main/Stop.java#L60
We have the feeling this is kind of a race condition between sending the stop command and deleting the file which contains the stop command.
whats your thoughts? shouldn'T we at least ensure that `config.shutdownCommand` is non null?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)