commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (JIRA)" <>
Subject [jira] [Resolved] (DAEMON-281) Jsvc not loading correct shared lib for Java 7 on MacOS
Date Wed, 06 Mar 2013 10:36:15 GMT


Mladen Turk resolved DAEMON-281.

       Resolution: Fixed
    Fix Version/s: 1.0.14

Fixed in the SVN with r1453272.
Will be part of next release.
> Jsvc not loading correct shared lib for Java 7 on MacOS
> -------------------------------------------------------
>                 Key: DAEMON-281
>                 URL:
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Jsvc
>    Affects Versions: 1.0.13
>         Environment: MacOS 10.8.2 with Java 7:
> $ java -version
> java version "1.7.0_15"
> Java(TM) SE Runtime Environment (build 1.7.0_15-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
>            Reporter: Ian Emmons
>             Fix For: 1.0.14
> When I try to run my program via jsvc, it complains:
> Cannot find any VM in Java Home <<JAVA_HOME>>
> Cannot locate JVM library file
> where <<JAVA_HOME>> is set to
> /Library/Java/JavaVirtualMachines/jdk1.7.0_15.jdk/Contents/Home
> The -debug switch shows jsvc searching for several shared libraries in the folder
>   $JAVA_HOME/../Libraries/
> However, with Java 1.7 this folder does not exist, and jsvc should be trying to load
>   $JAVA_HOME/jre/lib/server/libjvm.dylib
> If I change JAVA_HOME to point to Apple's Java 1.6, then jsvc successfully finds the
JVM shared library.
> Note:  I built jsvc myself with no problems, and the output of the build makes it clear
that it used the Java 7 JNI headers in the compilation.
> Background:  Apple has deprecated Java 1.6.  It not longer is present unless the user
explicitly installs it, and recent OS updates have disabled the browser plugin and removed
the Java control panel.  Apple is pushing customers toward's Oracle's Java 1.7.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message