Quantcast

[GitHub] karaf pull request #292: [KARAF-4260] Rename Service Wrapper pid file to not...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] karaf pull request #292: [KARAF-4260] Rename Service Wrapper pid file to not...

earcam-2
GitHub user vladimirfx opened a pull request:

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

    [KARAF-4260] Rename Service Wrapper pid file to not clash with Karaf JVM pid file

    When service name is 'karaf' PID file created by Service Wrapper clashes with PID file created from Karaf JVM. As result service is started, PID file overridden by Karaf Java code and service can't be controlled by OS "service" command.
   
    Example output:
   
    ```
    [root@smosesb02 java]# service karaf stop
    Stopping karaf...
    Removed stale pid file: /opt/apache-karaf-4.0.9-SNAPSHOT/karaf.pid
    karaf was not running.
   
    [root@smosesb02 java]# ps -ef | grep java
    root      5184 17242  0 12:24 pts/0    00:00:00 grep java
    karaf    27269 27267 24 12:19 ?        00:01:06 /usr/java/jdk1.8.0_92/bin/java -Dkaraf.home=/opt/apache-karaf-4.0.9-SNAPSHOT -Dkaraf.base=/opt/apache-karaf-4.0.9-SNAPSHOT -Dkaraf.data=/opt/apache-karaf-4.0.9-SNAPSHOT/data -Dkaraf.etc=/opt/apache-karaf-4.0.9-SNAPSHOT/etc -Dcom.sun.management.jmxremote -Dkaraf.startLocalConsole=false -Dkaraf.startRemoteShell=true -Djava.endorsed.dirs=/usr/java/jdk1.8.0_92/jre/lib/endorsed:/usr/java/jdk1.8.0_92/lib/endorsed:/opt/apache-karaf-4.0.9-SNAPSHOT/lib/endorsed -Djava.ext.dirs=/usr/java/jdk1.8.0_92/jre/lib/ext:/usr/java/jdk1.8.0_92/lib/ext:/opt/apache-karaf-4.0.9-SNAPSHOT/lib/ext -Djava.io.tmpdir=/opt/apache-karaf-4.0.9-SNAPSHOT/data/tmp -XX:MaxPermSize=128m -Djava.io.tmpdir=/opt/apache-karaf-4.0.9-SNAPSHOT/data/tmp -XX:-HeapDumpOnOutOfMemoryError -Xms512m -Xmx512m -Djava.library.path=/opt/apache-karaf-4.0.9-SNAPSHOT/lib/wrapper/ -classpath /opt/apache-karaf-4.0.9-SNAPSHOT/lib/boot/org.apache.karaf.diagnostic.boot-4.0.8.CITC_8.jar:/opt/apach
 e-karaf-4.0.9-SNAPSHOT/lib/boot/org.apache.karaf.jaas.boot-4.0.8.CITC_8.jar:/opt/apache-karaf-4.0.9-SNAPSHOT/lib/boot/org.osgi.core-6.0.0.jar:/opt/apache-karaf-4.0.9-SNAPSHOT/lib/boot/org.apache.karaf.main-4.0.8.CITC_8.jar:/opt/apache-karaf-4.0.9-SNAPSHOT/lib/wrapper/karaf-wrapper-main.jar:/opt/apache-karaf-4.0.9-SNAPSHOT/lib/wrapper/karaf-wrapper.jar -Dwrapper.key=755NX7xqehWEZrWs -Dwrapper.port=32001 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=27267 -Dwrapper.version=3.2.3 -Dwrapper.native_library=wrapper -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=30 -Dwrapper.jvmid=1 org.apache.karaf.wrapper.internal.service.Main
   
    ```

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

    $ git pull https://github.com/cit-consulting/karaf KARAF-4260

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

    https://github.com/apache/karaf/pull/292.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 #292
   
----
commit e6dc731f86440dd19c466c20afc83ba36fb62c16
Author: Vladimir Konkov <[hidden email]>
Date:   2017-03-27T08:30:52Z

    [KARAF-4260] Rename Service Wrapper pid file to not clash with Karaf JVM pid file

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GitHub] karaf pull request #292: [KARAF-4260] Rename Service Wrapper pid file to not...

earcam-2
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Loading...