|
From: Rob D. <rd...@ap...> - 2008-07-22 10:04:41
|
Hi All,
I have seen some users have the following issue with the JVM not
starting. (Here, we are using Vista 64, with Mule 1.4.4).
The suggested workaround include checking the path to the JVM is
correct, and ensuring the the correct permissions are set on the folders.
Here I have two processes using the wrapper - a client-from server, and
a client-to server.
The client-from-server launches fine:
wrapper config file:
C:\opt\appendium\mule\client-from-server\conf\wrapper-from-
server_client1.conf
Working directory set to: C:\opt\appendium\mule\client-from-server
--> Wrapper Started as Console
Using tick timer.
server listening on port 32001.
Launching a JVM...
command: "C:\opt\java\jdk1.5.0_16\bin\java" -Dmule.home="."
-Dmule.base="." -Dm2
.repo="%M2_REPO%" -Dappendium.env=Gonzales
-Dcom.sun.management.jmxremote=true -
Dcom.sun.management.jmxremote.port=15001
-Dcom.sun.management.jmxremote.ssl=fals
e -Dcom.sun.management.jmxremote.authenticate=false -Xms128m -Xmx600m
-Djava.lib
rary.path="%LD_LIBRARY_PATH%;./lib/boot" -classpath
".\bin/../conf;.\conf;./lib/
boot/commons-cli-1.0.jar;./lib/boot/mule-module-boot-1.4.4.jar;./lib/boot/wrappe
r-3.2.3.jar" -Dwrapper.key="hcHoizgB_iqKRoc5" -Dwrapper.port=32001
-Dwrapper.jvm
.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE"
-Dwrapper.pi
d=4744 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper"
-Dwrapper.cp
u.timeout="10" -Dwrapper.jvmid=1 org.mule.modules.boot.MuleBootstrap
-config .\c
onf\objectlab-esb-client-from-server-config_client1.xml
JVM started (PID=436)
However, the client-to-server does not:
wrapper config file:
C:\opt\appendium\mule\client-to-server\conf\wrapper-to-serv
er_client1.conf
Working directory set to: C:\opt\appendium\mule\client-to-server
--> Wrapper Started as Console
Using tick timer.
server listening on port 32001.
Launching a JVM...
command: "C:\opt\java\jdk1.5.0_16\bin\java" -Dmule.home="."
-Dmule.base="." -Dm2
.repo="%M2_REPO%" -Dappendium.env=Gonzales
-Dcom.sun.management.jmxremote=true -
Dcom.sun.management.jmxremote.port=16001
-Dcom.sun.management.jmxremote.ssl=fals
e -Dcom.sun.management.jmxremote.authenticate=false -Xms128m -Xmx256m
-Djava.lib
rary.path="%LD_LIBRARY_PATH%;./lib/boot" -classpath
".\bin/../conf;.\conf;./lib/
boot/commons-cli-1.0.jar;./lib/boot/mule-module-boot-1.4.4.jar;./lib/boot/wrappe
r-3.2.3.jar" -Dwrapper.key="9rKoYDt55Uk8QLuR" -Dwrapper.port=32001
-Dwrapper.jvm
.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE"
-Dwrapper.pi
d=3184 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper"
-Dwrapper.cp
u.timeout="10" -Dwrapper.jvmid=1 org.mule.modules.boot.MuleBootstrap
-config .\c
onf\objectlab-esb-client-to-server-config_client1.xml
Unable to execute Java command. Access is denied. (0x5)
"C:\opt\java\jdk1.5.0_16\bin\java" -Dmule.home="." -Dmule.base="."
-Dm2.repo
="%M2_REPO%" -Dappendium.env=Gonzales
-Dcom.sun.management.jmxremote=true -Dcom.
sun.management.jmxremote.port=16001
-Dcom.sun.management.jmxremote.ssl=false -Dc
om.sun.management.jmxremote.authenticate=false -Xms128m -Xmx256m
-Djava.library.
path="%LD_LIBRARY_PATH%;./lib/boot" -classpath
".\bin/../conf;.\conf;./lib/boot/
commons-cli-1.0.jar;./lib/boot/mule-module-boot-1.4.4.jar;./lib/boot/wrapper-3.2
.3.jar" -Dwrapper.key="9rKoYDt55Uk8QLuR" -Dwrapper.port=32001
-Dwrapper.jvm.port
.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE"
-Dwrapper.pid=318
4 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper"
-Dwrapper.cpu.tim
eout="10" -Dwrapper.jvmid=1 org.mule.modules.boot.MuleBootstrap -config
.\conf\o
bjectlab-esb-client-to-server-config_client1.xml
------------------------------------------------------------------------
Advice:
Access denied errors when attempting to launch the Java process are
usually caused by strict access permissions assigned to the directory
in which Java is installed.
------------------------------------------------------------------------
Critical error: wait for JVM process failed
Press any key to continue . . .
As far as I can tell, the parameters are identical (with the exception
of 'from/to paths') and the permissions are the same on all the folders.
Has anybody else come across this issue?
Many thanks
Rob.
--
------------------------------
IMPORTANT NOTICE
This communication contains information that is considered confidential and may also be privileged . It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender and delete the original.
|
|
From: Leif M. <le...@ta...> - 2008-07-22 15:42:13
|
Rob, As you are running from the console, you should be able to reproduce this by running the same command that the Wrapper generates from the command line. Open a command prompt and cd into the directory where the wrapper.exe is located. Now run the following command. It is the generated Java command minus the wrapper.key property: "C:\opt\java\jdk1.5.0_16\bin\java" -Dmule.home="." -Dmule.base="." -Dm2.repo="%M2_REPO%" -Dappendium.env=Gonzales -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=16001 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Xms128m -Xmx256m -Djava.library.path="%LD_LIBRARY_PATH%;./lib/boot" -classpath ".\bin/../conf;.\conf;./lib/boot/commons-cli-1.0.jar;./lib/boot/mule-module-boot-1.4.4.jar;./lib/boot/wrapper-3.2.3.jar" -Dwrapper.port=32001 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=3184 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.mule.modules.boot.MuleBootstrap -config .\conf\objectlab-esb-client-to-server-config_client1.xml My guess is that you will get the same error from the command line. Next try the java command itself: "C:\opt\java\jdk1.5.0_16\bin\java" -version What happens there? Cheers, Leif On Tue, Jul 22, 2008 at 7:04 PM, Rob Davison <rd...@ap...> wrote: > Hi All, > > I have seen some users have the following issue with the JVM not > starting. (Here, we are using Vista 64, with Mule 1.4.4). > The suggested workaround include checking the path to the JVM is > correct, and ensuring the the correct permissions are set on the folders. > > Here I have two processes using the wrapper - a client-from server, and > a client-to server. > > The client-from-server launches fine: > > wrapper config file: > C:\opt\appendium\mule\client-from-server\conf\wrapper-from- > server_client1.conf > Working directory set to: C:\opt\appendium\mule\client-from-server > --> Wrapper Started as Console > Using tick timer. > server listening on port 32001. > Launching a JVM... > command: "C:\opt\java\jdk1.5.0_16\bin\java" -Dmule.home="." > -Dmule.base="." -Dm2 > .repo="%M2_REPO%" -Dappendium.env=Gonzales > -Dcom.sun.management.jmxremote=true - > Dcom.sun.management.jmxremote.port=15001 > -Dcom.sun.management.jmxremote.ssl=fals > e -Dcom.sun.management.jmxremote.authenticate=false -Xms128m -Xmx600m > -Djava.lib > rary.path="%LD_LIBRARY_PATH%;./lib/boot" -classpath > ".\bin/../conf;.\conf;./lib/ > boot/commons-cli-1.0.jar;./lib/boot/mule-module-boot-1.4.4.jar;./lib/boot/wrappe > r-3.2.3.jar" -Dwrapper.key="hcHoizgB_iqKRoc5" -Dwrapper.port=32001 > -Dwrapper.jvm > .port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" > -Dwrapper.pi > d=4744 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" > -Dwrapper.cp > u.timeout="10" -Dwrapper.jvmid=1 org.mule.modules.boot.MuleBootstrap > -config .\c > onf\objectlab-esb-client-from-server-config_client1.xml > JVM started (PID=436) > > However, the client-to-server does not: > > wrapper config file: > C:\opt\appendium\mule\client-to-server\conf\wrapper-to-serv > er_client1.conf > Working directory set to: C:\opt\appendium\mule\client-to-server > --> Wrapper Started as Console > Using tick timer. > server listening on port 32001. > Launching a JVM... > command: "C:\opt\java\jdk1.5.0_16\bin\java" -Dmule.home="." > -Dmule.base="." -Dm2 > .repo="%M2_REPO%" -Dappendium.env=Gonzales > -Dcom.sun.management.jmxremote=true - > Dcom.sun.management.jmxremote.port=16001 > -Dcom.sun.management.jmxremote.ssl=fals > e -Dcom.sun.management.jmxremote.authenticate=false -Xms128m -Xmx256m > -Djava.lib > rary.path="%LD_LIBRARY_PATH%;./lib/boot" -classpath > ".\bin/../conf;.\conf;./lib/ > boot/commons-cli-1.0.jar;./lib/boot/mule-module-boot-1.4.4.jar;./lib/boot/wrappe > r-3.2.3.jar" -Dwrapper.key="9rKoYDt55Uk8QLuR" -Dwrapper.port=32001 > -Dwrapper.jvm > .port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" > -Dwrapper.pi > d=3184 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" > -Dwrapper.cp > u.timeout="10" -Dwrapper.jvmid=1 org.mule.modules.boot.MuleBootstrap > -config .\c > onf\objectlab-esb-client-to-server-config_client1.xml > Unable to execute Java command. Access is denied. (0x5) > "C:\opt\java\jdk1.5.0_16\bin\java" -Dmule.home="." -Dmule.base="." > -Dm2.repo > ="%M2_REPO%" -Dappendium.env=Gonzales > -Dcom.sun.management.jmxremote=true -Dcom. > sun.management.jmxremote.port=16001 > -Dcom.sun.management.jmxremote.ssl=false -Dc > om.sun.management.jmxremote.authenticate=false -Xms128m -Xmx256m > -Djava.library. > path="%LD_LIBRARY_PATH%;./lib/boot" -classpath > ".\bin/../conf;.\conf;./lib/boot/ > commons-cli-1.0.jar;./lib/boot/mule-module-boot-1.4.4.jar;./lib/boot/wrapper-3.2 > .3.jar" -Dwrapper.key="9rKoYDt55Uk8QLuR" -Dwrapper.port=32001 > -Dwrapper.jvm.port > .min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" > -Dwrapper.pid=318 > 4 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" > -Dwrapper.cpu.tim > eout="10" -Dwrapper.jvmid=1 org.mule.modules.boot.MuleBootstrap -config > .\conf\o > bjectlab-esb-client-to-server-config_client1.xml > > ------------------------------------------------------------------------ > Advice: > Access denied errors when attempting to launch the Java process are > usually caused by strict access permissions assigned to the directory > in which Java is installed. > ------------------------------------------------------------------------ > > Critical error: wait for JVM process failed > Press any key to continue . . . > > As far as I can tell, the parameters are identical (with the exception > of 'from/to paths') and the permissions are the same on all the folders. > Has anybody else come across this issue? > Many thanks > Rob. > > -- > ------------------------------ > > IMPORTANT NOTICE > > This communication contains information that is considered confidential and may also be privileged . It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender and delete the original. > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |