Menu
▾
▴
wrapper-user — User issues for Wrapper. (Support questions, etc.)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(13) |
Nov
(16) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(38) |
Feb
(51) |
Mar
(51) |
Apr
(115) |
May
(82) |
Jun
(30) |
Jul
(50) |
Aug
(68) |
Sep
(57) |
Oct
(160) |
Nov
(80) |
Dec
(78) |
| 2004 |
Jan
(71) |
Feb
(75) |
Mar
(108) |
Apr
(87) |
May
(79) |
Jun
(70) |
Jul
(69) |
Aug
(39) |
Sep
(52) |
Oct
(47) |
Nov
(50) |
Dec
(32) |
| 2005 |
Jan
(22) |
Feb
(122) |
Mar
(46) |
Apr
(76) |
May
(31) |
Jun
(51) |
Jul
(61) |
Aug
(70) |
Sep
(37) |
Oct
(46) |
Nov
(57) |
Dec
(83) |
| 2006 |
Jan
(55) |
Feb
(81) |
Mar
(51) |
Apr
(67) |
May
(77) |
Jun
(43) |
Jul
(106) |
Aug
(64) |
Sep
(47) |
Oct
(64) |
Nov
(60) |
Dec
(12) |
| 2007 |
Jan
(50) |
Feb
(93) |
Mar
(49) |
Apr
(56) |
May
(40) |
Jun
(63) |
Jul
(40) |
Aug
(47) |
Sep
(54) |
Oct
(37) |
Nov
(54) |
Dec
(37) |
| 2008 |
Jan
(35) |
Feb
(39) |
Mar
(26) |
Apr
(14) |
May
(23) |
Jun
(51) |
Jul
(43) |
Aug
(26) |
Sep
(29) |
Oct
(31) |
Nov
(24) |
Dec
(16) |
| 2009 |
Jan
(21) |
Feb
(30) |
Mar
(74) |
Apr
(26) |
May
(26) |
Jun
(43) |
Jul
(23) |
Aug
(23) |
Sep
(15) |
Oct
(27) |
Nov
(37) |
Dec
(10) |
| 2010 |
Jan
(16) |
Feb
(28) |
Mar
(16) |
Apr
(45) |
May
(8) |
Jun
(68) |
Jul
(45) |
Aug
(44) |
Sep
(51) |
Oct
(7) |
Nov
(20) |
Dec
(21) |
| 2011 |
Jan
(14) |
Feb
(17) |
Mar
(7) |
Apr
(7) |
May
(48) |
Jun
(23) |
Jul
(5) |
Aug
(33) |
Sep
(22) |
Oct
(14) |
Nov
(14) |
Dec
(5) |
| 2012 |
Jan
|
Feb
(10) |
Mar
(12) |
Apr
(51) |
May
(10) |
Jun
(8) |
Jul
(14) |
Aug
(22) |
Sep
(9) |
Oct
(24) |
Nov
(14) |
Dec
(13) |
| 2013 |
Jan
(12) |
Feb
(4) |
Mar
(14) |
Apr
(19) |
May
(2) |
Jun
(5) |
Jul
(13) |
Aug
(10) |
Sep
(4) |
Oct
(11) |
Nov
(13) |
Dec
(2) |
| 2014 |
Jan
(3) |
Feb
(14) |
Mar
(5) |
Apr
(10) |
May
(10) |
Jun
(11) |
Jul
(10) |
Aug
(3) |
Sep
(13) |
Oct
(22) |
Nov
(14) |
Dec
(32) |
| 2015 |
Jan
(8) |
Feb
(2) |
Mar
(17) |
Apr
(1) |
May
(24) |
Jun
|
Jul
(4) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(5) |
Dec
(2) |
| 2016 |
Jan
(8) |
Feb
(6) |
Mar
(6) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(7) |
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(8) |
Mar
(6) |
Apr
|
May
|
Jun
(3) |
Jul
(13) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(6) |
Dec
|
| 2018 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
(2) |
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(9) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2019 |
Jan
(9) |
Feb
|
Mar
|
Apr
(10) |
May
(3) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2021 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
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-15 16:33:01
|
Charles, There are some minor differences in the Wrapper process itself between running in a console and as a daemon process. But none of them should affect the way the JVM runs. The only possible difference should be with the enviroment in which the Wrapper itself starts. ie. some environment variables may be different. You said that it works when you run as "start". This is running the exact same mode as when started on system startup. The only difference is once again the environment. When you run in a console, you will be running as the current user. On startup, it will run as the root user with a VERY minimal environment, meaning that almost no environment variables will be set. I assume you have run with wrapper.debug enabled in both cases. Are there any differences in the java command used to launch the JVM in each case? Java itself should not be able to see the system environment variables directly, so any differences should be getting passed in on the command line. Another thing to check in the above is that the same JVM is being used in both cases. Cheers, Leif On Tue, Jul 15, 2008 at 11:52 PM, Charles Perry <c.e...@da...> wrote: > Yeah, the thing is that com.tivo.hme.host.sample.Main is not my code, so I > don't really have a full understanding of what its doing. The API I'm using > uses that as the main entry point, then hands off to my code. > > I've continued to work on this. I've not tried both methods 1 and 3. Both of > which work fine from the console, neither of which work from init.d. The > thing is, method 1 works just fine on Windows XP. I assumed that if it > worked on Windows, it should work on Linux as well. Is there an explanation > for the difference that could help me understand what's going on? > > Charlie > > Leif Mortenson wrote: > > Charles, > It looks like all of that setup work is taking place within the main > method of com.tivo.hme.host.sample.Main and then completing at > 2008/07/13 21:43:29. Java things it is supposed to quit as soon as > your main method completes which makes my think that there are not any > daemon threads being started as part of your application. > > There is no way for me to tell on this end what would be different > depending on how you launch your application. I don't see any sign > that anything is being done incorrectly with the wrapper configuration > though. > > At the very end of your main method, try calling > WrapperManager.requestThreadDump(). This will cause a dump of all > threads at the same point in your application. Compare the cases that > work and don't. My guess is that either your main method never > completes, or that there is at least one more daemon thread running > when it is working correctly. > > Cheers, > Leif > > On Mon, Jul 14, 2008 at 10:56 AM, Charles Perry <c.e...@da...> > wrote: > > > Leif, > > My application is an MP3 player that streams music from a networked PC to a > TiVo DVR, thus the messages about playlists. What should be happening at the > point in the logs timestamped with 17:53:21 ["Searching for music..."] in > the log I previously sent is that harmonium is searching through a directory > tree for mp3 files and setting up an internal data structure. This takes a > few seconds with the small data set I use for testing, then it moves on to > search for playlists at 17:53:27. I have no playlists in my set of test > data, so it immediately announces "Build of music database completed". I'm > attaching another log in which harmonium prints some debug messages. It > doesn't really show much that's new other than it has successfully found the > music directory and is loading mp3 files. > > In your email you said that there were two options you could think of. The > first involved System.exit(). I don't call System.exit() in my program. (I > just did a `find` to double check.) Are there other ways for that to be > called other than through my code? The second was that "all non-daemon > threads have completed." I'm not sure I completely understand that, but it > seems to mean that harmonium decided that it was done and exited. Any ideas > what might cause my program to bail out when the only thing that changed was > the method of execution? > > After your comment about environment variables, I modified my wrapper.conf > file to use the absolute path to java (/usr/bin/java). As far as I can tell, > all file references in wrapper.conf now are either absolute paths, or are > relative to the current directory (which should be ok, right?). I'm > attaching my wrapper.conf for your reference. What else might be affected by > a messed up environment variables? Should I modify the shell script you > supplied to set a PATH environment variable? > > Sorry for all the questions, but thanks for the help. > > Charlie > > > Leif Mortenson wrote: > > > Charles, > When Linux boots up, the environment used to launch daemon services > has very little in the way of an environment set up. Most likely > your system PATH and any other environment variables have not been set > up in this case. > > Looking at your log file, the following is interesting: > INFO | jvm 1 | 2008/07/13 17:53:27 | Searching for playlists... > INFO | jvm 1 | 2008/07/13 17:53:27 | Build of music database > completed > INFO | jvm 1 | 2008/07/13 17:53:27 | LOG: added factory > INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperSimpleApp: main method > completed > INFO | jvm 1 | 2008/07/13 17:53:27 | Wrapper Manager: ShutdownHook > started > > I am not sure what exactly your application does. But it says it is > looking for playlists and is immediately done. The JVM (and not the > Wrapper) then decides that the JVM should be shutdown. This happens > either when something calls System.exit or when all non-daemon threads > have completed. > > >From what I can see however, the Wrapper is working correctly. We > need to figure out which of the above 2 reasons is causing your > application to complete. > > Cheers, > Leif > > > > > DEBUG | wrapper | 2008/07/13 21:43:18 | Spawning intermediate process... > DEBUG | wrapper | 2008/07/13 21:43:18 | Spawning daemon process... > STATUS | wrapper | 2008/07/13 21:43:18 | --> Wrapper Started as Daemon > DEBUG | wrapper | 2008/07/13 21:43:18 | Using tick timer. > DEBUG | wrapperp | 2008/07/13 21:43:18 | server listening on port 32000. > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[0] : /usr/bin/java > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[1] : > -Djava.library.path=../lib > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[2] : -classpath > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[3] : > ../lib/bananas.jar:../lib/hme.jar:../lib/commons-logging-1.1.1.jar:../lib/hme-hd-0.4.1.jar:../lib/wrapper.jar:../lib/hme-host-sample.jar:../lib/JID3.jar:../Harmonium.jar > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[4] : > -Dwrapper.key=ET43Bkcr8tgRfi6A > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[5] : -Dwrapper.port=32000 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[6] : > -Dwrapper.jvm.port.min=31000 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[7] : > -Dwrapper.jvm.port.max=31999 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[8] : -Dwrapper.debug=TRUE > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[9] : -Dwrapper.pid=6787 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[10] : > -Dwrapper.version=3.2.3 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[11] : > -Dwrapper.native_library=wrapper > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[12] : > -Dwrapper.service=TRUE > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[13] : > -Dwrapper.cpu.timeout=10 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[14] : -Dwrapper.jvmid=1 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[15] : > org.tanukisoftware.wrapper.WrapperSimpleApp > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[16] : > com.tivo.hme.host.sample.Main > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[17] : > org.dazeend.harmonium.Harmonium > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[18] : -musicRoot > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[19] : > /home/ceperry/Harmonium/test_data/music > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[20] : -playlistRoot > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[21] : > /home/ceperry/Harmonium/test_data/playlists > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[22] : -debug > STATUS | wrapper | 2008/07/13 21:43:18 | Launching a JVM... > INFO | jvm 1 | 2008/07/13 21:43:20 | WrapperManager class initialized > by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@1ba34f2 > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper (Version 3.2.3) > http://wrapper.tanukisoftware.org > INFO | jvm 1 | 2008/07/13 21:43:22 | Copyright 1999-2006 Tanuki > Software, Inc. All Rights Reserved. > INFO | jvm 1 | 2008/07/13 21:43:22 | > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: JVM #1 > INFO | jvm 1 | 2008/07/13 21:43:22 | Running a 32-bit JVM. > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: Registering > shutdown hook > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: Using wrapper > INFO | jvm 1 | 2008/07/13 21:43:22 | Load native library. One or more > attempts may fail if platform specific libraries do not exist. > INFO | jvm 1 | 2008/07/13 21:43:22 | Loading native library failed: > libwrapper-linux-x86-32.so Cause: java.lang.UnsatisfiedLinkError: no > wrapper-linux-x86-32 in java.library.path > INFO | jvm 1 | 2008/07/13 21:43:22 | Loaded native library: > libwrapper.so > INFO | jvm 1 | 2008/07/13 21:43:22 | Calling native initialization > method. > INFO | jvm 1 | 2008/07/13 21:43:22 | Inside native WrapperManager > initialization method > INFO | jvm 1 | 2008/07/13 21:43:22 | Java Version : 1.6.0_06-b02 Java > HotSpot(TM) Server VM > INFO | jvm 1 | 2008/07/13 21:43:22 | Java VM Vendor : Sun Microsystems > Inc. > INFO | jvm 1 | 2008/07/13 21:43:22 | > INFO | jvm 1 | 2008/07/13 21:43:22 | Startup runner thread started. > INFO | jvm 1 | 2008/07/13 21:43:22 | Control event monitor thread > started. > INFO | jvm 1 | 2008/07/13 21:43:22 | > WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@17bd6a1, > args["org.dazeend.harmonium.Harmonium", "-musicRoot", > "/home/ceperry/Harmonium/test_data/music", "-playlistRoot", > "/home/ceperry/Harmonium/test_data/playlists", "-debug"]) called by thread: > main > INFO | jvm 1 | 2008/07/13 21:43:22 | Communications runner thread > started. > INFO | jvm 1 | 2008/07/13 21:43:22 | Open socket to > wrapper...Wrapper-Connection > INFO | jvm 1 | 2008/07/13 21:43:22 | Opened Socket from 31000 to 32000 > INFO | jvm 1 | 2008/07/13 21:43:22 | Send a packet KEY : > ET43Bkcr8tgRfi6A > INFO | jvm 1 | 2008/07/13 21:43:22 | > handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) > DEBUG | wrapperp | 2008/07/13 21:43:22 | accepted a socket from 127.0.0.1 > on port 31000 > DEBUG | wrapperp | 2008/07/13 21:43:22 | read a packet KEY : > ET43Bkcr8tgRfi6A > DEBUG | wrapper | 2008/07/13 21:43:22 | Got key from JVM: ET43Bkcr8tgRfi6A > DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet LOW_LOG_LEVEL : 1 > DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet PING_TIMEOUT : 30 > DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet PROPERTIES : > (Property Values) > DEBUG | wrapper | 2008/07/13 21:43:22 | Start Application. > DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet START : start > INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet LOW_LOG_LEVEL : > 1 > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: LowLogLevel from > Wrapper is 1 > INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet PING_TIMEOUT : > 30 > INFO | jvm 1 | 2008/07/13 21:43:22 | PingTimeout from Wrapper is 30000 > INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet PROPERTIES : > (Property Values) > INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet START : start > INFO | jvm 1 | 2008/07/13 21:43:22 | calling WrapperListener.start() > INFO | jvm 1 | 2008/07/13 21:43:22 | Waiting for WrapperListener.start > runner thread to complete. > INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperListener.start runner > thread started. > INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperSimpleApp: start(args) Will > wait up to 2 seconds for the main method to complete. > INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperSimpleApp: invoking main > method > INFO | jvm 1 | 2008/07/13 21:43:22 | HME SDK 1.4 (TiVo, Inc.) > INFO | jvm 1 | 2008/07/13 21:43:23 | Searching for music... > INFO | jvm 1 | 2008/07/13 21:43:23 | DEBUG: reading file 1: Incomplete > Tags/Mixed No Art/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:23 | Send a packet START_PENDING : 5000 > DEBUG | wrapperp | 2008/07/13 21:43:23 | read a packet START_PENDING : 5000 > DEBUG | wrapper | 2008/07/13 21:43:23 | JVM signalled a start pending with > waitHint of 5000 millis. > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 2: Incomplete > Tags/Mixed No Art/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 3: Incomplete > Tags/Mixed No Art/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 4: Incomplete > Tags/Mixed No Art/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 5: Incomplete > Tags/No Artist and No Artist Album/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 6: Incomplete > Tags/No Artist and No Artist Album/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet START_PENDING : 5000 > INFO | jvm 1 | 2008/07/13 21:43:24 | WrapperSimpleApp: start(args) end. > Main Completed=false, exitCode=null > INFO | jvm 1 | 2008/07/13 21:43:24 | WrapperListener.start runner > thread stopped. > INFO | jvm 1 | 2008/07/13 21:43:24 | returned from > WrapperListener.start() > INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet STARTED : > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 7: Incomplete > Tags/No Artist and No Artist Album/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | Startup runner thread stopped. > DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet START_PENDING : 5000 > DEBUG | wrapper | 2008/07/13 21:43:24 | JVM signalled a start pending with > waitHint of 5000 millis. > DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet STARTED : > DEBUG | wrapper | 2008/07/13 21:43:24 | JVM signalled that it was started. > DEBUG | wrapperp | 2008/07/13 21:43:24 | send a packet PING : ping > INFO | jvm 1 | 2008/07/13 21:43:24 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet PING : ok > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 8: Incomplete > Tags/No Artist and No Artist Album/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 9: Incomplete > Tags/No Album/03 Candy Everybody Wants.mp3 > DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet PING : ok > DEBUG | wrapper | 2008/07/13 21:43:24 | Got ping response from JVM > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 10: Incomplete > Tags/No Album/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 11: Incomplete > Tags/No Album/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 12: Incomplete > Tags/No Album/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 13: Incomplete > Tags/No Artist Album/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 14: Incomplete > Tags/No Artist Album/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 15: Incomplete > Tags/No Artist Album/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 16: Incomplete > Tags/No Artist Album/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 17: Incomplete > Tags/No Art/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 18: Incomplete > Tags/No Art/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 19: Incomplete > Tags/No Art/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 20: Incomplete > Tags/No Art/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 21: Incomplete > Tags/No Artist/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 22: Incomplete > Tags/No Artist/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 23: Incomplete > Tags/No Artist/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 24: Incomplete > Tags/No Artist/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 25: Incomplete > Tags/No Track Name/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 26: Incomplete > Tags/No Track Name/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 27: Incomplete > Tags/No Track Name/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 28: Incomplete > Tags/No Track Name/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 29: Multi-disc > set/Album1/Disc 2/01 My Life.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 30: Multi-disc > set/Album1/Disc 2/02 Big Shot.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 31: Multi-disc > set/Album1/Disc 1/01 Piano Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 32: Multi-disc > set/Album1/Disc 1/02 Captain Jack.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 33: Multi-disc > set/Album2/02 An Innocent Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 34: Multi-disc > set/Album2/01 Keeping the Faith.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 35: Complete > tags/Four/03 Look Around.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 36: Complete > tags/Four/02 Stand.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 37: Complete > tags/Four/01 Run-Around.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 38: Complete > tags/Four/04 Fallible.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 39: Complete > tags/Save His Soul/03 Letter from a Friend.mp3 > DEBUG | wrapperp | 2008/07/13 21:43:28 | send a packet PING : ping > INFO | jvm 1 | 2008/07/13 21:43:28 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/13 21:43:28 | Send a packet PING : ok > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 40: Complete > tags/Save His Soul/02 Love and Greed.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 41: Complete > tags/Save His Soul/01 Trina Magna.mp3 > DEBUG | wrapperp | 2008/07/13 21:43:28 | read a packet PING : ok > DEBUG | wrapper | 2008/07/13 21:43:28 | Got ping response from JVM > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 42: CEP3/07 > While My Guitar Gently Weeps.mp3 > INFO | jvm 1 | 2008/07/13 21:43:29 | DEBUG: reading file 43: CEP3/06 > The Continuing Story of Bungalow Bill.mp3 > INFO | jvm 1 | 2008/07/13 21:43:29 | Searching for playlists... > INFO | jvm 1 | 2008/07/13 21:43:29 | Build of music database completed > INFO | jvm 1 | 2008/07/13 21:43:29 | LOG: added factory > INFO | jvm 1 | 2008/07/13 21:43:29 | WrapperSimpleApp: main method > completed > INFO | jvm 1 | 2008/07/13 21:43:29 | Wrapper Manager: ShutdownHook > started > INFO | jvm 1 | 2008/07/13 21:43:29 | WrapperManager.stop(0) called by > thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/07/13 21:43:29 | Send a packet STOP : 0 > DEBUG | wrapperp | 2008/07/13 21:43:29 | read a packet STOP : 0 > DEBUG | wrapper | 2008/07/13 21:43:29 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2008/07/13 21:43:29 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2008/07/13 21:43:29 | Sending stop signal to JVM > DEBUG | wrapperp | 2008/07/13 21:43:29 | send a packet STOP : NULL > INFO | jvm 1 | 2008/07/13 21:43:29 | Received a packet STOP : > INFO | jvm 1 | 2008/07/13 21:43:30 | Thread, Wrapper-Shutdown-Hook, > handling the shutdown process. > INFO | jvm 1 | 2008/07/13 21:43:30 | calling listener.stop() > INFO | jvm 1 | 2008/07/13 21:43:30 | WrapperSimpleApp: stop(0) > INFO | jvm 1 | 2008/07/13 21:43:30 | returned from listener.stop() -> 0 > INFO | jvm 1 | 2008/07/13 21:43:30 | shutdownJVM(0) > Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/07/13 21:43:30 | Send a packet STOPPED : 0 > DEBUG | wrapperp | 2008/07/13 21:43:30 | read a packet STOPPED : 0 > DEBUG | wrapper | 2008/07/13 21:43:30 | JVM signalled that it was stopped. > INFO | jvm 1 | 2008/07/13 21:43:30 | Closing socket. > DEBUG | wrapperp | 2008/07/13 21:43:30 | socket read no code (closed?). > DEBUG | wrapperp | 2008/07/13 21:43:30 | server listening on port 32001. > DEBUG | wrapper | 2008/07/13 21:43:30 | JVM exited normally. > DEBUG | wrapper | 2008/07/13 21:43:30 | Signal trapped. Details: > DEBUG | wrapper | 2008/07/13 21:43:30 | signal number=17 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2008/07/13 21:43:30 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2008/07/13 21:43:30 | JVM process exited with a code of > 0, leaving the wrapper exit code set to 0. > INFO | jvm 1 | 2008/07/13 21:43:30 | Wrapper Manager: ShutdownHook > complete > INFO | jvm 1 | 2008/07/13 21:43:30 | Server daemon shut down > STATUS | wrapper | 2008/07/13 21:43:31 | <-- Wrapper Stopped > > #******************************************************************** > # Wrapper Properties > #******************************************************************** > # Java Application > wrapper.java.command=/usr/bin/java > > # Java Main class. This class must implement the WrapperListener interface > # or guarantee that the WrapperManager class is initialized. Helper > # classes are provided to do this for you. See the Integration section > # of the documentation for details. > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > > # Java Classpath (include wrapper.jar) Add class path elements as > # needed starting from 1 > wrapper.java.classpath.1=../lib/*.jar > wrapper.java.classpath.2=../Harmonium.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=../lib > > # Java Additional Parameters > #wrapper.java.additional.1= > > # Initial Java Heap Size (in MB) > #wrapper.java.initmemory=3 > > # Maximum Java Heap Size (in MB) > #wrapper.java.maxmemory=64 > > # Application parameters. Add parameters as needed starting from 1 > wrapper.app.parameter.1=com.tivo.hme.host.sample.Main > wrapper.app.parameter.2=org.dazeend.harmonium.Harmonium > wrapper.app.parameter.3=-musicRoot > wrapper.app.parameter.4=/home/ceperry/Harmonium/test_data/music > wrapper.app.parameter.4.stripquotes=TRUE > wrapper.app.parameter.5=-playlistRoot > wrapper.app.parameter.6=/home/ceperry/Harmonium/test_data/playlists > wrapper.app.parameter.6.stripquotes=TRUE > wrapper.app.parameter.7=-debug > > #******************************************************************** > # Wrapper Logging Properties > #******************************************************************** > # Format of output for the console. (See docs for formats) > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > #wrapper.console.loglevel=INFO > wrapper.console.loglevel=DEBUG > > # Log file to use for wrapper output logging. > wrapper.logfile=../logs/wrapper.log > > # Format of output for the log file. (See docs for formats) > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > #wrapper.logfile.loglevel=INFO > wrapper.logfile.loglevel=DEBUG > > # Maximum size that the log file will be allowed to grow to before > # the log is rolled. Size is specified in bytes. The default value > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > wrapper.logfile.maxsize=0 > > # Maximum number of rolled log files which will be allowed before old > # files are deleted. The default value of 0 implies no limit. > wrapper.logfile.maxfiles=0 > > # Log Level for sys/event log output. (See docs for log levels) > #wrapper.syslog.loglevel=NONE > wrapper.syslog.loglevel=DEBUG > > #******************************************************************** > # Wrapper Windows Properties > #******************************************************************** > # Title to use when running as a console > wra...@ap...@ > > #******************************************************************** > # Wrapper Windows NT/2000/XP Service Properties > #******************************************************************** > # WARNING - Do not modify any of these properties when an application > # using this configuration file has been installed as a service. > # Please uninstall the service before modifying this section. The > # service can then be reinstalled. > > # Name of the service > wra...@ap...@ > > # Display name of the service > wra...@ap...@ > > # Description of the service > wra...@ap...@ > > # Service dependencies. Add dependencies as needed starting from 1 > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > wrapper.ntservice.starttype=AUTO_START > > # Allow the service to interact with the desktop. > wrapper.ntservice.interactive=false > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > ------------------------------------------------------------------------- > 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 > > |
|
From: Charles P. <c.e...@da...> - 2008-07-15 14:53:14
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Yeah, the thing is that com.tivo.hme.host.sample.Main is not my code,
so I don't really have a full understanding of what its doing. The API
I'm using uses that as the main entry point, then hands off to my code.<br>
<br>
I've continued to work on this. I've not tried both methods 1 and 3.
Both of which work fine from the console, neither of which work from
init.d. The thing is, method 1 works just fine on Windows XP. I assumed
that if it worked on Windows, it should work on Linux as well. Is there
an explanation for the difference that could help me understand what's
going on?<br>
<br>
Charlie<br>
<br>
Leif Mortenson wrote:
<blockquote
cite="mid:c0a...@ma..."
type="cite">
<pre wrap="">Charles,
It looks like all of that setup work is taking place within the main
method of com.tivo.hme.host.sample.Main and then completing at
2008/07/13 21:43:29. Java things it is supposed to quit as soon as
your main method completes which makes my think that there are not any
daemon threads being started as part of your application.
There is no way for me to tell on this end what would be different
depending on how you launch your application. I don't see any sign
that anything is being done incorrectly with the wrapper configuration
though.
At the very end of your main method, try calling
WrapperManager.requestThreadDump(). This will cause a dump of all
threads at the same point in your application. Compare the cases that
work and don't. My guess is that either your main method never
completes, or that there is at least one more daemon thread running
when it is working correctly.
Cheers,
Leif
On Mon, Jul 14, 2008 at 10:56 AM, Charles Perry <a class="moz-txt-link-rfc2396E" href="mailto:c.e...@da..."><c.e...@da...></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Leif,
My application is an MP3 player that streams music from a networked PC to a
TiVo DVR, thus the messages about playlists. What should be happening at the
point in the logs timestamped with 17:53:21 ["Searching for music..."] in
the log I previously sent is that harmonium is searching through a directory
tree for mp3 files and setting up an internal data structure. This takes a
few seconds with the small data set I use for testing, then it moves on to
search for playlists at 17:53:27. I have no playlists in my set of test
data, so it immediately announces "Build of music database completed". I'm
attaching another log in which harmonium prints some debug messages. It
doesn't really show much that's new other than it has successfully found the
music directory and is loading mp3 files.
In your email you said that there were two options you could think of. The
first involved System.exit(). I don't call System.exit() in my program. (I
just did a `find` to double check.) Are there other ways for that to be
called other than through my code? The second was that "all non-daemon
threads have completed." I'm not sure I completely understand that, but it
seems to mean that harmonium decided that it was done and exited. Any ideas
what might cause my program to bail out when the only thing that changed was
the method of execution?
After your comment about environment variables, I modified my wrapper.conf
file to use the absolute path to java (/usr/bin/java). As far as I can tell,
all file references in wrapper.conf now are either absolute paths, or are
relative to the current directory (which should be ok, right?). I'm
attaching my wrapper.conf for your reference. What else might be affected by
a messed up environment variables? Should I modify the shell script you
supplied to set a PATH environment variable?
Sorry for all the questions, but thanks for the help.
Charlie
Leif Mortenson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Charles,
When Linux boots up, the environment used to launch daemon services
has very little in the way of an environment set up. Most likely
your system PATH and any other environment variables have not been set
up in this case.
Looking at your log file, the following is interesting:
INFO | jvm 1 | 2008/07/13 17:53:27 | Searching for playlists...
INFO | jvm 1 | 2008/07/13 17:53:27 | Build of music database
completed
INFO | jvm 1 | 2008/07/13 17:53:27 | LOG: added factory
INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperSimpleApp: main method
completed
INFO | jvm 1 | 2008/07/13 17:53:27 | Wrapper Manager: ShutdownHook
started
I am not sure what exactly your application does. But it says it is
looking for playlists and is immediately done. The JVM (and not the
Wrapper) then decides that the JVM should be shutdown. This happens
either when something calls System.exit or when all non-daemon threads
have completed.
>From what I can see however, the Wrapper is working correctly. We
need to figure out which of the above 2 reasons is causing your
application to complete.
Cheers,
Leif
</pre>
</blockquote>
<pre wrap="">
DEBUG | wrapper | 2008/07/13 21:43:18 | Spawning intermediate process...
DEBUG | wrapper | 2008/07/13 21:43:18 | Spawning daemon process...
STATUS | wrapper | 2008/07/13 21:43:18 | --> Wrapper Started as Daemon
DEBUG | wrapper | 2008/07/13 21:43:18 | Using tick timer.
DEBUG | wrapperp | 2008/07/13 21:43:18 | server listening on port 32000.
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[0] : /usr/bin/java
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[1] :
-Djava.library.path=../lib
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[2] : -classpath
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[3] :
../lib/bananas.jar:../lib/hme.jar:../lib/commons-logging-1.1.1.jar:../lib/hme-hd-0.4.1.jar:../lib/wrapper.jar:../lib/hme-host-sample.jar:../lib/JID3.jar:../Harmonium.jar
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[4] :
-Dwrapper.key=ET43Bkcr8tgRfi6A
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[5] : -Dwrapper.port=32000
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[6] :
-Dwrapper.jvm.port.min=31000
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[7] :
-Dwrapper.jvm.port.max=31999
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[8] : -Dwrapper.debug=TRUE
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[9] : -Dwrapper.pid=6787
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[10] :
-Dwrapper.version=3.2.3
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[11] :
-Dwrapper.native_library=wrapper
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[12] :
-Dwrapper.service=TRUE
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[13] :
-Dwrapper.cpu.timeout=10
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[14] : -Dwrapper.jvmid=1
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[15] :
org.tanukisoftware.wrapper.WrapperSimpleApp
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[16] :
com.tivo.hme.host.sample.Main
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[17] :
org.dazeend.harmonium.Harmonium
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[18] : -musicRoot
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[19] :
/home/ceperry/Harmonium/test_data/music
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[20] : -playlistRoot
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[21] :
/home/ceperry/Harmonium/test_data/playlists
DEBUG | wrapper | 2008/07/13 21:43:18 | Command[22] : -debug
STATUS | wrapper | 2008/07/13 21:43:18 | Launching a JVM...
INFO | jvm 1 | 2008/07/13 21:43:20 | WrapperManager class initialized
by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@1ba34f2
INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper (Version 3.2.3)
<a class="moz-txt-link-freetext" href="http://wrapper.tanukisoftware.org">http://wrapper.tanukisoftware.org</a>
INFO | jvm 1 | 2008/07/13 21:43:22 | Copyright 1999-2006 Tanuki
Software, Inc. All Rights Reserved.
INFO | jvm 1 | 2008/07/13 21:43:22 |
INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: JVM #1
INFO | jvm 1 | 2008/07/13 21:43:22 | Running a 32-bit JVM.
INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: Registering
shutdown hook
INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: Using wrapper
INFO | jvm 1 | 2008/07/13 21:43:22 | Load native library. One or more
attempts may fail if platform specific libraries do not exist.
INFO | jvm 1 | 2008/07/13 21:43:22 | Loading native library failed:
libwrapper-linux-x86-32.so Cause: java.lang.UnsatisfiedLinkError: no
wrapper-linux-x86-32 in java.library.path
INFO | jvm 1 | 2008/07/13 21:43:22 | Loaded native library:
libwrapper.so
INFO | jvm 1 | 2008/07/13 21:43:22 | Calling native initialization
method.
INFO | jvm 1 | 2008/07/13 21:43:22 | Inside native WrapperManager
initialization method
INFO | jvm 1 | 2008/07/13 21:43:22 | Java Version : 1.6.0_06-b02 Java
HotSpot(TM) Server VM
INFO | jvm 1 | 2008/07/13 21:43:22 | Java VM Vendor : Sun Microsystems
Inc.
INFO | jvm 1 | 2008/07/13 21:43:22 |
INFO | jvm 1 | 2008/07/13 21:43:22 | Startup runner thread started.
INFO | jvm 1 | 2008/07/13 21:43:22 | Control event monitor thread
started.
INFO | jvm 1 | 2008/07/13 21:43:22 |
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@17bd6a1,
args["org.dazeend.harmonium.Harmonium", "-musicRoot",
"/home/ceperry/Harmonium/test_data/music", "-playlistRoot",
"/home/ceperry/Harmonium/test_data/playlists", "-debug"]) called by thread:
main
INFO | jvm 1 | 2008/07/13 21:43:22 | Communications runner thread
started.
INFO | jvm 1 | 2008/07/13 21:43:22 | Open socket to
wrapper...Wrapper-Connection
INFO | jvm 1 | 2008/07/13 21:43:22 | Opened Socket from 31000 to 32000
INFO | jvm 1 | 2008/07/13 21:43:22 | Send a packet KEY :
ET43Bkcr8tgRfi6A
INFO | jvm 1 | 2008/07/13 21:43:22 |
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000])
DEBUG | wrapperp | 2008/07/13 21:43:22 | accepted a socket from 127.0.0.1
on port 31000
DEBUG | wrapperp | 2008/07/13 21:43:22 | read a packet KEY :
ET43Bkcr8tgRfi6A
DEBUG | wrapper | 2008/07/13 21:43:22 | Got key from JVM: ET43Bkcr8tgRfi6A
DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet LOW_LOG_LEVEL : 1
DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet PING_TIMEOUT : 30
DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet PROPERTIES :
(Property Values)
DEBUG | wrapper | 2008/07/13 21:43:22 | Start Application.
DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet START : start
INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet LOW_LOG_LEVEL :
1
INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: LowLogLevel from
Wrapper is 1
INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet PING_TIMEOUT :
30
INFO | jvm 1 | 2008/07/13 21:43:22 | PingTimeout from Wrapper is 30000
INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet PROPERTIES :
(Property Values)
INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet START : start
INFO | jvm 1 | 2008/07/13 21:43:22 | calling WrapperListener.start()
INFO | jvm 1 | 2008/07/13 21:43:22 | Waiting for WrapperListener.start
runner thread to complete.
INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperListener.start runner
thread started.
INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperSimpleApp: start(args) Will
wait up to 2 seconds for the main method to complete.
INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperSimpleApp: invoking main
method
INFO | jvm 1 | 2008/07/13 21:43:22 | HME SDK 1.4 (TiVo, Inc.)
INFO | jvm 1 | 2008/07/13 21:43:23 | Searching for music...
INFO | jvm 1 | 2008/07/13 21:43:23 | DEBUG: reading file 1: Incomplete
Tags/Mixed No Art/03 Candy Everybody Wants.mp3
INFO | jvm 1 | 2008/07/13 21:43:23 | Send a packet START_PENDING : 5000
DEBUG | wrapperp | 2008/07/13 21:43:23 | read a packet START_PENDING : 5000
DEBUG | wrapper | 2008/07/13 21:43:23 | JVM signalled a start pending with
waitHint of 5000 millis.
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 2: Incomplete
Tags/Mixed No Art/01 These Are Days.mp3
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 3: Incomplete
Tags/Mixed No Art/04 I'm Not the Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 4: Incomplete
Tags/Mixed No Art/02 Eat for Two.mp3
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 5: Incomplete
Tags/No Artist and No Artist Album/03 Candy Everybody Wants.mp3
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 6: Incomplete
Tags/No Artist and No Artist Album/01 These Are Days.mp3
INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet START_PENDING : 5000
INFO | jvm 1 | 2008/07/13 21:43:24 | WrapperSimpleApp: start(args) end.
Main Completed=false, exitCode=null
INFO | jvm 1 | 2008/07/13 21:43:24 | WrapperListener.start runner
thread stopped.
INFO | jvm 1 | 2008/07/13 21:43:24 | returned from
WrapperListener.start()
INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet STARTED :
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 7: Incomplete
Tags/No Artist and No Artist Album/04 I'm Not the Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:24 | Startup runner thread stopped.
DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet START_PENDING : 5000
DEBUG | wrapper | 2008/07/13 21:43:24 | JVM signalled a start pending with
waitHint of 5000 millis.
DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet STARTED :
DEBUG | wrapper | 2008/07/13 21:43:24 | JVM signalled that it was started.
DEBUG | wrapperp | 2008/07/13 21:43:24 | send a packet PING : ping
INFO | jvm 1 | 2008/07/13 21:43:24 | Received a packet PING : ping
INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet PING : ok
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 8: Incomplete
Tags/No Artist and No Artist Album/02 Eat for Two.mp3
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 9: Incomplete
Tags/No Album/03 Candy Everybody Wants.mp3
DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet PING : ok
DEBUG | wrapper | 2008/07/13 21:43:24 | Got ping response from JVM
INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 10: Incomplete
Tags/No Album/01 These Are Days.mp3
INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 11: Incomplete
Tags/No Album/04 I'm Not the Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 12: Incomplete
Tags/No Album/02 Eat for Two.mp3
INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 13: Incomplete
Tags/No Artist Album/03 Candy Everybody Wants.mp3
INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 14: Incomplete
Tags/No Artist Album/01 These Are Days.mp3
INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 15: Incomplete
Tags/No Artist Album/04 I'm Not the Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 16: Incomplete
Tags/No Artist Album/02 Eat for Two.mp3
INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 17: Incomplete
Tags/No Art/03 Candy Everybody Wants.mp3
INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 18: Incomplete
Tags/No Art/01 These Are Days.mp3
INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 19: Incomplete
Tags/No Art/04 I'm Not the Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 20: Incomplete
Tags/No Art/02 Eat for Two.mp3
INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 21: Incomplete
Tags/No Artist/03 Candy Everybody Wants.mp3
INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 22: Incomplete
Tags/No Artist/01 These Are Days.mp3
INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 23: Incomplete
Tags/No Artist/04 I'm Not the Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 24: Incomplete
Tags/No Artist/02 Eat for Two.mp3
INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 25: Incomplete
Tags/No Track Name/03 Candy Everybody Wants.mp3
INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 26: Incomplete
Tags/No Track Name/01 These Are Days.mp3
INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 27: Incomplete
Tags/No Track Name/04 I'm Not the Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 28: Incomplete
Tags/No Track Name/02 Eat for Two.mp3
INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 29: Multi-disc
set/Album1/Disc 2/01 My Life.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 30: Multi-disc
set/Album1/Disc 2/02 Big Shot.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 31: Multi-disc
set/Album1/Disc 1/01 Piano Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 32: Multi-disc
set/Album1/Disc 1/02 Captain Jack.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 33: Multi-disc
set/Album2/02 An Innocent Man.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 34: Multi-disc
set/Album2/01 Keeping the Faith.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 35: Complete
tags/Four/03 Look Around.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 36: Complete
tags/Four/02 Stand.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 37: Complete
tags/Four/01 Run-Around.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 38: Complete
tags/Four/04 Fallible.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 39: Complete
tags/Save His Soul/03 Letter from a Friend.mp3
DEBUG | wrapperp | 2008/07/13 21:43:28 | send a packet PING : ping
INFO | jvm 1 | 2008/07/13 21:43:28 | Received a packet PING : ping
INFO | jvm 1 | 2008/07/13 21:43:28 | Send a packet PING : ok
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 40: Complete
tags/Save His Soul/02 Love and Greed.mp3
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 41: Complete
tags/Save His Soul/01 Trina Magna.mp3
DEBUG | wrapperp | 2008/07/13 21:43:28 | read a packet PING : ok
DEBUG | wrapper | 2008/07/13 21:43:28 | Got ping response from JVM
INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 42: CEP3/07
While My Guitar Gently Weeps.mp3
INFO | jvm 1 | 2008/07/13 21:43:29 | DEBUG: reading file 43: CEP3/06
The Continuing Story of Bungalow Bill.mp3
INFO | jvm 1 | 2008/07/13 21:43:29 | Searching for playlists...
INFO | jvm 1 | 2008/07/13 21:43:29 | Build of music database completed
INFO | jvm 1 | 2008/07/13 21:43:29 | LOG: added factory
INFO | jvm 1 | 2008/07/13 21:43:29 | WrapperSimpleApp: main method
completed
INFO | jvm 1 | 2008/07/13 21:43:29 | Wrapper Manager: ShutdownHook
started
INFO | jvm 1 | 2008/07/13 21:43:29 | WrapperManager.stop(0) called by
thread: Wrapper-Shutdown-Hook
INFO | jvm 1 | 2008/07/13 21:43:29 | Send a packet STOP : 0
DEBUG | wrapperp | 2008/07/13 21:43:29 | read a packet STOP : 0
DEBUG | wrapper | 2008/07/13 21:43:29 | JVM requested a shutdown. (0)
DEBUG | wrapper | 2008/07/13 21:43:29 | wrapperStopProcess(0) called.
DEBUG | wrapper | 2008/07/13 21:43:29 | Sending stop signal to JVM
DEBUG | wrapperp | 2008/07/13 21:43:29 | send a packet STOP : NULL
INFO | jvm 1 | 2008/07/13 21:43:29 | Received a packet STOP :
INFO | jvm 1 | 2008/07/13 21:43:30 | Thread, Wrapper-Shutdown-Hook,
handling the shutdown process.
INFO | jvm 1 | 2008/07/13 21:43:30 | calling listener.stop()
INFO | jvm 1 | 2008/07/13 21:43:30 | WrapperSimpleApp: stop(0)
INFO | jvm 1 | 2008/07/13 21:43:30 | returned from listener.stop() -> 0
INFO | jvm 1 | 2008/07/13 21:43:30 | shutdownJVM(0)
Thread:Wrapper-Shutdown-Hook
INFO | jvm 1 | 2008/07/13 21:43:30 | Send a packet STOPPED : 0
DEBUG | wrapperp | 2008/07/13 21:43:30 | read a packet STOPPED : 0
DEBUG | wrapper | 2008/07/13 21:43:30 | JVM signalled that it was stopped.
INFO | jvm 1 | 2008/07/13 21:43:30 | Closing socket.
DEBUG | wrapperp | 2008/07/13 21:43:30 | socket read no code (closed?).
DEBUG | wrapperp | 2008/07/13 21:43:30 | server listening on port 32001.
DEBUG | wrapper | 2008/07/13 21:43:30 | JVM exited normally.
DEBUG | wrapper | 2008/07/13 21:43:30 | Signal trapped. Details:
DEBUG | wrapper | 2008/07/13 21:43:30 | signal number=17 (SIGCHLD),
source="unknown"
DEBUG | wrapper | 2008/07/13 21:43:30 | Received SIGCHLD, checking JVM
process status.
DEBUG | wrapper | 2008/07/13 21:43:30 | JVM process exited with a code of
0, leaving the wrapper exit code set to 0.
INFO | jvm 1 | 2008/07/13 21:43:30 | Wrapper Manager: ShutdownHook
complete
INFO | jvm 1 | 2008/07/13 21:43:30 | Server daemon shut down
STATUS | wrapper | 2008/07/13 21:43:31 | <-- Wrapper Stopped
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=/usr/bin/java
# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../lib/*.jar
wrapper.java.classpath.2=../Harmonium.jar
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib
# Java Additional Parameters
#wrapper.java.additional.1=
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3
# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=com.tivo.hme.host.sample.Main
wrapper.app.parameter.2=org.dazeend.harmonium.Harmonium
wrapper.app.parameter.3=-musicRoot
wrapper.app.parameter.4=/home/ceperry/Harmonium/test_data/music
wrapper.app.parameter.4.stripquotes=TRUE
wrapper.app.parameter.5=-playlistRoot
wrapper.app.parameter.6=/home/ceperry/Harmonium/test_data/playlists
wrapper.app.parameter.6.stripquotes=TRUE
wrapper.app.parameter.7=-debug
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM
# Log Level for console output. (See docs for log levels)
#wrapper.console.loglevel=INFO
wrapper.console.loglevel=DEBUG
# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log
# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM
# Log Level for log file output. (See docs for log levels)
#wrapper.logfile.loglevel=INFO
wrapper.logfile.loglevel=DEBUG
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0
# Log Level for sys/event log output. (See docs for log levels)
#wrapper.syslog.loglevel=NONE
wrapper.syslog.loglevel=DEBUG
#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
<a class="moz-txt-link-abbreviated" href="mailto:wra...@ap...@">wra...@ap...@</a>
#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
<a class="moz-txt-link-abbreviated" href="mailto:wra...@ap...@">wra...@ap...@</a>
# Display name of the service
<a class="moz-txt-link-abbreviated" href="mailto:wra...@ap...@">wra...@ap...@</a>
# Description of the service
<a class="moz-txt-link-abbreviated" href="mailto:wra...@ap...@">wra...@ap...@</a>
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at <a class="moz-txt-link-freetext" href="http://www.sourceforge.net/community/cca08">http://www.sourceforge.net/community/cca08</a>
_______________________________________________
Wrapper-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Wra...@li...">Wra...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wrapper-user">https://lists.sourceforge.net/lists/listinfo/wrapper-user</a>
</pre>
</blockquote>
<pre wrap=""><!---->
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at <a class="moz-txt-link-freetext" href="http://www.sourceforge.net/community/cca08">http://www.sourceforge.net/community/cca08</a>
_______________________________________________
Wrapper-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Wra...@li...">Wra...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wrapper-user">https://lists.sourceforge.net/lists/listinfo/wrapper-user</a>
</pre>
</blockquote>
<br>
</body>
</html>
|
|
From: Leif M. <le...@ta...> - 2008-07-14 03:23:58
|
Charles, It looks like all of that setup work is taking place within the main method of com.tivo.hme.host.sample.Main and then completing at 2008/07/13 21:43:29. Java things it is supposed to quit as soon as your main method completes which makes my think that there are not any daemon threads being started as part of your application. There is no way for me to tell on this end what would be different depending on how you launch your application. I don't see any sign that anything is being done incorrectly with the wrapper configuration though. At the very end of your main method, try calling WrapperManager.requestThreadDump(). This will cause a dump of all threads at the same point in your application. Compare the cases that work and don't. My guess is that either your main method never completes, or that there is at least one more daemon thread running when it is working correctly. Cheers, Leif On Mon, Jul 14, 2008 at 10:56 AM, Charles Perry <c.e...@da...> wrote: > Leif, > > My application is an MP3 player that streams music from a networked PC to a > TiVo DVR, thus the messages about playlists. What should be happening at the > point in the logs timestamped with 17:53:21 ["Searching for music..."] in > the log I previously sent is that harmonium is searching through a directory > tree for mp3 files and setting up an internal data structure. This takes a > few seconds with the small data set I use for testing, then it moves on to > search for playlists at 17:53:27. I have no playlists in my set of test > data, so it immediately announces "Build of music database completed". I'm > attaching another log in which harmonium prints some debug messages. It > doesn't really show much that's new other than it has successfully found the > music directory and is loading mp3 files. > > In your email you said that there were two options you could think of. The > first involved System.exit(). I don't call System.exit() in my program. (I > just did a `find` to double check.) Are there other ways for that to be > called other than through my code? The second was that "all non-daemon > threads have completed." I'm not sure I completely understand that, but it > seems to mean that harmonium decided that it was done and exited. Any ideas > what might cause my program to bail out when the only thing that changed was > the method of execution? > > After your comment about environment variables, I modified my wrapper.conf > file to use the absolute path to java (/usr/bin/java). As far as I can tell, > all file references in wrapper.conf now are either absolute paths, or are > relative to the current directory (which should be ok, right?). I'm > attaching my wrapper.conf for your reference. What else might be affected by > a messed up environment variables? Should I modify the shell script you > supplied to set a PATH environment variable? > > Sorry for all the questions, but thanks for the help. > > Charlie > > > Leif Mortenson wrote: >> >> Charles, >> When Linux boots up, the environment used to launch daemon services >> has very little in the way of an environment set up. Most likely >> your system PATH and any other environment variables have not been set >> up in this case. >> >> Looking at your log file, the following is interesting: >> INFO | jvm 1 | 2008/07/13 17:53:27 | Searching for playlists... >> INFO | jvm 1 | 2008/07/13 17:53:27 | Build of music database >> completed >> INFO | jvm 1 | 2008/07/13 17:53:27 | LOG: added factory >> INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperSimpleApp: main method >> completed >> INFO | jvm 1 | 2008/07/13 17:53:27 | Wrapper Manager: ShutdownHook >> started >> >> I am not sure what exactly your application does. But it says it is >> looking for playlists and is immediately done. The JVM (and not the >> Wrapper) then decides that the JVM should be shutdown. This happens >> either when something calls System.exit or when all non-daemon threads >> have completed. >> >> >From what I can see however, the Wrapper is working correctly. We >> need to figure out which of the above 2 reasons is causing your >> application to complete. >> >> Cheers, >> Leif >> >> > > > DEBUG | wrapper | 2008/07/13 21:43:18 | Spawning intermediate process... > DEBUG | wrapper | 2008/07/13 21:43:18 | Spawning daemon process... > STATUS | wrapper | 2008/07/13 21:43:18 | --> Wrapper Started as Daemon > DEBUG | wrapper | 2008/07/13 21:43:18 | Using tick timer. > DEBUG | wrapperp | 2008/07/13 21:43:18 | server listening on port 32000. > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[0] : /usr/bin/java > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[1] : > -Djava.library.path=../lib > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[2] : -classpath > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[3] : > ../lib/bananas.jar:../lib/hme.jar:../lib/commons-logging-1.1.1.jar:../lib/hme-hd-0.4.1.jar:../lib/wrapper.jar:../lib/hme-host-sample.jar:../lib/JID3.jar:../Harmonium.jar > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[4] : > -Dwrapper.key=ET43Bkcr8tgRfi6A > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[5] : -Dwrapper.port=32000 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[6] : > -Dwrapper.jvm.port.min=31000 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[7] : > -Dwrapper.jvm.port.max=31999 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[8] : -Dwrapper.debug=TRUE > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[9] : -Dwrapper.pid=6787 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[10] : > -Dwrapper.version=3.2.3 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[11] : > -Dwrapper.native_library=wrapper > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[12] : > -Dwrapper.service=TRUE > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[13] : > -Dwrapper.cpu.timeout=10 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[14] : -Dwrapper.jvmid=1 > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[15] : > org.tanukisoftware.wrapper.WrapperSimpleApp > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[16] : > com.tivo.hme.host.sample.Main > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[17] : > org.dazeend.harmonium.Harmonium > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[18] : -musicRoot > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[19] : > /home/ceperry/Harmonium/test_data/music > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[20] : -playlistRoot > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[21] : > /home/ceperry/Harmonium/test_data/playlists > DEBUG | wrapper | 2008/07/13 21:43:18 | Command[22] : -debug > STATUS | wrapper | 2008/07/13 21:43:18 | Launching a JVM... > INFO | jvm 1 | 2008/07/13 21:43:20 | WrapperManager class initialized > by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@1ba34f2 > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper (Version 3.2.3) > http://wrapper.tanukisoftware.org > INFO | jvm 1 | 2008/07/13 21:43:22 | Copyright 1999-2006 Tanuki > Software, Inc. All Rights Reserved. > INFO | jvm 1 | 2008/07/13 21:43:22 | > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: JVM #1 > INFO | jvm 1 | 2008/07/13 21:43:22 | Running a 32-bit JVM. > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: Registering > shutdown hook > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: Using wrapper > INFO | jvm 1 | 2008/07/13 21:43:22 | Load native library. One or more > attempts may fail if platform specific libraries do not exist. > INFO | jvm 1 | 2008/07/13 21:43:22 | Loading native library failed: > libwrapper-linux-x86-32.so Cause: java.lang.UnsatisfiedLinkError: no > wrapper-linux-x86-32 in java.library.path > INFO | jvm 1 | 2008/07/13 21:43:22 | Loaded native library: > libwrapper.so > INFO | jvm 1 | 2008/07/13 21:43:22 | Calling native initialization > method. > INFO | jvm 1 | 2008/07/13 21:43:22 | Inside native WrapperManager > initialization method > INFO | jvm 1 | 2008/07/13 21:43:22 | Java Version : 1.6.0_06-b02 Java > HotSpot(TM) Server VM > INFO | jvm 1 | 2008/07/13 21:43:22 | Java VM Vendor : Sun Microsystems > Inc. > INFO | jvm 1 | 2008/07/13 21:43:22 | > INFO | jvm 1 | 2008/07/13 21:43:22 | Startup runner thread started. > INFO | jvm 1 | 2008/07/13 21:43:22 | Control event monitor thread > started. > INFO | jvm 1 | 2008/07/13 21:43:22 | > WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@17bd6a1, > args["org.dazeend.harmonium.Harmonium", "-musicRoot", > "/home/ceperry/Harmonium/test_data/music", "-playlistRoot", > "/home/ceperry/Harmonium/test_data/playlists", "-debug"]) called by thread: > main > INFO | jvm 1 | 2008/07/13 21:43:22 | Communications runner thread > started. > INFO | jvm 1 | 2008/07/13 21:43:22 | Open socket to > wrapper...Wrapper-Connection > INFO | jvm 1 | 2008/07/13 21:43:22 | Opened Socket from 31000 to 32000 > INFO | jvm 1 | 2008/07/13 21:43:22 | Send a packet KEY : > ET43Bkcr8tgRfi6A > INFO | jvm 1 | 2008/07/13 21:43:22 | > handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) > DEBUG | wrapperp | 2008/07/13 21:43:22 | accepted a socket from 127.0.0.1 > on port 31000 > DEBUG | wrapperp | 2008/07/13 21:43:22 | read a packet KEY : > ET43Bkcr8tgRfi6A > DEBUG | wrapper | 2008/07/13 21:43:22 | Got key from JVM: ET43Bkcr8tgRfi6A > DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet LOW_LOG_LEVEL : 1 > DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet PING_TIMEOUT : 30 > DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet PROPERTIES : > (Property Values) > DEBUG | wrapper | 2008/07/13 21:43:22 | Start Application. > DEBUG | wrapperp | 2008/07/13 21:43:22 | send a packet START : start > INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet LOW_LOG_LEVEL : > 1 > INFO | jvm 1 | 2008/07/13 21:43:22 | Wrapper Manager: LowLogLevel from > Wrapper is 1 > INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet PING_TIMEOUT : > 30 > INFO | jvm 1 | 2008/07/13 21:43:22 | PingTimeout from Wrapper is 30000 > INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet PROPERTIES : > (Property Values) > INFO | jvm 1 | 2008/07/13 21:43:22 | Received a packet START : start > INFO | jvm 1 | 2008/07/13 21:43:22 | calling WrapperListener.start() > INFO | jvm 1 | 2008/07/13 21:43:22 | Waiting for WrapperListener.start > runner thread to complete. > INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperListener.start runner > thread started. > INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperSimpleApp: start(args) Will > wait up to 2 seconds for the main method to complete. > INFO | jvm 1 | 2008/07/13 21:43:22 | WrapperSimpleApp: invoking main > method > INFO | jvm 1 | 2008/07/13 21:43:22 | HME SDK 1.4 (TiVo, Inc.) > INFO | jvm 1 | 2008/07/13 21:43:23 | Searching for music... > INFO | jvm 1 | 2008/07/13 21:43:23 | DEBUG: reading file 1: Incomplete > Tags/Mixed No Art/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:23 | Send a packet START_PENDING : 5000 > DEBUG | wrapperp | 2008/07/13 21:43:23 | read a packet START_PENDING : 5000 > DEBUG | wrapper | 2008/07/13 21:43:23 | JVM signalled a start pending with > waitHint of 5000 millis. > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 2: Incomplete > Tags/Mixed No Art/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 3: Incomplete > Tags/Mixed No Art/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 4: Incomplete > Tags/Mixed No Art/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 5: Incomplete > Tags/No Artist and No Artist Album/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 6: Incomplete > Tags/No Artist and No Artist Album/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet START_PENDING : 5000 > INFO | jvm 1 | 2008/07/13 21:43:24 | WrapperSimpleApp: start(args) end. > Main Completed=false, exitCode=null > INFO | jvm 1 | 2008/07/13 21:43:24 | WrapperListener.start runner > thread stopped. > INFO | jvm 1 | 2008/07/13 21:43:24 | returned from > WrapperListener.start() > INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet STARTED : > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 7: Incomplete > Tags/No Artist and No Artist Album/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | Startup runner thread stopped. > DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet START_PENDING : 5000 > DEBUG | wrapper | 2008/07/13 21:43:24 | JVM signalled a start pending with > waitHint of 5000 millis. > DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet STARTED : > DEBUG | wrapper | 2008/07/13 21:43:24 | JVM signalled that it was started. > DEBUG | wrapperp | 2008/07/13 21:43:24 | send a packet PING : ping > INFO | jvm 1 | 2008/07/13 21:43:24 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/13 21:43:24 | Send a packet PING : ok > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 8: Incomplete > Tags/No Artist and No Artist Album/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 9: Incomplete > Tags/No Album/03 Candy Everybody Wants.mp3 > DEBUG | wrapperp | 2008/07/13 21:43:24 | read a packet PING : ok > DEBUG | wrapper | 2008/07/13 21:43:24 | Got ping response from JVM > INFO | jvm 1 | 2008/07/13 21:43:24 | DEBUG: reading file 10: Incomplete > Tags/No Album/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 11: Incomplete > Tags/No Album/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 12: Incomplete > Tags/No Album/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 13: Incomplete > Tags/No Artist Album/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 14: Incomplete > Tags/No Artist Album/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 15: Incomplete > Tags/No Artist Album/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 16: Incomplete > Tags/No Artist Album/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:25 | DEBUG: reading file 17: Incomplete > Tags/No Art/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 18: Incomplete > Tags/No Art/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 19: Incomplete > Tags/No Art/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 20: Incomplete > Tags/No Art/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 21: Incomplete > Tags/No Artist/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:26 | DEBUG: reading file 22: Incomplete > Tags/No Artist/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 23: Incomplete > Tags/No Artist/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 24: Incomplete > Tags/No Artist/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 25: Incomplete > Tags/No Track Name/03 Candy Everybody Wants.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 26: Incomplete > Tags/No Track Name/01 These Are Days.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 27: Incomplete > Tags/No Track Name/04 I'm Not the Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 28: Incomplete > Tags/No Track Name/02 Eat for Two.mp3 > INFO | jvm 1 | 2008/07/13 21:43:27 | DEBUG: reading file 29: Multi-disc > set/Album1/Disc 2/01 My Life.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 30: Multi-disc > set/Album1/Disc 2/02 Big Shot.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 31: Multi-disc > set/Album1/Disc 1/01 Piano Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 32: Multi-disc > set/Album1/Disc 1/02 Captain Jack.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 33: Multi-disc > set/Album2/02 An Innocent Man.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 34: Multi-disc > set/Album2/01 Keeping the Faith.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 35: Complete > tags/Four/03 Look Around.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 36: Complete > tags/Four/02 Stand.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 37: Complete > tags/Four/01 Run-Around.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 38: Complete > tags/Four/04 Fallible.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 39: Complete > tags/Save His Soul/03 Letter from a Friend.mp3 > DEBUG | wrapperp | 2008/07/13 21:43:28 | send a packet PING : ping > INFO | jvm 1 | 2008/07/13 21:43:28 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/13 21:43:28 | Send a packet PING : ok > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 40: Complete > tags/Save His Soul/02 Love and Greed.mp3 > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 41: Complete > tags/Save His Soul/01 Trina Magna.mp3 > DEBUG | wrapperp | 2008/07/13 21:43:28 | read a packet PING : ok > DEBUG | wrapper | 2008/07/13 21:43:28 | Got ping response from JVM > INFO | jvm 1 | 2008/07/13 21:43:28 | DEBUG: reading file 42: CEP3/07 > While My Guitar Gently Weeps.mp3 > INFO | jvm 1 | 2008/07/13 21:43:29 | DEBUG: reading file 43: CEP3/06 > The Continuing Story of Bungalow Bill.mp3 > INFO | jvm 1 | 2008/07/13 21:43:29 | Searching for playlists... > INFO | jvm 1 | 2008/07/13 21:43:29 | Build of music database completed > INFO | jvm 1 | 2008/07/13 21:43:29 | LOG: added factory > INFO | jvm 1 | 2008/07/13 21:43:29 | WrapperSimpleApp: main method > completed > INFO | jvm 1 | 2008/07/13 21:43:29 | Wrapper Manager: ShutdownHook > started > INFO | jvm 1 | 2008/07/13 21:43:29 | WrapperManager.stop(0) called by > thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/07/13 21:43:29 | Send a packet STOP : 0 > DEBUG | wrapperp | 2008/07/13 21:43:29 | read a packet STOP : 0 > DEBUG | wrapper | 2008/07/13 21:43:29 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2008/07/13 21:43:29 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2008/07/13 21:43:29 | Sending stop signal to JVM > DEBUG | wrapperp | 2008/07/13 21:43:29 | send a packet STOP : NULL > INFO | jvm 1 | 2008/07/13 21:43:29 | Received a packet STOP : > INFO | jvm 1 | 2008/07/13 21:43:30 | Thread, Wrapper-Shutdown-Hook, > handling the shutdown process. > INFO | jvm 1 | 2008/07/13 21:43:30 | calling listener.stop() > INFO | jvm 1 | 2008/07/13 21:43:30 | WrapperSimpleApp: stop(0) > INFO | jvm 1 | 2008/07/13 21:43:30 | returned from listener.stop() -> 0 > INFO | jvm 1 | 2008/07/13 21:43:30 | shutdownJVM(0) > Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/07/13 21:43:30 | Send a packet STOPPED : 0 > DEBUG | wrapperp | 2008/07/13 21:43:30 | read a packet STOPPED : 0 > DEBUG | wrapper | 2008/07/13 21:43:30 | JVM signalled that it was stopped. > INFO | jvm 1 | 2008/07/13 21:43:30 | Closing socket. > DEBUG | wrapperp | 2008/07/13 21:43:30 | socket read no code (closed?). > DEBUG | wrapperp | 2008/07/13 21:43:30 | server listening on port 32001. > DEBUG | wrapper | 2008/07/13 21:43:30 | JVM exited normally. > DEBUG | wrapper | 2008/07/13 21:43:30 | Signal trapped. Details: > DEBUG | wrapper | 2008/07/13 21:43:30 | signal number=17 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2008/07/13 21:43:30 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2008/07/13 21:43:30 | JVM process exited with a code of > 0, leaving the wrapper exit code set to 0. > INFO | jvm 1 | 2008/07/13 21:43:30 | Wrapper Manager: ShutdownHook > complete > INFO | jvm 1 | 2008/07/13 21:43:30 | Server daemon shut down > STATUS | wrapper | 2008/07/13 21:43:31 | <-- Wrapper Stopped > > #******************************************************************** > # Wrapper Properties > #******************************************************************** > # Java Application > wrapper.java.command=/usr/bin/java > > # Java Main class. This class must implement the WrapperListener interface > # or guarantee that the WrapperManager class is initialized. Helper > # classes are provided to do this for you. See the Integration section > # of the documentation for details. > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > > # Java Classpath (include wrapper.jar) Add class path elements as > # needed starting from 1 > wrapper.java.classpath.1=../lib/*.jar > wrapper.java.classpath.2=../Harmonium.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=../lib > > # Java Additional Parameters > #wrapper.java.additional.1= > > # Initial Java Heap Size (in MB) > #wrapper.java.initmemory=3 > > # Maximum Java Heap Size (in MB) > #wrapper.java.maxmemory=64 > > # Application parameters. Add parameters as needed starting from 1 > wrapper.app.parameter.1=com.tivo.hme.host.sample.Main > wrapper.app.parameter.2=org.dazeend.harmonium.Harmonium > wrapper.app.parameter.3=-musicRoot > wrapper.app.parameter.4=/home/ceperry/Harmonium/test_data/music > wrapper.app.parameter.4.stripquotes=TRUE > wrapper.app.parameter.5=-playlistRoot > wrapper.app.parameter.6=/home/ceperry/Harmonium/test_data/playlists > wrapper.app.parameter.6.stripquotes=TRUE > wrapper.app.parameter.7=-debug > > #******************************************************************** > # Wrapper Logging Properties > #******************************************************************** > # Format of output for the console. (See docs for formats) > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > #wrapper.console.loglevel=INFO > wrapper.console.loglevel=DEBUG > > # Log file to use for wrapper output logging. > wrapper.logfile=../logs/wrapper.log > > # Format of output for the log file. (See docs for formats) > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > #wrapper.logfile.loglevel=INFO > wrapper.logfile.loglevel=DEBUG > > # Maximum size that the log file will be allowed to grow to before > # the log is rolled. Size is specified in bytes. The default value > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > wrapper.logfile.maxsize=0 > > # Maximum number of rolled log files which will be allowed before old > # files are deleted. The default value of 0 implies no limit. > wrapper.logfile.maxfiles=0 > > # Log Level for sys/event log output. (See docs for log levels) > #wrapper.syslog.loglevel=NONE > wrapper.syslog.loglevel=DEBUG > > #******************************************************************** > # Wrapper Windows Properties > #******************************************************************** > # Title to use when running as a console > wra...@ap...@ > > #******************************************************************** > # Wrapper Windows NT/2000/XP Service Properties > #******************************************************************** > # WARNING - Do not modify any of these properties when an application > # using this configuration file has been installed as a service. > # Please uninstall the service before modifying this section. The > # service can then be reinstalled. > > # Name of the service > wra...@ap...@ > > # Display name of the service > wra...@ap...@ > > # Description of the service > wra...@ap...@ > > # Service dependencies. Add dependencies as needed starting from 1 > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > wrapper.ntservice.starttype=AUTO_START > > # Allow the service to interact with the desktop. > wrapper.ntservice.interactive=false > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Charles P. <c.e...@da...> - 2008-07-14 01:56:52
|
Leif, My application is an MP3 player that streams music from a networked PC to a TiVo DVR, thus the messages about playlists. What should be happening at the point in the logs timestamped with 17:53:21 ["Searching for music..."] in the log I previously sent is that harmonium is searching through a directory tree for mp3 files and setting up an internal data structure. This takes a few seconds with the small data set I use for testing, then it moves on to search for playlists at 17:53:27. I have no playlists in my set of test data, so it immediately announces "Build of music database completed". I'm attaching another log in which harmonium prints some debug messages. It doesn't really show much that's new other than it has successfully found the music directory and is loading mp3 files. In your email you said that there were two options you could think of. The first involved System.exit(). I don't call System.exit() in my program. (I just did a `find` to double check.) Are there other ways for that to be called other than through my code? The second was that "all non-daemon threads have completed." I'm not sure I completely understand that, but it seems to mean that harmonium decided that it was done and exited. Any ideas what might cause my program to bail out when the only thing that changed was the method of execution? After your comment about environment variables, I modified my wrapper.conf file to use the absolute path to java (/usr/bin/java). As far as I can tell, all file references in wrapper.conf now are either absolute paths, or are relative to the current directory (which should be ok, right?). I'm attaching my wrapper.conf for your reference. What else might be affected by a messed up environment variables? Should I modify the shell script you supplied to set a PATH environment variable? Sorry for all the questions, but thanks for the help. Charlie Leif Mortenson wrote: > Charles, > When Linux boots up, the environment used to launch daemon services > has very little in the way of an environment set up. Most likely > your system PATH and any other environment variables have not been set > up in this case. > > Looking at your log file, the following is interesting: > INFO | jvm 1 | 2008/07/13 17:53:27 | Searching for playlists... > INFO | jvm 1 | 2008/07/13 17:53:27 | Build of music database completed > INFO | jvm 1 | 2008/07/13 17:53:27 | LOG: added factory > INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperSimpleApp: main method > completed > INFO | jvm 1 | 2008/07/13 17:53:27 | Wrapper Manager: ShutdownHook > started > > I am not sure what exactly your application does. But it says it is > looking for playlists and is immediately done. The JVM (and not the > Wrapper) then decides that the JVM should be shutdown. This happens > either when something calls System.exit or when all non-daemon threads > have completed. > > >From what I can see however, the Wrapper is working correctly. We > need to figure out which of the above 2 reasons is causing your > application to complete. > > Cheers, > Leif > > |
|
From: Leif M. <le...@ta...> - 2008-07-14 00:56:08
|
Charles, When Linux boots up, the environment used to launch daemon services has very little in the way of an environment set up. Most likely your system PATH and any other environment variables have not been set up in this case. Looking at your log file, the following is interesting: INFO | jvm 1 | 2008/07/13 17:53:27 | Searching for playlists... INFO | jvm 1 | 2008/07/13 17:53:27 | Build of music database completed INFO | jvm 1 | 2008/07/13 17:53:27 | LOG: added factory INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperSimpleApp: main method completed INFO | jvm 1 | 2008/07/13 17:53:27 | Wrapper Manager: ShutdownHook started I am not sure what exactly your application does. But it says it is looking for playlists and is immediately done. The JVM (and not the Wrapper) then decides that the JVM should be shutdown. This happens either when something calls System.exit or when all non-daemon threads have completed. >From what I can see however, the Wrapper is working correctly. We need to figure out which of the above 2 reasons is causing your application to complete. Cheers, Leif On Mon, Jul 14, 2008 at 9:03 AM, Charles Perry <c.e...@da...> wrote: > I've installed version 3.2.3 of the Wrapper on my Ubuntu box (Hardy > Heron - 8.04). I configured the wrapper to start my program "harmonium", > then configured linux to start the service at boot (I symlinked in > /etc/init.d, then ran update-rc.d). When I 'cd' to /etc/init.d and run: > > sudo ./harmonium console > > everything works as expected. I can run my program and all is well. If I > just start the program with > > sudo ./harmonium start > > everything works as expected. The program happily rolls along until I do > a 'stop'. > > If I reboot the machine, harmonium is started at boot as expected, but > then it immediately stops. I don't know why. I'm hoping someone on here > can give me some guidance. > > I'm including DEBUG level logs below. > > Thanks, > > Charlie > > ##### BEGIN LOG ##### > DEBUG | wrapper | 2008/07/13 17:53:16 | Spawning intermediate process... > DEBUG | wrapper | 2008/07/13 17:53:16 | Spawning daemon process... > STATUS | wrapper | 2008/07/13 17:53:16 | --> Wrapper Started as Daemon > DEBUG | wrapper | 2008/07/13 17:53:16 | Using tick timer. > DEBUG | wrapperp | 2008/07/13 17:53:16 | server listening on port 32000. > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[0] : java > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[1] : > -Djava.library.path=../lib > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[2] : -classpath > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[3] : > ../lib/bananas.jar:../lib/hme.jar:../lib/commons-logging-1.1.1.jar:../lib/hme-hd-0.4.1.jar:../lib/wrapper.jar:../lib/hme-host-sample.jar:../lib/JID3.jar:../Harmonium.jar > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[4] : > -Dwrapper.key=P6TgVO2G8iqqxuI1 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[5] : -Dwrapper.port=32000 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[6] : > -Dwrapper.jvm.port.min=31000 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[7] : > -Dwrapper.jvm.port.max=31999 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[8] : -Dwrapper.debug=TRUE > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[9] : -Dwrapper.pid=5902 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[10] : > -Dwrapper.version=3.2.3 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[11] : > -Dwrapper.native_library=wrapper > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[12] : > -Dwrapper.service=TRUE > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[13] : > -Dwrapper.cpu.timeout=10 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[14] : -Dwrapper.jvmid=1 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[15] : > org.tanukisoftware.wrapper.WrapperSimpleApp > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[16] : > com.tivo.hme.host.sample.Main > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[17] : > org.dazeend.harmonium.Harmonium > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[18] : -musicRoot > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[19] : > /home/ceperry/Harmonium/test_data/music > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[20] : -playlistRoot > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[21] : > /home/ceperry/Harmonium/test_data/playlists > STATUS | wrapper | 2008/07/13 17:53:17 | Launching a JVM... > INFO | jvm 1 | 2008/07/13 17:53:19 | WrapperManager class > initialized by thread: main Using classloader: > sun.misc.Launcher$AppClassLoader@1ba34f2 > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper (Version 3.2.3) > http://wrapper.tanukisoftware.org > INFO | jvm 1 | 2008/07/13 17:53:21 | Copyright 1999-2006 Tanuki > Software, Inc. All Rights Reserved. > INFO | jvm 1 | 2008/07/13 17:53:21 | > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: JVM #1 > INFO | jvm 1 | 2008/07/13 17:53:21 | Running a 32-bit JVM. > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: Registering > shutdown hook > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: Using wrapper > INFO | jvm 1 | 2008/07/13 17:53:21 | Load native library. One or > more attempts may fail if platform specific libraries do not exist. > INFO | jvm 1 | 2008/07/13 17:53:21 | Loading native library failed: > libwrapper-linux-x86-32.so Cause: java.lang.UnsatisfiedLinkError: no > wrapper-linux-x86-32 in java.library.path > INFO | jvm 1 | 2008/07/13 17:53:21 | Loaded native library: > libwrapper.so > INFO | jvm 1 | 2008/07/13 17:53:21 | Calling native initialization > method. > INFO | jvm 1 | 2008/07/13 17:53:21 | Inside native WrapperManager > initialization method > INFO | jvm 1 | 2008/07/13 17:53:21 | Java Version : 1.6.0_06-b02 > Java HotSpot(TM) Server VM > INFO | jvm 1 | 2008/07/13 17:53:21 | Java VM Vendor : Sun > Microsystems Inc. > INFO | jvm 1 | 2008/07/13 17:53:21 | > INFO | jvm 1 | 2008/07/13 17:53:21 | Startup runner thread started. > INFO | jvm 1 | 2008/07/13 17:53:21 | Control event monitor thread > started. > INFO | jvm 1 | 2008/07/13 17:53:21 | > WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@17bd6a1, > args["org.dazeend.harmonium.Harmonium", "-musicRoot", > "/home/ceperry/Harmonium/test_data/music", "-playlistRoot", > "/home/ceperry/Harmonium/test_data/playlists"]) called by thread: main > INFO | jvm 1 | 2008/07/13 17:53:21 | Communications runner thread > started. > INFO | jvm 1 | 2008/07/13 17:53:21 | Open socket to > wrapper...Wrapper-Connection > INFO | jvm 1 | 2008/07/13 17:53:21 | Opened Socket from 31000 to 32000 > INFO | jvm 1 | 2008/07/13 17:53:21 | Send a packet KEY : > P6TgVO2G8iqqxuI1 > INFO | jvm 1 | 2008/07/13 17:53:21 | > handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) > DEBUG | wrapperp | 2008/07/13 17:53:21 | accepted a socket from > 127.0.0.1 on port 31000 > DEBUG | wrapperp | 2008/07/13 17:53:21 | read a packet KEY : > P6TgVO2G8iqqxuI1 > DEBUG | wrapper | 2008/07/13 17:53:21 | Got key from JVM: P6TgVO2G8iqqxuI1 > DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet LOW_LOG_LEVEL : 1 > DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet PING_TIMEOUT : 30 > DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet PROPERTIES : > (Property Values) > DEBUG | wrapper | 2008/07/13 17:53:21 | Start Application. > DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet START : start > INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet > LOW_LOG_LEVEL : 1 > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: LowLogLevel > from Wrapper is 1 > INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet PING_TIMEOUT > : 30 > INFO | jvm 1 | 2008/07/13 17:53:21 | PingTimeout from Wrapper is 30000 > INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet PROPERTIES : > (Property Values) > INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet START : start > INFO | jvm 1 | 2008/07/13 17:53:21 | calling WrapperListener.start() > INFO | jvm 1 | 2008/07/13 17:53:21 | Waiting for > WrapperListener.start runner thread to complete. > INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperListener.start runner > thread started. > INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperSimpleApp: start(args) > Will wait up to 2 seconds for the main method to complete. > INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperSimpleApp: invoking > main method > INFO | jvm 1 | 2008/07/13 17:53:21 | HME SDK 1.4 (TiVo, Inc.) > INFO | jvm 1 | 2008/07/13 17:53:21 | Searching for music... > INFO | jvm 1 | 2008/07/13 17:53:22 | Send a packet START_PENDING : 5000 > DEBUG | wrapperp | 2008/07/13 17:53:22 | read a packet START_PENDING : 5000 > DEBUG | wrapper | 2008/07/13 17:53:22 | JVM signalled a start pending > with waitHint of 5000 millis. > INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet START_PENDING : 5000 > INFO | jvm 1 | 2008/07/13 17:53:23 | WrapperSimpleApp: start(args) > end. Main Completed=false, exitCode=null > INFO | jvm 1 | 2008/07/13 17:53:23 | WrapperListener.start runner > thread stopped. > INFO | jvm 1 | 2008/07/13 17:53:23 | returned from > WrapperListener.start() > INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet STARTED : > INFO | jvm 1 | 2008/07/13 17:53:23 | Startup runner thread stopped. > DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet START_PENDING : 5000 > DEBUG | wrapper | 2008/07/13 17:53:23 | JVM signalled a start pending > with waitHint of 5000 millis. > DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet STARTED : > DEBUG | wrapper | 2008/07/13 17:53:23 | JVM signalled that it was started. > DEBUG | wrapperp | 2008/07/13 17:53:23 | send a packet PING : ping > INFO | jvm 1 | 2008/07/13 17:53:23 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet PING : ok > DEBUG | wrapper | 2008/07/13 17:53:23 | Got ping response from JVM > DEBUG | wrapperp | 2008/07/13 17:53:27 | send a packet PING : ping > INFO | jvm 1 | 2008/07/13 17:53:27 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/13 17:53:27 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/13 17:53:27 | read a packet PING : ok > DEBUG | wrapper | 2008/07/13 17:53:27 | Got ping response from JVM > INFO | jvm 1 | 2008/07/13 17:53:27 | Searching for playlists... > INFO | jvm 1 | 2008/07/13 17:53:27 | Build of music database completed > INFO | jvm 1 | 2008/07/13 17:53:27 | LOG: added factory > INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperSimpleApp: main method > completed > INFO | jvm 1 | 2008/07/13 17:53:27 | Wrapper Manager: ShutdownHook > started > INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperManager.stop(0) called > by thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/07/13 17:53:27 | Send a packet STOP : 0 > DEBUG | wrapperp | 2008/07/13 17:53:27 | read a packet STOP : 0 > DEBUG | wrapper | 2008/07/13 17:53:27 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2008/07/13 17:53:27 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2008/07/13 17:53:27 | Sending stop signal to JVM > DEBUG | wrapperp | 2008/07/13 17:53:27 | send a packet STOP : NULL > INFO | jvm 1 | 2008/07/13 17:53:27 | Received a packet STOP : > INFO | jvm 1 | 2008/07/13 17:53:28 | Thread, Wrapper-Shutdown-Hook, > handling the shutdown process. > INFO | jvm 1 | 2008/07/13 17:53:28 | calling listener.stop() > INFO | jvm 1 | 2008/07/13 17:53:28 | WrapperSimpleApp: stop(0) > INFO | jvm 1 | 2008/07/13 17:53:28 | returned from listener.stop() -> 0 > INFO | jvm 1 | 2008/07/13 17:53:28 | shutdownJVM(0) > Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/07/13 17:53:28 | Send a packet STOPPED : 0 > DEBUG | wrapperp | 2008/07/13 17:53:28 | read a packet STOPPED : 0 > DEBUG | wrapper | 2008/07/13 17:53:28 | JVM signalled that it was stopped. > INFO | jvm 1 | 2008/07/13 17:53:29 | Closing socket. > DEBUG | wrapperp | 2008/07/13 17:53:29 | socket read no code (closed?). > DEBUG | wrapperp | 2008/07/13 17:53:29 | server listening on port 32001. > DEBUG | wrapper | 2008/07/13 17:53:29 | JVM exited normally. > DEBUG | wrapper | 2008/07/13 17:53:29 | Signal trapped. Details: > DEBUG | wrapper | 2008/07/13 17:53:29 | signal number=17 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2008/07/13 17:53:29 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2008/07/13 17:53:29 | JVM process exited with a code > of 0, leaving the wrapper exit code set to 0. > INFO | jvm 1 | 2008/07/13 17:53:29 | Wrapper Manager: ShutdownHook > complete > INFO | jvm 1 | 2008/07/13 17:53:29 | Server daemon shut down > STATUS | wrapper | 2008/07/13 17:53:29 | <-- Wrapper Stopped > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Matthew C. <ma...@ma...> - 2008-07-14 00:49:01
|
just a cursory look here... I think you may have your environment set up with a proper CLASSPATH when you're logged in... but, on system boot I don't think the script has the proper environment set up. Try setting the CLASSPATH, PATH, etc. in the boot script so your program will have all that it needs to properly execute. Matt On Sun, Jul 13, 2008 at 5:03 PM, Charles Perry <c.e...@da...> wrote: > I've installed version 3.2.3 of the Wrapper on my Ubuntu box (Hardy > Heron - 8.04). I configured the wrapper to start my program "harmonium", > then configured linux to start the service at boot (I symlinked in > /etc/init.d, then ran update-rc.d). When I 'cd' to /etc/init.d and run: > > sudo ./harmonium console > > everything works as expected. I can run my program and all is well. If I > just start the program with > > sudo ./harmonium start > > everything works as expected. The program happily rolls along until I do > a 'stop'. > > If I reboot the machine, harmonium is started at boot as expected, but > then it immediately stops. I don't know why. I'm hoping someone on here > can give me some guidance. > > I'm including DEBUG level logs below. > > Thanks, > > Charlie > > ##### BEGIN LOG ##### > DEBUG | wrapper | 2008/07/13 17:53:16 | Spawning intermediate process... > DEBUG | wrapper | 2008/07/13 17:53:16 | Spawning daemon process... > STATUS | wrapper | 2008/07/13 17:53:16 | --> Wrapper Started as Daemon > DEBUG | wrapper | 2008/07/13 17:53:16 | Using tick timer. > DEBUG | wrapperp | 2008/07/13 17:53:16 | server listening on port 32000. > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[0] : java > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[1] : > -Djava.library.path=../lib > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[2] : -classpath > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[3] : > > ../lib/bananas.jar:../lib/hme.jar:../lib/commons-logging-1.1.1.jar:../lib/hme-hd-0.4.1.jar:../lib/wrapper.jar:../lib/hme-host-sample.jar:../lib/JID3.jar:../Harmonium.jar > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[4] : > -Dwrapper.key=P6TgVO2G8iqqxuI1 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[5] : -Dwrapper.port=32000 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[6] : > -Dwrapper.jvm.port.min=31000 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[7] : > -Dwrapper.jvm.port.max=31999 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[8] : -Dwrapper.debug=TRUE > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[9] : -Dwrapper.pid=5902 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[10] : > -Dwrapper.version=3.2.3 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[11] : > -Dwrapper.native_library=wrapper > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[12] : > -Dwrapper.service=TRUE > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[13] : > -Dwrapper.cpu.timeout=10 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[14] : -Dwrapper.jvmid=1 > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[15] : > org.tanukisoftware.wrapper.WrapperSimpleApp > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[16] : > com.tivo.hme.host.sample.Main > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[17] : > org.dazeend.harmonium.Harmonium > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[18] : -musicRoot > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[19] : > /home/ceperry/Harmonium/test_data/music > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[20] : -playlistRoot > DEBUG | wrapper | 2008/07/13 17:53:17 | Command[21] : > /home/ceperry/Harmonium/test_data/playlists > STATUS | wrapper | 2008/07/13 17:53:17 | Launching a JVM... > INFO | jvm 1 | 2008/07/13 17:53:19 | WrapperManager class > initialized by thread: main Using classloader: > sun.misc.Launcher$AppClassLoader@1ba34f2 > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper (Version 3.2.3) > http://wrapper.tanukisoftware.org > INFO | jvm 1 | 2008/07/13 17:53:21 | Copyright 1999-2006 Tanuki > Software, Inc. All Rights Reserved. > INFO | jvm 1 | 2008/07/13 17:53:21 | > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: JVM #1 > INFO | jvm 1 | 2008/07/13 17:53:21 | Running a 32-bit JVM. > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: Registering > shutdown hook > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: Using wrapper > INFO | jvm 1 | 2008/07/13 17:53:21 | Load native library. One or > more attempts may fail if platform specific libraries do not exist. > INFO | jvm 1 | 2008/07/13 17:53:21 | Loading native library failed: > libwrapper-linux-x86-32.so Cause: java.lang.UnsatisfiedLinkError: no > wrapper-linux-x86-32 in java.library.path > INFO | jvm 1 | 2008/07/13 17:53:21 | Loaded native library: > libwrapper.so > INFO | jvm 1 | 2008/07/13 17:53:21 | Calling native initialization > method. > INFO | jvm 1 | 2008/07/13 17:53:21 | Inside native WrapperManager > initialization method > INFO | jvm 1 | 2008/07/13 17:53:21 | Java Version : 1.6.0_06-b02 > Java HotSpot(TM) Server VM > INFO | jvm 1 | 2008/07/13 17:53:21 | Java VM Vendor : Sun > Microsystems Inc. > INFO | jvm 1 | 2008/07/13 17:53:21 | > INFO | jvm 1 | 2008/07/13 17:53:21 | Startup runner thread started. > INFO | jvm 1 | 2008/07/13 17:53:21 | Control event monitor thread > started. > INFO | jvm 1 | 2008/07/13 17:53:21 | > WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@17bd6a1, > args["org.dazeend.harmonium.Harmonium", "-musicRoot", > "/home/ceperry/Harmonium/test_data/music", "-playlistRoot", > "/home/ceperry/Harmonium/test_data/playlists"]) called by thread: main > INFO | jvm 1 | 2008/07/13 17:53:21 | Communications runner thread > started. > INFO | jvm 1 | 2008/07/13 17:53:21 | Open socket to > wrapper...Wrapper-Connection > INFO | jvm 1 | 2008/07/13 17:53:21 | Opened Socket from 31000 to 32000 > INFO | jvm 1 | 2008/07/13 17:53:21 | Send a packet KEY : > P6TgVO2G8iqqxuI1 > INFO | jvm 1 | 2008/07/13 17:53:21 | > handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) > DEBUG | wrapperp | 2008/07/13 17:53:21 | accepted a socket from > 127.0.0.1 on port 31000 > DEBUG | wrapperp | 2008/07/13 17:53:21 | read a packet KEY : > P6TgVO2G8iqqxuI1 > DEBUG | wrapper | 2008/07/13 17:53:21 | Got key from JVM: > P6TgVO2G8iqqxuI1 > DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet LOW_LOG_LEVEL : 1 > DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet PING_TIMEOUT : 30 > DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet PROPERTIES : > (Property Values) > DEBUG | wrapper | 2008/07/13 17:53:21 | Start Application. > DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet START : start > INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet > LOW_LOG_LEVEL : 1 > INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: LowLogLevel > from Wrapper is 1 > INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet PING_TIMEOUT > : 30 > INFO | jvm 1 | 2008/07/13 17:53:21 | PingTimeout from Wrapper is 30000 > INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet PROPERTIES : > (Property Values) > INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet START : start > INFO | jvm 1 | 2008/07/13 17:53:21 | calling WrapperListener.start() > INFO | jvm 1 | 2008/07/13 17:53:21 | Waiting for > WrapperListener.start runner thread to complete. > INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperListener.start runner > thread started. > INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperSimpleApp: start(args) > Will wait up to 2 seconds for the main method to complete. > INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperSimpleApp: invoking > main method > INFO | jvm 1 | 2008/07/13 17:53:21 | HME SDK 1.4 (TiVo, Inc.) > INFO | jvm 1 | 2008/07/13 17:53:21 | Searching for music... > INFO | jvm 1 | 2008/07/13 17:53:22 | Send a packet START_PENDING : > 5000 > DEBUG | wrapperp | 2008/07/13 17:53:22 | read a packet START_PENDING : > 5000 > DEBUG | wrapper | 2008/07/13 17:53:22 | JVM signalled a start pending > with waitHint of 5000 millis. > INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet START_PENDING : > 5000 > INFO | jvm 1 | 2008/07/13 17:53:23 | WrapperSimpleApp: start(args) > end. Main Completed=false, exitCode=null > INFO | jvm 1 | 2008/07/13 17:53:23 | WrapperListener.start runner > thread stopped. > INFO | jvm 1 | 2008/07/13 17:53:23 | returned from > WrapperListener.start() > INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet STARTED : > INFO | jvm 1 | 2008/07/13 17:53:23 | Startup runner thread stopped. > DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet START_PENDING : > 5000 > DEBUG | wrapper | 2008/07/13 17:53:23 | JVM signalled a start pending > with waitHint of 5000 millis. > DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet STARTED : > DEBUG | wrapper | 2008/07/13 17:53:23 | JVM signalled that it was > started. > DEBUG | wrapperp | 2008/07/13 17:53:23 | send a packet PING : ping > INFO | jvm 1 | 2008/07/13 17:53:23 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet PING : ok > DEBUG | wrapper | 2008/07/13 17:53:23 | Got ping response from JVM > DEBUG | wrapperp | 2008/07/13 17:53:27 | send a packet PING : ping > INFO | jvm 1 | 2008/07/13 17:53:27 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/13 17:53:27 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/13 17:53:27 | read a packet PING : ok > DEBUG | wrapper | 2008/07/13 17:53:27 | Got ping response from JVM > INFO | jvm 1 | 2008/07/13 17:53:27 | Searching for playlists... > INFO | jvm 1 | 2008/07/13 17:53:27 | Build of music database completed > INFO | jvm 1 | 2008/07/13 17:53:27 | LOG: added factory > INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperSimpleApp: main method > completed > INFO | jvm 1 | 2008/07/13 17:53:27 | Wrapper Manager: ShutdownHook > started > INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperManager.stop(0) called > by thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/07/13 17:53:27 | Send a packet STOP : 0 > DEBUG | wrapperp | 2008/07/13 17:53:27 | read a packet STOP : 0 > DEBUG | wrapper | 2008/07/13 17:53:27 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2008/07/13 17:53:27 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2008/07/13 17:53:27 | Sending stop signal to JVM > DEBUG | wrapperp | 2008/07/13 17:53:27 | send a packet STOP : NULL > INFO | jvm 1 | 2008/07/13 17:53:27 | Received a packet STOP : > INFO | jvm 1 | 2008/07/13 17:53:28 | Thread, Wrapper-Shutdown-Hook, > handling the shutdown process. > INFO | jvm 1 | 2008/07/13 17:53:28 | calling listener.stop() > INFO | jvm 1 | 2008/07/13 17:53:28 | WrapperSimpleApp: stop(0) > INFO | jvm 1 | 2008/07/13 17:53:28 | returned from listener.stop() -> > 0 > INFO | jvm 1 | 2008/07/13 17:53:28 | shutdownJVM(0) > Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2008/07/13 17:53:28 | Send a packet STOPPED : 0 > DEBUG | wrapperp | 2008/07/13 17:53:28 | read a packet STOPPED : 0 > DEBUG | wrapper | 2008/07/13 17:53:28 | JVM signalled that it was > stopped. > INFO | jvm 1 | 2008/07/13 17:53:29 | Closing socket. > DEBUG | wrapperp | 2008/07/13 17:53:29 | socket read no code (closed?). > DEBUG | wrapperp | 2008/07/13 17:53:29 | server listening on port 32001. > DEBUG | wrapper | 2008/07/13 17:53:29 | JVM exited normally. > DEBUG | wrapper | 2008/07/13 17:53:29 | Signal trapped. Details: > DEBUG | wrapper | 2008/07/13 17:53:29 | signal number=17 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2008/07/13 17:53:29 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2008/07/13 17:53:29 | JVM process exited with a code > of 0, leaving the wrapper exit code set to 0. > INFO | jvm 1 | 2008/07/13 17:53:29 | Wrapper Manager: ShutdownHook > complete > INFO | jvm 1 | 2008/07/13 17:53:29 | Server daemon shut down > STATUS | wrapper | 2008/07/13 17:53:29 | <-- Wrapper Stopped > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Charles P. <c.e...@da...> - 2008-07-14 00:03:25
|
I've installed version 3.2.3 of the Wrapper on my Ubuntu box (Hardy Heron - 8.04). I configured the wrapper to start my program "harmonium", then configured linux to start the service at boot (I symlinked in /etc/init.d, then ran update-rc.d). When I 'cd' to /etc/init.d and run: sudo ./harmonium console everything works as expected. I can run my program and all is well. If I just start the program with sudo ./harmonium start everything works as expected. The program happily rolls along until I do a 'stop'. If I reboot the machine, harmonium is started at boot as expected, but then it immediately stops. I don't know why. I'm hoping someone on here can give me some guidance. I'm including DEBUG level logs below. Thanks, Charlie ##### BEGIN LOG ##### DEBUG | wrapper | 2008/07/13 17:53:16 | Spawning intermediate process... DEBUG | wrapper | 2008/07/13 17:53:16 | Spawning daemon process... STATUS | wrapper | 2008/07/13 17:53:16 | --> Wrapper Started as Daemon DEBUG | wrapper | 2008/07/13 17:53:16 | Using tick timer. DEBUG | wrapperp | 2008/07/13 17:53:16 | server listening on port 32000. DEBUG | wrapper | 2008/07/13 17:53:17 | Command[0] : java DEBUG | wrapper | 2008/07/13 17:53:17 | Command[1] : -Djava.library.path=../lib DEBUG | wrapper | 2008/07/13 17:53:17 | Command[2] : -classpath DEBUG | wrapper | 2008/07/13 17:53:17 | Command[3] : ../lib/bananas.jar:../lib/hme.jar:../lib/commons-logging-1.1.1.jar:../lib/hme-hd-0.4.1.jar:../lib/wrapper.jar:../lib/hme-host-sample.jar:../lib/JID3.jar:../Harmonium.jar DEBUG | wrapper | 2008/07/13 17:53:17 | Command[4] : -Dwrapper.key=P6TgVO2G8iqqxuI1 DEBUG | wrapper | 2008/07/13 17:53:17 | Command[5] : -Dwrapper.port=32000 DEBUG | wrapper | 2008/07/13 17:53:17 | Command[6] : -Dwrapper.jvm.port.min=31000 DEBUG | wrapper | 2008/07/13 17:53:17 | Command[7] : -Dwrapper.jvm.port.max=31999 DEBUG | wrapper | 2008/07/13 17:53:17 | Command[8] : -Dwrapper.debug=TRUE DEBUG | wrapper | 2008/07/13 17:53:17 | Command[9] : -Dwrapper.pid=5902 DEBUG | wrapper | 2008/07/13 17:53:17 | Command[10] : -Dwrapper.version=3.2.3 DEBUG | wrapper | 2008/07/13 17:53:17 | Command[11] : -Dwrapper.native_library=wrapper DEBUG | wrapper | 2008/07/13 17:53:17 | Command[12] : -Dwrapper.service=TRUE DEBUG | wrapper | 2008/07/13 17:53:17 | Command[13] : -Dwrapper.cpu.timeout=10 DEBUG | wrapper | 2008/07/13 17:53:17 | Command[14] : -Dwrapper.jvmid=1 DEBUG | wrapper | 2008/07/13 17:53:17 | Command[15] : org.tanukisoftware.wrapper.WrapperSimpleApp DEBUG | wrapper | 2008/07/13 17:53:17 | Command[16] : com.tivo.hme.host.sample.Main DEBUG | wrapper | 2008/07/13 17:53:17 | Command[17] : org.dazeend.harmonium.Harmonium DEBUG | wrapper | 2008/07/13 17:53:17 | Command[18] : -musicRoot DEBUG | wrapper | 2008/07/13 17:53:17 | Command[19] : /home/ceperry/Harmonium/test_data/music DEBUG | wrapper | 2008/07/13 17:53:17 | Command[20] : -playlistRoot DEBUG | wrapper | 2008/07/13 17:53:17 | Command[21] : /home/ceperry/Harmonium/test_data/playlists STATUS | wrapper | 2008/07/13 17:53:17 | Launching a JVM... INFO | jvm 1 | 2008/07/13 17:53:19 | WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@1ba34f2 INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 1 | 2008/07/13 17:53:21 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 1 | 2008/07/13 17:53:21 | INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: JVM #1 INFO | jvm 1 | 2008/07/13 17:53:21 | Running a 32-bit JVM. INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: Registering shutdown hook INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: Using wrapper INFO | jvm 1 | 2008/07/13 17:53:21 | Load native library. One or more attempts may fail if platform specific libraries do not exist. INFO | jvm 1 | 2008/07/13 17:53:21 | Loading native library failed: libwrapper-linux-x86-32.so Cause: java.lang.UnsatisfiedLinkError: no wrapper-linux-x86-32 in java.library.path INFO | jvm 1 | 2008/07/13 17:53:21 | Loaded native library: libwrapper.so INFO | jvm 1 | 2008/07/13 17:53:21 | Calling native initialization method. INFO | jvm 1 | 2008/07/13 17:53:21 | Inside native WrapperManager initialization method INFO | jvm 1 | 2008/07/13 17:53:21 | Java Version : 1.6.0_06-b02 Java HotSpot(TM) Server VM INFO | jvm 1 | 2008/07/13 17:53:21 | Java VM Vendor : Sun Microsystems Inc. INFO | jvm 1 | 2008/07/13 17:53:21 | INFO | jvm 1 | 2008/07/13 17:53:21 | Startup runner thread started. INFO | jvm 1 | 2008/07/13 17:53:21 | Control event monitor thread started. INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@17bd6a1, args["org.dazeend.harmonium.Harmonium", "-musicRoot", "/home/ceperry/Harmonium/test_data/music", "-playlistRoot", "/home/ceperry/Harmonium/test_data/playlists"]) called by thread: main INFO | jvm 1 | 2008/07/13 17:53:21 | Communications runner thread started. INFO | jvm 1 | 2008/07/13 17:53:21 | Open socket to wrapper...Wrapper-Connection INFO | jvm 1 | 2008/07/13 17:53:21 | Opened Socket from 31000 to 32000 INFO | jvm 1 | 2008/07/13 17:53:21 | Send a packet KEY : P6TgVO2G8iqqxuI1 INFO | jvm 1 | 2008/07/13 17:53:21 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) DEBUG | wrapperp | 2008/07/13 17:53:21 | accepted a socket from 127.0.0.1 on port 31000 DEBUG | wrapperp | 2008/07/13 17:53:21 | read a packet KEY : P6TgVO2G8iqqxuI1 DEBUG | wrapper | 2008/07/13 17:53:21 | Got key from JVM: P6TgVO2G8iqqxuI1 DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet PING_TIMEOUT : 30 DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2008/07/13 17:53:21 | Start Application. DEBUG | wrapperp | 2008/07/13 17:53:21 | send a packet START : start INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet LOW_LOG_LEVEL : 1 INFO | jvm 1 | 2008/07/13 17:53:21 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet PING_TIMEOUT : 30 INFO | jvm 1 | 2008/07/13 17:53:21 | PingTimeout from Wrapper is 30000 INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet PROPERTIES : (Property Values) INFO | jvm 1 | 2008/07/13 17:53:21 | Received a packet START : start INFO | jvm 1 | 2008/07/13 17:53:21 | calling WrapperListener.start() INFO | jvm 1 | 2008/07/13 17:53:21 | Waiting for WrapperListener.start runner thread to complete. INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperListener.start runner thread started. INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. INFO | jvm 1 | 2008/07/13 17:53:21 | WrapperSimpleApp: invoking main method INFO | jvm 1 | 2008/07/13 17:53:21 | HME SDK 1.4 (TiVo, Inc.) INFO | jvm 1 | 2008/07/13 17:53:21 | Searching for music... INFO | jvm 1 | 2008/07/13 17:53:22 | Send a packet START_PENDING : 5000 DEBUG | wrapperp | 2008/07/13 17:53:22 | read a packet START_PENDING : 5000 DEBUG | wrapper | 2008/07/13 17:53:22 | JVM signalled a start pending with waitHint of 5000 millis. INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet START_PENDING : 5000 INFO | jvm 1 | 2008/07/13 17:53:23 | WrapperSimpleApp: start(args) end. Main Completed=false, exitCode=null INFO | jvm 1 | 2008/07/13 17:53:23 | WrapperListener.start runner thread stopped. INFO | jvm 1 | 2008/07/13 17:53:23 | returned from WrapperListener.start() INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet STARTED : INFO | jvm 1 | 2008/07/13 17:53:23 | Startup runner thread stopped. DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet START_PENDING : 5000 DEBUG | wrapper | 2008/07/13 17:53:23 | JVM signalled a start pending with waitHint of 5000 millis. DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet STARTED : DEBUG | wrapper | 2008/07/13 17:53:23 | JVM signalled that it was started. DEBUG | wrapperp | 2008/07/13 17:53:23 | send a packet PING : ping INFO | jvm 1 | 2008/07/13 17:53:23 | Received a packet PING : ping INFO | jvm 1 | 2008/07/13 17:53:23 | Send a packet PING : ok DEBUG | wrapperp | 2008/07/13 17:53:23 | read a packet PING : ok DEBUG | wrapper | 2008/07/13 17:53:23 | Got ping response from JVM DEBUG | wrapperp | 2008/07/13 17:53:27 | send a packet PING : ping INFO | jvm 1 | 2008/07/13 17:53:27 | Received a packet PING : ping INFO | jvm 1 | 2008/07/13 17:53:27 | Send a packet PING : ok DEBUG | wrapperp | 2008/07/13 17:53:27 | read a packet PING : ok DEBUG | wrapper | 2008/07/13 17:53:27 | Got ping response from JVM INFO | jvm 1 | 2008/07/13 17:53:27 | Searching for playlists... INFO | jvm 1 | 2008/07/13 17:53:27 | Build of music database completed INFO | jvm 1 | 2008/07/13 17:53:27 | LOG: added factory INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperSimpleApp: main method completed INFO | jvm 1 | 2008/07/13 17:53:27 | Wrapper Manager: ShutdownHook started INFO | jvm 1 | 2008/07/13 17:53:27 | WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook INFO | jvm 1 | 2008/07/13 17:53:27 | Send a packet STOP : 0 DEBUG | wrapperp | 2008/07/13 17:53:27 | read a packet STOP : 0 DEBUG | wrapper | 2008/07/13 17:53:27 | JVM requested a shutdown. (0) DEBUG | wrapper | 2008/07/13 17:53:27 | wrapperStopProcess(0) called. DEBUG | wrapper | 2008/07/13 17:53:27 | Sending stop signal to JVM DEBUG | wrapperp | 2008/07/13 17:53:27 | send a packet STOP : NULL INFO | jvm 1 | 2008/07/13 17:53:27 | Received a packet STOP : INFO | jvm 1 | 2008/07/13 17:53:28 | Thread, Wrapper-Shutdown-Hook, handling the shutdown process. INFO | jvm 1 | 2008/07/13 17:53:28 | calling listener.stop() INFO | jvm 1 | 2008/07/13 17:53:28 | WrapperSimpleApp: stop(0) INFO | jvm 1 | 2008/07/13 17:53:28 | returned from listener.stop() -> 0 INFO | jvm 1 | 2008/07/13 17:53:28 | shutdownJVM(0) Thread:Wrapper-Shutdown-Hook INFO | jvm 1 | 2008/07/13 17:53:28 | Send a packet STOPPED : 0 DEBUG | wrapperp | 2008/07/13 17:53:28 | read a packet STOPPED : 0 DEBUG | wrapper | 2008/07/13 17:53:28 | JVM signalled that it was stopped. INFO | jvm 1 | 2008/07/13 17:53:29 | Closing socket. DEBUG | wrapperp | 2008/07/13 17:53:29 | socket read no code (closed?). DEBUG | wrapperp | 2008/07/13 17:53:29 | server listening on port 32001. DEBUG | wrapper | 2008/07/13 17:53:29 | JVM exited normally. DEBUG | wrapper | 2008/07/13 17:53:29 | Signal trapped. Details: DEBUG | wrapper | 2008/07/13 17:53:29 | signal number=17 (SIGCHLD), source="unknown" DEBUG | wrapper | 2008/07/13 17:53:29 | Received SIGCHLD, checking JVM process status. DEBUG | wrapper | 2008/07/13 17:53:29 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. INFO | jvm 1 | 2008/07/13 17:53:29 | Wrapper Manager: ShutdownHook complete INFO | jvm 1 | 2008/07/13 17:53:29 | Server daemon shut down STATUS | wrapper | 2008/07/13 17:53:29 | <-- Wrapper Stopped |
|
From: Leif M. <le...@ta...> - 2008-07-12 05:34:06
|
Jay,
Thanks for the log. Looking at it you can see that the Ruby thread is
indeed a "daemon" thread:
"Ruby Thread5832210" daemon prio=6 tid=0x03635400 nid=0x1328 in
Object.wait() [0x0345e000..0x0345fb98]
The only non-daemon thread at the time of the thread dump is:
"Wrapper-Startup-Runner" prio=6 tid=0x02df2000 nid=0x1410 waiting on
condition [0x0303f000..0x0303fd18]
The startup runner is a simple thread that the Wrapper starts to keep
the JVM running as the user application starts up. Once the
WrapperListener.start method returns the above startup runner will
complete. If there are not any other non-daemon threads left
running at that point, the JVM itself will start the shutdown process.
Cheers,
Leif
On Fri, Jul 11, 2008 at 10:05 PM, <Jay...@sc...> wrote:
>
> Hi Leif... still haven't turned ont he time stamps.. (I'll do that next)
>
> But it looks as if ruby threads are daemon threads...
>
> Jay
>
>
> ________________________________
>
> From: wra...@li...
> [mailto:wra...@li...] On Behalf Of "Leif
> Mortenson" <le...@ta...>
> Sent: Friday, June 27, 2008 3:03 PM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Using the wrapper integration method 3
>
>
> Jay,
> I am not sure how Ruby would be doing this but it would surprise beif
> they were daemons by default.
>
> Try doing a thread dump. The JVM looks like it is shutting down
> fairly quickly so try adding code like the following after you start
> your Ruby thread.
>
> try {
> Thread.sleep(500); // Let Ruby start.
> } catch (InterruptedException e) {
> //Something
> }
> org.tanukisoftware.wrapper.WrapperManager.requestThreadDump();
>
> A daemon thread will look something like this:
> "Reference Handler" daemon prio=10 tid=0x0003efb0 nid=0x308 in
> Object.wait() [0x02b8f000..0x02b8fd68]
>
> Non daemon like this:
> "AWT-EventQueue-0" prio=7 tid=0x02d65170 nid=0x940 in Object.wait()
> [0x0436f000..0x0436fd68]
>
> If all else fails, you may need to create a simple java thread which
> starts and loops until a flag is set from the WrapperListener.stop
> method or something.
>
> Cheers,
> Leif
>
> On Fri, Jun 27, 2008 at 9:29 PM, < Jay...@sc...> wrote:
>> Sorry about the no timestamps... How do I turn those on?
>>
>> What am I doing...
>>
>> In my start method I am spinning up a Jruby VM and in that VM I am
> spawning
>> a thread. It is my understanding that in Jruby .. Ruby threads are
> Java
>> threads... But they may not be non daemon threads I will look into
> that.
>>
>> Here are the pertinent functions:
>>
>> public Integer start( String[] args)
>> {
>> if (_service == null)
>> {
>> LauncherOptions opts = new LauncherOptions();
>> CmdLineParser parser = new CmdLineParser(opts);
>> try{
>> parser.parseArgument(args);
>> } catch( CmdLineException e ) {
>> System.err.println(e.getMessage());
>> System.err.println(" Example: java
>> ServiceLauncher"+parser.printExample(ALL));
>> parser.printUsage(System.err);
>> System.err.println();
>> return -1;
>> }
>> initialize(opts.serviceClassName, opts.serviceFileName,
>> opts.serviceInstanceName);
>>
>> }
>>
>> _service.start();
>> return null;
>> }
>>
>> public void initialize(String serviceClassName, String serviceFile,
> String
>> serviceName)
>> {
>> try {
>> String filename = serviceFile.split("\\.")[0];
>> // Create runtime instance of the Ruby VM
>> _rubyRuntime = Ruby.newInstance();
>> _rubyRuntime.evalScriptlet(String.format("require '%s'",filename));
>> Object rfj =
>> _rubyRuntime.evalScriptlet(String.format("%s.new",serviceClassName,
>> serviceName));
>> rfj = org.jruby.javasupport.JavaEmbedUtils.rubyToJava(_rubyRuntime,
>> (org.jruby.runtime.builtin.IRubyObject) rfj,
>> AffinityService.class); //((AffinityService)rfj).start();
>>
>> _service = (AffinityService)rfj;
>>
>> } catch (Throwable e) {
>> System.err.println("Exception creating the service: ");
>> e.printStackTrace(System.err);
>> }
>> }
>>
>> Here is the Ruby code that gets executed:
>>
>> class RubyService < tv.seachange.affininty.util.AffinityService
>> attr_reader :name
>> def initialize
>> #configure the service for the common stuff
>> @name = "RubyService"
>> end
>>
>> def start
>> @thread = Thread.new do
>> @started = true
>> spin_up
>> end
>> end
>>
>> def stop
>> @started = false
>> spin_down
>> end
>> end
>>
>>
>>
>> ________________________________
>>
>> From: wra...@li...
>> [mailto:wra...@li...] On Behalf Of "Leif
>> Mortenson" < le...@ta...>
>> Sent: Thursday, June 26, 2008 10:48 PM
>> To: Wrapper User List
>> Subject: Re: [Wrapper-user] Using the wrapper integration method 3
>>
>>
>> Jay,
>> see this part of the log:
>>
>>> jvm 1 | WrapperManager Debug: calling WrapperListener.start()
>>> jvm 1 | WrapperManager Debug: Waiting for WrapperListener.start
> runner
>>> thread to complete.
>>> jvm 1 | WrapperManager Debug: WrapperListener.start runner thread
> started.
>>> jvm 1 | Starting up!
>>> jvm 1 | WrapperManager Debug: WrapperListener.start runner thread
> stopped.
>>> jvm 1 | hi
>>> jvm 1 | WrapperManager Debug: returned from WrapperListener.start()
>>> jvm 1 | WrapperManager Debug: Send a packet STARTED :
>>> wrapperp | read a packet STARTED :
>>> wrapper | JVM signalled that it was started.
>>> jvm 1 | WrapperManager Debug: Startup runner thread stopped.
>>> jvm 1 | WrapperManager Debug: ShutdownHook started
>>
>> The Wrapper is calling WrapperListener.start in your application.
>> That returns and the WrapperManager reports that the application has
>> started. The WrapperManager starts up something called the start
>> runner which runs while the application is being started to keep the
>> JVM from shutting itself down due to a lack of non-daemon threads.
>> The problem is that as soon as that thread completes, there are no
>> longer any non-daemon threads running so the JVM is initiating a
>> shutdown. This is all correct behavior for the Wrapper.
>>
>> What exactly are you doing inside of your WrapperListener.start
>> method? Are you starting any non-daemon threads which make up the
>> application that should be running?
>>
>> If we exchange any more log files, please include time stamps. They
>> are useful in understanding the timing of when things happen.
>>
>> Cheers,
>> Leif
>>
>> On Fri, Jun 27, 2008 at 7:13 AM, < Jay...@sc...> wrote:
>>> Leif,
>>>
>>> Here is the log. ...
>>>
>>> It could definitely be a thread thing.
>>>
>>> I am spinning up a thread in Jruby. (my java code launches a ruby vm
> and
>>> in
>>> ruby I am creating a thread)
>>>
>>> Jay
>>>
>> < log snip>
>>>
>>>
>>>
>>> ====
>>>
>>> Could you please set the wrapper.debug=true property and then reply
> with
>>> the resulting wrapper.log attached. I only need to see a single
> Wrapper
>>> invocation so delete the old wrapper.log file first. The log should
>>> allow me to say what your exact problem is.
>>>
>>> Cheers,
>>> Leif
>>>
>>> Jay...@sc... wrote:
>>>> Hi,
>>>>
>>>> I'm playing around with the service wrapper and trying to get an
> example
>>>> running using integration method 3. I'm running on the Mac OS X.
>>>>
>>>> Everything appears to work. The service starts up when I use the
> start
>>>> script (sh.script.ln) except that after a few seconds the
> infrastructure
>>>> appears to call a stop on my service.
>>>>
>>>> Does anyone know the reasons why the stop would be called? I've
>>>> returned null from my start method. I spun up my logic in a thread
>>>> although I did the thread start in a wierd way. (what if the thread
>>>> exited (that's not necessarily happening but I'm trying to learn)?).
>>>>
>>>> My service is a very simple loop where I'm just printing a message
> to
>>>> std out every second.
>>>>
>>>
>>
>>
> ------------------------------------------------------------------------
> -
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>>
> ------------------------------------------------------------------------
> -
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
> ------------------------------------------------------------------------
> -
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
|
|
From: Davis, B. [DAS] <Bil...@io...> - 2008-07-10 15:16:48
|
> Bill, > When you shut the Wrapper down at 16:30, there was a single "Wrapper > Stopped" line logged. If the Wrapper is not getting anything from > the JVM, that is all that is expected. This tells me that the > Wrapper's ability to write something to the log file is working > correctly. It does not, however, confirm that the Wrapper is > receiving and processing any JVM output correctly. Thanks, that's kind of what I thought. > Rather that you going through and adding System.out calls manually, > the easiest thing to do would be to set the wrapper.debug=true > property. This will cause log entries originating from the Wrapper > and Java processes to be logged every 5 seconds. Doing this will tell > us if all logging is stopping, only JVM console output, or possibly > only the log4j output. I was thinking about doing that, actually, and fiddling with some of the threshold and flushing settings in case maybe the sudden flood of messages was overloading memory or something somewhere. Good to know I was on the right track. > I understand that it is difficult to test on customer systems. The > debug property should not affect how the application runs and is a > very low risk change. The only effect will be to have a large > wrapper.log file. We have the disk space. I'll probably want to change the number of files kept to a larger amount too (presently 10). I might also move the log file to the D: drive which has 106gb free space (don't ask me why the C: drive is 30GB with 8GB free and the D: is >100 GB and unused. Seems silly to me, and potentially dangerous.) > Question: In the log examples you sent me, the last entry on > 2008/07/08 was at 01:03. The Wrapper was then stopped at 16:30. > What happened to the 2008/07/08 01:30 Wrapper shutdown that should > happen every night. Is it possible that something there could be > causing the problem? I am not sure what normally happens during that > shutdown period. That would be the one at 2007/07/*09* 01:19:25.096. Note the 09, not 08. That was further down in the log file excerpts I sent, actually: 2008/07/09 01:19:23.987 | jvm 1 | INFO | ****************************************************************************** 2008/07/09 01:19:23.987 | jvm 1 | INFO | * Mule shut down normally on: Wednesday, July 9, 2008 1:19:23 AM CDT * 2008/07/09 01:19:23.987 | jvm 1 | INFO | * Server was up for: 0 days, 8 hours, 48 mins, 10.347 sec * 2008/07/09 01:19:23.987 | jvm 1 | INFO | ****************************************************************************** 2008/07/09 01:19:24.096 | wrapper | STATUS | <-- Wrapper Stopped 2008/07/09 01:20:26.673 | wrapper | STATUS | --> Wrapper Started as Service 2008/07/09 01:20:26.891 | wrapper | STATUS | Launching a JVM... 2008/07/09 01:20:27.438 | jvm 1 | INFO | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org 2008/07/09 01:20:27.438 | jvm 1 | INFO | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. 2008/07/09 01:20:27.438 | jvm 1 | INFO | 2008/07/09 01:20:27.547 | jvm 1 | INFO | log4j:INFO Using URL [file:/C:/Programs/I3Gateway/classes/log4j.xml] for automatic log4j configuration of repository named [default]. The 1AM shutdown-and-restart of the Wrapper to change the configuration file for the Mule server happens only approximately at 1AM to 1:30AM. Time can vary based on evening processing tasks taking different amounts of time (payroll, several other things than happen only monthly/weekly/quarterly/annually/etc) To make sure what we're doing is clear: The Wrapper is ALWAYS running the Mule ESB server process except for a 1 minute interval twice at day at 16:30 (4:30PM) and somewhere between 01:00 and 02:00 AM (or more accurately: whenever evening processing has completed) to swap between Mule configuration files for our normal daytime processing and evening processing tasks. We do this because we don't want Mule accepting daytime data files during evening processing of the daytime data files we received...and Mule apparently ain't smart enough to not trigger file transfer and processing jobs in the evening. Dumb ol' Mule! Also, we likewise have some data transfers TO and FROM other systems to which we expect responses in the evenings that we don't want running during the day. Thus the stop-and-start of the Wrapper around Mule, with the Mule config file swaps in between. Thanks again for the guidance. We'll see what we can come up with. I may also try to figure out how to have the console stuff written to log4j from our code go to our own separate file, if possible. I prefer it in the Wrapper log, truthfully, to keep all the service's activity logging in ONE place, but hey, whatever works. And I've got a lot of reading up on Wrapper, Mule and Log4j yet to do. Among other technologies and tools! - Bill Davis |
|
From: Leif M. <le...@ta...> - 2008-07-10 00:21:19
|
Bill, When you shut the Wrapper down at 16:30, there was a single "Wrapper Stopped" line logged. If the Wrapper is not getting anything from the JVM, that is all that is expected. This tells me that the Wrapper's ability to write something to the log file is working correctly. It does not, however, confirm that the Wrapper is receiving and processing any JVM output correctly. Rather that you going through and adding System.out calls manually, the easiest thing to do would be to set the wrapper.debug=true property. This will cause log entries originating from the Wrapper and Java processes to be logged every 5 seconds. Doing this will tell us if all logging is stopping, only JVM console output, or possibly only the log4j output. I understand that it is difficult to test on customer systems. The debug property should not affect how the application runs and is a very low risk change. The only effect will be to have a large wrapper.log file. Question: In the log examples you sent me, the last entry on 2008/07/08 was at 01:03. The Wrapper was then stopped at 16:30. What happened to the 2008/07/08 01:30 Wrapper shutdown that should happen every night. Is it possible that something there could be causing the problem? I am not sure what normally happens during that shutdown period. Cheers, Leif On Thu, Jul 10, 2008 at 4:43 AM, Davis, Bill [DAS] <Bil...@io...> wrote: > Bill, >> When the application is in a state where it has stopped logging, are >> you running a service or in console mode? > > We are running it as a service, on a Windows 2003 Server box, an HP Dual-core AMD Opteron, 2.6GHz, with 2GB RAM. Win 2K3 Server R2 Standard Edition with Service Pack 2. > > >> If possible can you reproduce this running in console mode? I am >> assuming for now you are running on windows. > > I'll have to bump that up the chain of command and see if it will be allowed. I do not have physical access to the server. > > >> 1) When in the stopped state, can you request a thread dump by pressing >> CTRL-BREAK? If you see the dump, then the Wrapper process is >> correctly receiving and logging output from the Java process. > > I'll see if that's possible for me to do (since I don't have direct access to the machine). > > > >> 2) As an alternative to the thread dump, simply start the shutdown >> process. If you see more log entries then once again things are >> working on the Wrapper side. > > I'll keep an eye on that and see if I can look back through the logs and find one of these occurrences to see if when we run the batch script that shuts down the service the messages from Wrapper get logged or not. > > Wrapper is running a Mule ESB Server process that we shutdown and switch between two configuration files for daytime and evening processing tasks at about 1:30 am and 4:30pm. > > In looking at recent log files, the problem seems to happen EVERY day after we do the 1:30 am switch; it processes a boatload of transactions and at some point writing to the log just stops happening. Then about 4:30 when the service is stopped, the config files for the Mule ESB Server are switched to evening processing and the service is started, we do get some Wrapper messages....but not the Mule shutdown messages. Here's an example: > > Here's the log entries centered around the 16:30 shutdown and restart of the service: > > 2008/07/08 01:03:44.824 | jvm 1 | INFO | INFO|EmailNotification.send(82)| Adding rk...@dh... to email > 2008/07/08 01:03:44.824 | jvm 1 | INFO | INFO|EmailNotification.send(82)| Adding BC...@dh... to email > 2008/07/08 01:03:44.824 | jvm 1 | INFO | INFO|EmailNotification.send(82)| Adding BC...@dh... to email > 2008/07/08 01:03:46.684 | jvm 1 | INFO | INFO|AMSVendorExporter.exportSubmission(148)| Submission with id of 637 has finished exporting > 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(116)| The following email was sent on 07/08/2008 01:03:49 > 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(116)| The following email was sent on 07/08/2008 01:03:49 > 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(118)| Notification Type: gov.iowa.das.ite.i3.conversion.notification.PartialLoadNotification > 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(118)| Notification Type: gov.iowa.das.ite.i3.conversion.notification.PartialLoadNotification > 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(119)| Recipients: jw...@dh... mp...@dh... Tai...@io... les...@io... rk...@dh... BC...@dh... > 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(119)| Recipients: jw...@dh... mp...@dh... Tai...@io... les...@io... rk...@dh... BC...@dh... > > 2008/07/08 16:30:03.454 | wrapper | STATUS | <-- Wrapper Stopped > 2008/07/08 16:31:06.014 | wrapper | STATUS | --> Wrapper Started as Service > > 2008/07/08 16:31:06.233 | wrapper | STATUS | Launching a JVM... > 2008/07/08 16:31:06.780 | jvm 1 | INFO | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org > 2008/07/08 16:31:06.780 | jvm 1 | INFO | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. > 2008/07/08 16:31:06.780 | jvm 1 | INFO | > 2008/07/08 16:31:06.780 | jvm 1 | INFO | log4j:INFO Using URL [file:/C:/Programs/I3Gateway/classes/log4j.xml] for automatic log4j configuration of repository named [default]. > 2008/07/08 16:31:06.999 | jvm 1 | INFO | AbandonedObjectPool is used (org.apache.commons.dbcp.AbandonedObjectPool@7bb290) > 2008/07/08 16:31:06.999 | jvm 1 | INFO | LogAbandoned: true > 2008/07/08 16:31:06.999 | jvm 1 | INFO | RemoveAbandoned: true > 2008/07/08 16:31:06.999 | jvm 1 | INFO | RemoveAbandonedTimeout: 300 > 2008/07/08 16:31:08.421 | jvm 1 | INFO | INFO|MuleManager.getInstance(280)| Creating new MuleManager instance > > > Here's the 1:00AM shutdown and restart (exact time floats based on evening processing tasks times): > > 2008/07/09 01:19:23.877 | jvm 1 | INFO | INFO|MuleManager.disposeAgents(1348)| disposing agents... > 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|MuleManager.disposeAgents(1355)| Agents Successfully Disposed > 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|AbstractApplicationContext.close(500)| Closing application context [org.springframework.context.support.FileSystemXmlApplicationContext;hashCode=2221396] > 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|AbstractBeanFactory.destroySingletons(555)| Destroying singletons in factory .... > 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|LocalSessionFactoryBean.destroy(1028)| Closing Hibernate SessionFactory > 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|SessionFactoryImpl.close(766)| closing > 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|AbstractResourceManager.stop(106)| Stopping ResourceManager > 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|AbstractResourceManager.stop(116)| Stopped ResourceManager > 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|MuleManager.dispose(441)| > > 2008/07/09 01:19:23.987 | jvm 1 | INFO | ****************************************************************************** > 2008/07/09 01:19:23.987 | jvm 1 | INFO | * Mule shut down normally on: Wednesday, July 9, 2008 1:19:23 AM CDT * > 2008/07/09 01:19:23.987 | jvm 1 | INFO | * Server was up for: 0 days, 8 hours, 48 mins, 10.347 sec * > 2008/07/09 01:19:23.987 | jvm 1 | INFO | ****************************************************************************** > 2008/07/09 01:19:24.096 | wrapper | STATUS | <-- Wrapper Stopped > 2008/07/09 01:20:26.673 | wrapper | STATUS | --> Wrapper Started as Service > > 2008/07/09 01:20:26.891 | wrapper | STATUS | Launching a JVM... > 2008/07/09 01:20:27.438 | jvm 1 | INFO | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org > 2008/07/09 01:20:27.438 | jvm 1 | INFO | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. > 2008/07/09 01:20:27.438 | jvm 1 | INFO | > 2008/07/09 01:20:27.547 | jvm 1 | INFO | log4j:INFO Using URL [file:/C:/Programs/I3Gateway/classes/log4j.xml] for automatic log4j configuration of repository named [default]. > 2008/07/09 01:20:27.657 | jvm 1 | INFO | AbandonedObjectPool is used (org.apache.commons.dbcp.AbandonedObjectPool@7bb290) > 2008/07/09 01:20:27.657 | jvm 1 | INFO | LogAbandoned: true > 2008/07/09 01:20:27.657 | jvm 1 | INFO | RemoveAbandoned: true > 2008/07/09 01:20:27.657 | jvm 1 | INFO | RemoveAbandonedTimeout: 300 > 2008/07/09 01:20:29.079 | jvm 1 | INFO | INFO|MuleManager.getInstance(280)| Creating new MuleManager instance > > > Notice the Mule shutdown message on this one that doesn't show up on the 16:30 shutdown because logging has stopped. I've put some blank lines around these log entries to highlight them. > > I can't tell if it's Wrapper that needs configuration changing, or a bug in log4j or Mule. > > To stop the service, we have a Windows Scheduled task that runs a batch script that does: > > Net Stop "I3InternalESBServer" > > Then switches out the settings file for morning/evening processing, waits one minuen, and then does a: > > Net Start "I3InternalESBServer" > > > > >> 3) Make sure you are seeing the log entries both in the Console and the >> Log file. If they are only showing up in the Console then that would >> point to a problem writing to the log file. > > > Again, I'll see if that is going to be allowed, but thanks for the tip. > > > > >> 4) At the point that the logging stops, how large is the wrapper.log >> file? I assume you have plenty of disk space. > > We have the log file size set to 1 MB before it starts a new one. We have over 8 GB of free disk space. > > > > >> 5) What are your logging settings from the wrapper.conf file. > > Here is our entire wrapper.conf file (it's small) > > wrapper.java.command=../jre/bin/JavaESBServer.exe > wrapper.java.maxmemory=512 > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > > wrapper.app.parameter.1=gov.iowa.das.ite.i3.esb.server.ESBServer > > wrapper.java.classpath.1=../lib/wrapper.jar > wrapper.java.classpath.2=../classes > wrapper.java.classpath.3=../lib/javamail-1.4.jar > wrapper.java.classpath.4=../lib/*.jar > > wrapper.ntservice.name=I3InternalESBServer > wrapper.ntservice.displayname=I3InternalESBServer > wrapper.ntservice.description=I3InternalESBServer > > wrapper.pidfile=../logs/wrapper.pid > wrapper.java.pidfile=../logs/java.pid > > wrapper.logfile=../logs/I-3InternalESBServer-ROLLNUM.log > wrapper.logfile.maxsize=1m > wrapper.logfile.rollmode=SIZE > wrapper.logfile.maxfiles=10 > > wrapper.logfile.format=ZPLM > wrapper.logfile.loglevel=INFO > > > > > Here is also our log4j.xml file: > > <?xml version="1.0" encoding="UTF-8" ?> > <!DOCTYPE log4j:configuration> > > <log4j:configuration xmlns:log4j='http://logging.apache.org/' > debug="false"> > > <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender"> > <layout class="org.apache.log4j.PatternLayout"> > <param name="ConversionPattern" > value="%p|%C{1}.%M(%L)| %m%n" /> > </layout> > </appender> > > <appender name="DB" class="org.apache.log4j.db.DBAppender"> > <connectionSource > class="org.apache.log4j.db.DataSourceConnectionSource"> > <dataSource > class="org.apache.commons.dbcp.BasicDataSource"> > <param name="driverClassName" value="com.mysql.jdbc.Driver" /> > <param name="url" value="jdbc:mysql://localhost:3306/I3Gateway" /> > <param name="username" value="conv_system" /> > <param name="password" value="password" /> > <param name="maxActive" value="10" /> > <param name="maxIdle" value="1" /> > <param name="defaultAutoCommit" value="true" /> > <param name="removeAbandoned" value="true" /> > <param name="removeAbandonedTimeout" value="300" /> > <param name="logAbandoned" value="true" /> > <param name="validationQuery" value="select 1" /> > </dataSource> > </connectionSource> > </appender> > > > <logger name="gov.iowa.das.ite.i3.conversion.server" additivity="true"> > <level value="INFO" /> > <appender-ref ref="CONSOLE" /> > </logger> > > <logger name="gov.iowa.das.ite.i3.conversion.notification" additivity="true"> > <level value="INFO" /> > <appender-ref ref="CONSOLE" /> > </logger> > > <root> > <level value="INFO" /> > <appender-ref ref="CONSOLE" /> > </root> > > </log4j:configuration> > > > >> Once we have confirmed that some output from the JVM is making it to >> the Wrapper to be logged then the Wrapper can be ruled out and we can >> look into what on the Java side might be causing the problem. > > I'm guessing since Wrapper startup and shutdown seem to be getting logged it's not Wrapper, but since Wrapper is apparently intercepting the logging activity, well, it's hard to tell where the problem is after that. > > > > >> All java side logging tools use System.out to print log information to >> the Java console. So you can easily test that by adding some >> System.outs to your code. If those show up in the Wrapper.log file, >> but the log4j calls do not then it is a java side logging problem of >> some sort. > > I'll see if we can put some System.outs in the code next to the log.info or log.error calls which from what I can see our software uses exclusively. It won't be something I can do quickly; I'll have to get approval to deploy it even on our test machine. It may take a few days. > >> I may have more ideas after hearing back from you. > > I greatly appreciate the assistance, Leif! > > - Bill Davis > |
|
From: Davis, B. [DAS] <Bil...@io...> - 2008-07-09 19:41:43
|
Bill, > When the application is in a state where it has stopped logging, are > you running a service or in console mode? We are running it as a service, on a Windows 2003 Server box, an HP Dual-core AMD Opteron, 2.6GHz, with 2GB RAM. Win 2K3 Server R2 Standard Edition with Service Pack 2. > If possible can you reproduce this running in console mode? I am > assuming for now you are running on windows. I'll have to bump that up the chain of command and see if it will be allowed. I do not have physical access to the server. > 1) When in the stopped state, can you request a thread dump by pressing > CTRL-BREAK? If you see the dump, then the Wrapper process is > correctly receiving and logging output from the Java process. I'll see if that's possible for me to do (since I don't have direct access to the machine). > 2) As an alternative to the thread dump, simply start the shutdown > process. If you see more log entries then once again things are > working on the Wrapper side. I'll keep an eye on that and see if I can look back through the logs and find one of these occurrences to see if when we run the batch script that shuts down the service the messages from Wrapper get logged or not. Wrapper is running a Mule ESB Server process that we shutdown and switch between two configuration files for daytime and evening processing tasks at about 1:30 am and 4:30pm. In looking at recent log files, the problem seems to happen EVERY day after we do the 1:30 am switch; it processes a boatload of transactions and at some point writing to the log just stops happening. Then about 4:30 when the service is stopped, the config files for the Mule ESB Server are switched to evening processing and the service is started, we do get some Wrapper messages....but not the Mule shutdown messages. Here's an example: Here's the log entries centered around the 16:30 shutdown and restart of the service: 2008/07/08 01:03:44.824 | jvm 1 | INFO | INFO|EmailNotification.send(82)| Adding rk...@dh... to email 2008/07/08 01:03:44.824 | jvm 1 | INFO | INFO|EmailNotification.send(82)| Adding BC...@dh... to email 2008/07/08 01:03:44.824 | jvm 1 | INFO | INFO|EmailNotification.send(82)| Adding BC...@dh... to email 2008/07/08 01:03:46.684 | jvm 1 | INFO | INFO|AMSVendorExporter.exportSubmission(148)| Submission with id of 637 has finished exporting 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(116)| The following email was sent on 07/08/2008 01:03:49 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(116)| The following email was sent on 07/08/2008 01:03:49 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(118)| Notification Type: gov.iowa.das.ite.i3.conversion.notification.PartialLoadNotification 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(118)| Notification Type: gov.iowa.das.ite.i3.conversion.notification.PartialLoadNotification 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(119)| Recipients: jw...@dh... mp...@dh... Tai...@io... les...@io... rk...@dh... BC...@dh... 2008/07/08 01:03:49.965 | jvm 1 | INFO | INFO|EmailNotification.send(119)| Recipients: jw...@dh... mp...@dh... Tai...@io... les...@io... rk...@dh... BC...@dh... 2008/07/08 16:30:03.454 | wrapper | STATUS | <-- Wrapper Stopped 2008/07/08 16:31:06.014 | wrapper | STATUS | --> Wrapper Started as Service 2008/07/08 16:31:06.233 | wrapper | STATUS | Launching a JVM... 2008/07/08 16:31:06.780 | jvm 1 | INFO | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org 2008/07/08 16:31:06.780 | jvm 1 | INFO | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. 2008/07/08 16:31:06.780 | jvm 1 | INFO | 2008/07/08 16:31:06.780 | jvm 1 | INFO | log4j:INFO Using URL [file:/C:/Programs/I3Gateway/classes/log4j.xml] for automatic log4j configuration of repository named [default]. 2008/07/08 16:31:06.999 | jvm 1 | INFO | AbandonedObjectPool is used (org.apache.commons.dbcp.AbandonedObjectPool@7bb290) 2008/07/08 16:31:06.999 | jvm 1 | INFO | LogAbandoned: true 2008/07/08 16:31:06.999 | jvm 1 | INFO | RemoveAbandoned: true 2008/07/08 16:31:06.999 | jvm 1 | INFO | RemoveAbandonedTimeout: 300 2008/07/08 16:31:08.421 | jvm 1 | INFO | INFO|MuleManager.getInstance(280)| Creating new MuleManager instance Here's the 1:00AM shutdown and restart (exact time floats based on evening processing tasks times): 2008/07/09 01:19:23.877 | jvm 1 | INFO | INFO|MuleManager.disposeAgents(1348)| disposing agents... 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|MuleManager.disposeAgents(1355)| Agents Successfully Disposed 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|AbstractApplicationContext.close(500)| Closing application context [org.springframework.context.support.FileSystemXmlApplicationContext;hashCode=2221396] 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|AbstractBeanFactory.destroySingletons(555)| Destroying singletons in factory .... 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|LocalSessionFactoryBean.destroy(1028)| Closing Hibernate SessionFactory 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|SessionFactoryImpl.close(766)| closing 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|AbstractResourceManager.stop(106)| Stopping ResourceManager 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|AbstractResourceManager.stop(116)| Stopped ResourceManager 2008/07/09 01:19:23.987 | jvm 1 | INFO | INFO|MuleManager.dispose(441)| 2008/07/09 01:19:23.987 | jvm 1 | INFO | ****************************************************************************** 2008/07/09 01:19:23.987 | jvm 1 | INFO | * Mule shut down normally on: Wednesday, July 9, 2008 1:19:23 AM CDT * 2008/07/09 01:19:23.987 | jvm 1 | INFO | * Server was up for: 0 days, 8 hours, 48 mins, 10.347 sec * 2008/07/09 01:19:23.987 | jvm 1 | INFO | ****************************************************************************** 2008/07/09 01:19:24.096 | wrapper | STATUS | <-- Wrapper Stopped 2008/07/09 01:20:26.673 | wrapper | STATUS | --> Wrapper Started as Service 2008/07/09 01:20:26.891 | wrapper | STATUS | Launching a JVM... 2008/07/09 01:20:27.438 | jvm 1 | INFO | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org 2008/07/09 01:20:27.438 | jvm 1 | INFO | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. 2008/07/09 01:20:27.438 | jvm 1 | INFO | 2008/07/09 01:20:27.547 | jvm 1 | INFO | log4j:INFO Using URL [file:/C:/Programs/I3Gateway/classes/log4j.xml] for automatic log4j configuration of repository named [default]. 2008/07/09 01:20:27.657 | jvm 1 | INFO | AbandonedObjectPool is used (org.apache.commons.dbcp.AbandonedObjectPool@7bb290) 2008/07/09 01:20:27.657 | jvm 1 | INFO | LogAbandoned: true 2008/07/09 01:20:27.657 | jvm 1 | INFO | RemoveAbandoned: true 2008/07/09 01:20:27.657 | jvm 1 | INFO | RemoveAbandonedTimeout: 300 2008/07/09 01:20:29.079 | jvm 1 | INFO | INFO|MuleManager.getInstance(280)| Creating new MuleManager instance Notice the Mule shutdown message on this one that doesn't show up on the 16:30 shutdown because logging has stopped. I've put some blank lines around these log entries to highlight them. I can't tell if it's Wrapper that needs configuration changing, or a bug in log4j or Mule. To stop the service, we have a Windows Scheduled task that runs a batch script that does: Net Stop "I3InternalESBServer" Then switches out the settings file for morning/evening processing, waits one minuen, and then does a: Net Start "I3InternalESBServer" > 3) Make sure you are seeing the log entries both in the Console and the > Log file. If they are only showing up in the Console then that would > point to a problem writing to the log file. Again, I'll see if that is going to be allowed, but thanks for the tip. > 4) At the point that the logging stops, how large is the wrapper.log > file? I assume you have plenty of disk space. We have the log file size set to 1 MB before it starts a new one. We have over 8 GB of free disk space. > 5) What are your logging settings from the wrapper.conf file. Here is our entire wrapper.conf file (it's small) wrapper.java.command=../jre/bin/JavaESBServer.exe wrapper.java.maxmemory=512 wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp wrapper.app.parameter.1=gov.iowa.das.ite.i3.esb.server.ESBServer wrapper.java.classpath.1=../lib/wrapper.jar wrapper.java.classpath.2=../classes wrapper.java.classpath.3=../lib/javamail-1.4.jar wrapper.java.classpath.4=../lib/*.jar wrapper.ntservice.name=I3InternalESBServer wrapper.ntservice.displayname=I3InternalESBServer wrapper.ntservice.description=I3InternalESBServer wrapper.pidfile=../logs/wrapper.pid wrapper.java.pidfile=../logs/java.pid wrapper.logfile=../logs/I-3InternalESBServer-ROLLNUM.log wrapper.logfile.maxsize=1m wrapper.logfile.rollmode=SIZE wrapper.logfile.maxfiles=10 wrapper.logfile.format=ZPLM wrapper.logfile.loglevel=INFO Here is also our log4j.xml file: <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE log4j:configuration> <log4j:configuration xmlns:log4j='http://logging.apache.org/' debug="false"> <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender"> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%p|%C{1}.%M(%L)| %m%n" /> </layout> </appender> <appender name="DB" class="org.apache.log4j.db.DBAppender"> <connectionSource class="org.apache.log4j.db.DataSourceConnectionSource"> <dataSource class="org.apache.commons.dbcp.BasicDataSource"> <param name="driverClassName" value="com.mysql.jdbc.Driver" /> <param name="url" value="jdbc:mysql://localhost:3306/I3Gateway" /> <param name="username" value="conv_system" /> <param name="password" value="password" /> <param name="maxActive" value="10" /> <param name="maxIdle" value="1" /> <param name="defaultAutoCommit" value="true" /> <param name="removeAbandoned" value="true" /> <param name="removeAbandonedTimeout" value="300" /> <param name="logAbandoned" value="true" /> <param name="validationQuery" value="select 1" /> </dataSource> </connectionSource> </appender> <logger name="gov.iowa.das.ite.i3.conversion.server" additivity="true"> <level value="INFO" /> <appender-ref ref="CONSOLE" /> </logger> <logger name="gov.iowa.das.ite.i3.conversion.notification" additivity="true"> <level value="INFO" /> <appender-ref ref="CONSOLE" /> </logger> <root> <level value="INFO" /> <appender-ref ref="CONSOLE" /> </root> </log4j:configuration> > Once we have confirmed that some output from the JVM is making it to > the Wrapper to be logged then the Wrapper can be ruled out and we can > look into what on the Java side might be causing the problem. I'm guessing since Wrapper startup and shutdown seem to be getting logged it's not Wrapper, but since Wrapper is apparently intercepting the logging activity, well, it's hard to tell where the problem is after that. > All java side logging tools use System.out to print log information to > the Java console. So you can easily test that by adding some > System.outs to your code. If those show up in the Wrapper.log file, > but the log4j calls do not then it is a java side logging problem of > some sort. I'll see if we can put some System.outs in the code next to the log.info or log.error calls which from what I can see our software uses exclusively. It won't be something I can do quickly; I'll have to get approval to deploy it even on our test machine. It may take a few days. > I may have more ideas after hearing back from you. I greatly appreciate the assistance, Leif! - Bill Davis |
|
From: <le...@ta...> - 2008-07-09 04:20:14
|
Bill, When the application is in a state where it has stopped logging, are you running a service or in console mode? If possible can you reproduce this running in console mode? I am assuming for now you are running on windows. 1) When in the stopped state, can you request a thread dump by pressing CTRL-BREAK? If you see the dump, then the Wrapper process is correctly receiving and logging output from the Java process. 2) As an alternative to the thread dump, simply start the shutdown process. If you see more log entries then once again things are working on the Wrapper side. 3) Make sure you are seeing the log entries both in the Console and the Log file. If they are only showing up in the Console then that would point to a problem writing to the log file. 4) At the point that the logging stops, how large is the wrapper.log file? I assume you have plenty of disk space. 5) What are your logging settings from the wrapper.conf file. Once we have confirmed that some output from the JVM is making it to the Wrapper to be logged then the Wrapper can be ruled out and we can look into what on the Java side might be causing the problem. All java side logging tools use System.out to print log information to the Java console. So you can easily test that by adding some System.outs to your code. If those show up in the Wrapper.log file, but the log4j calls do not then it is a java side logging problem of some sort. I may have more ideas after hearing back from you. Cheers, Leif On Wed, Jul 9, 2008 at 2:49 AM, Davis, Bill [DAS] <Bil...@io...> wrote: > We are having problems with logging just simply "stopping" occasionally. > We use Wrapper (v. 3.2.3) to run a Mule ESB server that processing incoming > XML files from various state agencies and prepares them for our main system > here. The system will be running along fine but it just stops writing to > the log. The program is still running and processing files…but nothing > shows up in the log file. > > > > Anybody ever hear of a problem like this? I've poked around the web site > and searched the mailing list and stuff (still am searching, actually) and > haven't found anything yet that quite sounds like this problem, though > apparently there have been some "issues" with logging that have been fixed > in more recent version of Wrapper. > > > > We're also apparently using the following logging-related jar files in this > project: > > > > commons-logging-1.0.4.jar > > > > log4j-1.2.9jar > > > > log4j-all-1.3alpha-8.jar (which is most odd, as development of version 1.3 > was abandoned in favor of 2.0) > > > > We're probably going to start upgrading logging-related components one at a > time, starting with Wrapper (easiest) and then Mule and the logging-related > jar files, but of course since we can't reproduce the problem on demand, > fixing this will be a pain unless someone has run across something like > this before. > > > > We may also just change the log4j properties to write elsewhere than the > Wrapper log, I ran across a suggestion about that in the Wrapper mailing > list archives today. > > > > Note: I did not develop this app - I just "inherited" it after the previous > programmer left, so I'm not terribly familiar with Wrapper, Mule, or even > Java. I've had some courses in Java, and programmed in C and many other > languages for many years (decades, really). But an expert in Java, Mule, > Wrapper, etc I am not (yet.) I'm just getting started and am having > something of a baptism by fire, so please be patient with the noob! ;-) > > > > Thanks! > > > > Bill Davis > |
|
From: Davis, B. [DAS] <Bil...@io...> - 2008-07-08 17:47:59
|
We are having problems with logging just simply "stopping" occasionally. We use Wrapper (v. 3.2.3) to run a Mule ESB server that processing incoming XML files from various state agencies and prepares them for our main system here. The system will be running along fine but it just stops writing to the log. The program is still running and processing files...but nothing shows up in the log file. Anybody ever hear of a problem like this? I've poked around the web site and searched the mailing list and stuff (still am searching, actually) and haven't found anything yet that quite sounds like this problem, though apparently there have been some "issues" with logging that have been fixed in more recent version of Wrapper. We're also apparently using the following logging-related jar files in this project: commons-logging-1.0.4.jar log4j-1.2.9jar log4j-all-1.3alpha-8.jar (which is most odd, as development of version 1.3 was abandoned in favor of 2.0) We're probably going to start upgrading logging-related components one at a time, starting with Wrapper (easiest) and then Mule and the logging-related jar files, but of course since we can't reproduce the problem on demand, fixing this will be a pain unless someone has run across something like this before. We may also just change the log4j properties to write elsewhere than the Wrapper log, I ran across a suggestion about that in the Wrapper mailing list archives today. Note: I did not develop this app - I just "inherited" it after the previous programmer left, so I'm not terribly familiar with Wrapper, Mule, or even Java. I've had some courses in Java, and programmed in C and many other languages for many years (decades, really). But an expert in Java, Mule, Wrapper, etc I am not (yet.) I'm just getting started and am having something of a baptism by fire, so please be patient with the noob! ;-) Thanks! Bill Davis |
|
From: Leif M. <le...@ta...> - 2008-07-08 12:33:48
|
Scott, This is the first report of such a problem and is obviously a bug. It may be due to a configuration problem that can be worked around however. I will take it off list to request some long log files and report back here. Cheers, Leif On Tue, Jul 8, 2008 at 9:25 PM, Scott LaFave <sl...@tr...> wrote: > Hi All – > > > > I am getting these errors when I try and start the wrapper on x64 Vista: > > > > STATUS | wrapper | main | 2008/07/08 07:51:08.075 | --> Wrapper Started > as Console > > STATUS | wrapper | main | 2008/07/08 07:51:08.077 | Java Service Wrapper > Standard Edition 3.3.0 > > STATUS | wrapper | main | 2008/07/08 07:51:08.078 | Copyright (C) > 1999-2008 Tanuki Software, Inc. All Rights Reserved. > > STATUS | wrapper | main | 2008/07/08 07:51:08.079 | > http://wrapper.tanukisoftware.org > > FATAL | wrapper | main | 2008/07/08 07:51:09.414 | encountered a fatal > error in Wrapper > > FATAL | wrapper | main | 2008/07/08 07:51:09.414 | exceptionCode = > EXCEPTION_ACCESS_VIOLATION > > FATAL | wrapper | main | 2008/07/08 07:51:09.414 | exceptionFlag = > EXCEPTION_NONCONTINUABLE_EXCEPTION > > FATAL | wrapper | main | 2008/07/08 07:51:09.415 | exceptionAddress = > 000000000041FB21 > > FATAL | wrapper | main | 2008/07/08 07:51:09.415 | Read access > exception from 000000000000002C > > FATAL | wrapper | main | 2008/07/08 07:51:09.416 | <-- Wrapper Stopping > due to error > > > > The community wrapper was working perfectly on my previous x86 Vista load. > Yesterday I migrated to x64 Vista and updated my service with the x64 > licensed version of the wrapper. Now I get this error when trying to start > it. > > > > Can anyone assist? > > > > Thanks! > > > > Scott > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Scott L. <sl...@tr...> - 2008-07-08 12:25:24
|
Hi All - I am getting these errors when I try and start the wrapper on x64 Vista: STATUS | wrapper | main | 2008/07/08 07:51:08.075 | --> Wrapper Started as Console STATUS | wrapper | main | 2008/07/08 07:51:08.077 | Java Service Wrapper Standard Edition 3.3.0 STATUS | wrapper | main | 2008/07/08 07:51:08.078 | Copyright (C) 1999-2008 Tanuki Software, Inc. All Rights Reserved. STATUS | wrapper | main | 2008/07/08 07:51:08.079 | http://wrapper.tanukisoftware.org FATAL | wrapper | main | 2008/07/08 07:51:09.414 | encountered a fatal error in Wrapper FATAL | wrapper | main | 2008/07/08 07:51:09.414 | exceptionCode = EXCEPTION_ACCESS_VIOLATION FATAL | wrapper | main | 2008/07/08 07:51:09.414 | exceptionFlag = EXCEPTION_NONCONTINUABLE_EXCEPTION FATAL | wrapper | main | 2008/07/08 07:51:09.415 | exceptionAddress = 000000000041FB21 FATAL | wrapper | main | 2008/07/08 07:51:09.415 | Read access exception from 000000000000002C FATAL | wrapper | main | 2008/07/08 07:51:09.416 | <-- Wrapper Stopping due to error The community wrapper was working perfectly on my previous x86 Vista load. Yesterday I migrated to x64 Vista and updated my service with the x64 licensed version of the wrapper. Now I get this error when trying to start it. Can anyone assist? Thanks! Scott |
|
From: Leif M. <le...@ta...> - 2008-07-07 23:47:41
|
Sushil, Is there any reason why you need to have the Wrapper's debug log output enabled? That is normally only useful when debugging the Wrapper itself. wrapper.logfile.loglevel=DEBUG If you change it to INFO then all of those messages from the Wrapper will go away. It is also possible to reduce the number of ping related log messages (Not the actual pings) using the following property. As the page says though, this can make it difficult to track down certain types of timout problems. http://wrapper.tanukisoftware.org/doc/english/prop-ping-interval-logged.html Cheers, Leif On Tue, Jul 8, 2008 at 6:31 AM, Sushil Dodake <sus...@gm...> wrote: > Hi all, > > i am using a Java Wrapper and a Quartz schedular to trigger certain > processes. > i have configured my applications logging to the console from where the > wrapper picks that stuf and loggs it in the logfile. > i.e. my Log4j.properties refelects > > > # Set root category priority to INFO and its only appender to CONSOLE the > wrapper will log everything on the console to the > > #log file so that there won't be two processes trying to get the lock on the > log file and the which might cause problmes. > > #log4j.rootCategory=INFO, CONSOLE > > log4j.rootCategory=INFO, CONSOLE > > # CONSOLE is set to be a ConsoleAppender using a PatternLayout. > > log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender > > log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout > > log4j.appender.CONSOLE.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n > > > > while my wrapper configuration file snippet is as below > > #******************************************************************** > > # Wrapper Logging Properties > > #******************************************************************** > > # Format of output for the console. (See docs for formats) > > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > > wrapper.console.loglevel=INFO > > # Log file to use for wrapper output logging. > > wrapper.logfile=../logs/wrapper.log > > # Format of output for the log file. (See docs for formats) > > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > > wrapper.logfile.loglevel=DEBUG > > # Maximum size that the log file will be allowed to grow to before > > # the log is rolled. Size is specified in bytes. The default value > > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > > wrapper.logfile.maxsize=20m > > # Maximum number of rolled log files which will be allowed before old > > # files are deleted. The default value of 0 implies no limit. > > wrapper.logfile.maxfiles=20 > > # Log Level for sys/event log output. (See docs for log levels) > > wrapper.syslog.loglevel=NONE > > > > now my issue is this kind of logging loggs everything as expected but as my > process runs 24 X 7 the log files are very big (i used the rolling) > > as i could see some redundant log statements of the wrapper and the JVM > increasing the file size > > e.g. > > > > INFO | jvm 1 | 2008/07/07 16:12:21 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/07 16:12:21 | read a packet PING : ok > DEBUG | wrapper | 2008/07/07 16:12:21 | Got ping response from JVM > DEBUG | wrapperp | 2008/07/07 16:12:25 | send a packet PING : ping > INFO | jvm 1 | 2008/07/07 16:12:25 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/07 16:12:25 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/07 16:12:25 | read a packet PING : ok > DEBUG | wrapper | 2008/07/07 16:12:25 | Got ping response from JVM > DEBUG | wrapperp | 2008/07/07 16:12:29 | send a packet PING : ping > INFO | jvm 1 | 2008/07/07 16:12:29 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/07 16:12:29 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/07 16:12:29 | read a packet PING : ok > DEBUG | wrapper | 2008/07/07 16:12:29 | Got ping response from JVM > DEBUG | wrapperp | 2008/07/07 16:12:33 | send a packet PING : ping > INFO | jvm 1 | 2008/07/07 16:12:33 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/07 16:12:33 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/07 16:12:33 | read a packet PING : ok > DEBUG | wrapper | 2008/07/07 16:12:33 | Got ping response from JVM > DEBUG | wrapperp | 2008/07/07 16:12:37 | send a packet PING : ping > INFO | jvm 1 | 2008/07/07 16:12:37 | Received a packet PING : ping > INFO | jvm 1 | 2008/07/07 16:12:37 | Send a packet PING : ok > DEBUG | wrapperp | 2008/07/07 16:12:37 | read a packet PING : ok > > > > can these statements be filtered or can they be stopped from going in to the > log file? > > the only option i could see is seperating the loggs of the wrapper and my > application in 2 diff files but that is a very crude way to maintain 2 same > logs in diffrent files. > > any suggestions on this? > > > > regards, > > Sushil > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Sushil D. <sus...@gm...> - 2008-07-07 21:31:43
|
Hi all, i am using a Java Wrapper and a Quartz schedular to trigger certain processes. i have configured my applications logging to the console from where the wrapper picks that stuf and loggs it in the logfile. i.e. my Log4j.properties refelects # Set root category priority to INFO and its only appender to CONSOLE the wrapper will log everything on the console to the #log file so that there won't be two processes trying to get the lock on the log file and the which might cause problmes. #log4j.rootCategory=INFO, CONSOLE log4j.rootCategory=INFO, CONSOLE # CONSOLE is set to be a ConsoleAppender using a PatternLayout. log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n while my wrapper configuration file snippet is as below #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=PM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=INFO # Log file to use for wrapper output logging. wrapper.logfile=../logs/wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=DEBUG # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m = 10 megabytes. wrapper.logfile.maxsize=20m # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=20 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=NONE now my issue is this kind of logging loggs everything as expected but as my process runs 24 X 7 the log files are very big (i used the rolling) as i could see some redundant log statements of the wrapper and the JVM increasing the file size e.g. INFO | jvm 1 | 2008/07/07 16:12:21 | Send a packet PING : ok DEBUG | wrapperp | 2008/07/07 16:12:21 | read a packet PING : ok DEBUG | wrapper | 2008/07/07 16:12:21 | Got ping response from JVM DEBUG | wrapperp | 2008/07/07 16:12:25 | send a packet PING : ping INFO | jvm 1 | 2008/07/07 16:12:25 | Received a packet PING : ping INFO | jvm 1 | 2008/07/07 16:12:25 | Send a packet PING : ok DEBUG | wrapperp | 2008/07/07 16:12:25 | read a packet PING : ok DEBUG | wrapper | 2008/07/07 16:12:25 | Got ping response from JVM DEBUG | wrapperp | 2008/07/07 16:12:29 | send a packet PING : ping INFO | jvm 1 | 2008/07/07 16:12:29 | Received a packet PING : ping INFO | jvm 1 | 2008/07/07 16:12:29 | Send a packet PING : ok DEBUG | wrapperp | 2008/07/07 16:12:29 | read a packet PING : ok DEBUG | wrapper | 2008/07/07 16:12:29 | Got ping response from JVM DEBUG | wrapperp | 2008/07/07 16:12:33 | send a packet PING : ping INFO | jvm 1 | 2008/07/07 16:12:33 | Received a packet PING : ping INFO | jvm 1 | 2008/07/07 16:12:33 | Send a packet PING : ok DEBUG | wrapperp | 2008/07/07 16:12:33 | read a packet PING : ok DEBUG | wrapper | 2008/07/07 16:12:33 | Got ping response from JVM DEBUG | wrapperp | 2008/07/07 16:12:37 | send a packet PING : ping INFO | jvm 1 | 2008/07/07 16:12:37 | Received a packet PING : ping INFO | jvm 1 | 2008/07/07 16:12:37 | Send a packet PING : ok DEBUG | wrapperp | 2008/07/07 16:12:37 | read a packet PING : ok can these statements be filtered or can they be stopped from going in to the log file? the only option i could see is seperating the loggs of the wrapper and my application in 2 diff files but that is a very crude way to maintain 2 same logs in diffrent files. any suggestions on this? regards, Sushil |
|
From: Leif M. <le...@ta...> - 2008-07-04 00:58:53
|
Hi all, A quick update. We released the HP-UX PA-RISC 32 and 64-bit versions of the Wrapper. These use the same codebase as 3.3.0. Some users have asked for these so if you are one of them, please give them a try: http://wrapper.tanukisoftware.org/doc/english/download.jsp Cheers, Leif |
|
From: Philipp K. <phi...@gm...> - 2008-06-30 15:17:04
|
Only use 1.5. No need to have backward comptability to 1.2 imho On Mon, Jun 30, 2008 at 1:03 PM, Markus Schlegel <sc...@gm...> wrote: > 1.5 is sufficient for us. > Actually we use 1.6 for new releases. > Older releases still use 1.5 for 2-3 years. > > Markus > > 2008/6/30 Leif Mortenson <le...@ta...>: >> >> Hi all, >> The Wrapper has historically always been able to run on >> any JVM 1.2 and above. There are a couple changes I >> am considering which would make the minimum supported >> JVM version be 1.4. >> >> My question is, are you aware of any applications which >> are still making use of 1.2, or even 1.3 JVMs? I know of >> a couple customer applications which have been running >> on 1.3 JVMs for years. They are stable and unlikely to >> require any upgrades in the near future however. >> >> Cheers, >> Leif >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- The Dude Abides! |
|
From: Leif M. <le...@ta...> - 2008-06-30 13:43:31
|
Vin, Thanks for letting me know. It is still weird that the error message in the logs was not being displayed. I wonder what the error was. I have actually had problems with the Windows version of 1.4.2.x JVMs where one or more files in the JVM will become corrupted if Windows crashes while a JVM is running. This requires a JVM reinstall. I've seen this 3 times on my own. It doesn't appear to be a problem only with Java though. I have had other system files or directories vanish after a bad windows crash several times. These were always with the "safe" NTFS file system. (Deleted windows rant) :-) Anyway, glad you got it working. Cheers, Leif On Mon, Jun 30, 2008 at 7:12 PM, Vincent Finn <v.f...@gm...> wrote: > Hi, > > Good news. I uninstalled Java nd reinstalled it and the wrapper works again! > My installation must have become corrupt somehow which is worrying but > nothing to do with the wrapper! > > Vin > > On Thu, Jun 26, 2008 at 2:38 AM, Leif Mortenson <le...@ta...> > wrote: >> >> Vin, >> Given that the error message is not displaying correctly, I am wondering >> if there is a general character encoding problem. The Wrapper is not >> yet localized and double byte safe. This is on our todo list. >> >> 1) What is the locale of your Windows? ie. Japanese, English, etc. >> >> 2) What is the full path to where the wrapper.exe file is located? You >> have several relative paths in your configuration which in itself should >> be fine. >> >> 3) When you ran your "-version" test with the testwrapper configuration >> file, what was the full path to that wrapper.exe? >> >> 4) In case either of the above two paths contain non-ascii characters, >> could you try your test in a simple directory like c:\myapp\ ? >> >> Cheers, >> Leif >> >> Vincent Finn wrote: >> > Ok, >> > >> > If there is anything I can do to help narrow it down further let me >> > know. >> > >> > Vin >> > >> > On Tue, Jun 24, 2008 at 6:12 PM, Leif Mortenson >> > <le...@ta... <mailto:le...@ta...>> wrote: >> > >> > Vincent, >> > One of the lines of output from your log file does not display the >> > error message that should be telling me what the cause of your >> > problems is. >> > >> > Your log file has the line: >> > Unable to execute Java command. >> > >> > But when I run the released Windows 3.3.0 release it generates the >> > following message: >> > Unable to execute Java command. The system cannot find the file >> > specified. (0x2) >> > >> > That error message is generated with the following code: >> > log_printf(WRAPPER_SOURCE_WRAPPER, LEVEL_FATAL, >> > "Unable to execute Java command. %s", >> > getLastErrorText()); >> > >> > For some reason, your log output does not include the error >> > message and I am >> > trying to understand why. I had added that error message back in >> > 2004 >> > to help track >> > down the cause of problems like this. >> > >> > If as I assume, you are indeed using the official release then I >> > need >> > to figure out why >> > the getLastErrorText() function is returning "" on your machine. >> > That >> > line in your log >> > file does include trailing spaces so I think this is what is >> > happening. >> > >> > Thanks, >> > Leif >> > >> > >> > >> > On Tue, Jun 24, 2008 at 10:14 PM, Vincent Finn <v.f...@gm... >> > <mailto:v.f...@gm...>> wrote: >> > > Hi, >> > > >> > > Yeah, I am just running it in from the console. >> > > >> > > I have attached the log file but there not a lot in it. >> > > >> > > I also tried the trivial sample attached, all it does is run "java >> > > -version". >> > > That fails with the same error. >> > > >> > > Vin >> > > >> > > On Tue, Jun 24, 2008 at 12:47 PM, Leif Mortenson >> > <le...@ta... <mailto:le...@ta...>> >> > > wrote: >> > >> >> > >> Vincent, >> > >> To confirm, when you run with the Wrapper, you are running in a >> > console >> > >> and not >> > >> as a Service correct? >> > >> >> > >> Looking at your wrapper.conf, I did not see anything that stood >> > out as >> > >> incorrect. >> > >> >> > >> Could you please set the wrapper.debug=true property and then >> > reply back >> > >> with >> > >> the full resulting wrapper.log file. Delete the only file >> > before you >> > >> start so we only >> > >> get a single JVM run. >> > >> >> > >> Thanks, >> > >> Leif >> > >> >> > >> On Tue, Jun 24, 2008 at 7:08 PM, Vincent Finn >> > <v.f...@gm... <mailto:v.f...@gm...>> wrote: >> > >> > Hi, >> > >> > >> > >> > I have seen this error mentioned in the forum but it doesn't >> > to be for >> > >> > the >> > >> > same problem as I am having. >> > >> > >> > >> > I am using JSW 3.3.0 on Windows XP (32bit). >> > >> > I am simply trying to run the batch file in the bin folder >> > >> > (serviceName.bat) >> > >> > and I get the error >> > >> > "Critical error: wait for JVM process failed" >> > >> > >> > >> > I have attached my config file, and a file containing the >> > command line >> > >> > output by the wrapper (without the -Dwrapper.key argument). >> > >> > >> > >> > When I run the wrapper the output is: >> > >> > >> > >> > wrapper | Launching a JVM... >> > >> > wrapper | Unable to execute Java command. >> > >> > wrapper | C:\...\java ... >> > >> > wrapper | Critical error: wait for JVM process failed >> > >> > >> > >> > >> > >> > If I run the command directly on the command line it works >> > perfectly, it >> > >> > only fails when run through the wrapper. >> > >> > >> > >> > Any ideas as to what might be wrong? >> > >> > >> > >> > Thanks, Vin >> > >> > >> > >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Markus S. <sc...@gm...> - 2008-06-30 11:03:19
|
1.5 is sufficient for us. Actually we use 1.6 for new releases. Older releases still use 1.5 for 2-3 years. Markus 2008/6/30 Leif Mortenson <le...@ta...>: > Hi all, > The Wrapper has historically always been able to run on > any JVM 1.2 and above. There are a couple changes I > am considering which would make the minimum supported > JVM version be 1.4. > > My question is, are you aware of any applications which > are still making use of 1.2, or even 1.3 JVMs? I know of > a couple customer applications which have been running > on 1.3 JVMs for years. They are stable and unlikely to > require any upgrades in the near future however. > > Cheers, > Leif > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Vincent F. <v.f...@gm...> - 2008-06-30 10:12:48
|
Hi,
Good news. I uninstalled Java nd reinstalled it and the wrapper works again!
My installation must have become corrupt somehow which is worrying but
nothing to do with the wrapper!
Vin
On Thu, Jun 26, 2008 at 2:38 AM, Leif Mortenson <le...@ta...>
wrote:
> Vin,
> Given that the error message is not displaying correctly, I am wondering
> if there is a general character encoding problem. The Wrapper is not
> yet localized and double byte safe. This is on our todo list.
>
> 1) What is the locale of your Windows? ie. Japanese, English, etc.
>
> 2) What is the full path to where the wrapper.exe file is located? You
> have several relative paths in your configuration which in itself should
> be fine.
>
> 3) When you ran your "-version" test with the testwrapper configuration
> file, what was the full path to that wrapper.exe?
>
> 4) In case either of the above two paths contain non-ascii characters,
> could you try your test in a simple directory like c:\myapp\ ?
>
> Cheers,
> Leif
>
> Vincent Finn wrote:
> > Ok,
> >
> > If there is anything I can do to help narrow it down further let me know.
> >
> > Vin
> >
> > On Tue, Jun 24, 2008 at 6:12 PM, Leif Mortenson
> > <le...@ta... <mailto:le...@ta...>> wrote:
> >
> > Vincent,
> > One of the lines of output from your log file does not display the
> > error message that should be telling me what the cause of your
> > problems is.
> >
> > Your log file has the line:
> > Unable to execute Java command.
> >
> > But when I run the released Windows 3.3.0 release it generates the
> > following message:
> > Unable to execute Java command. The system cannot find the file
> > specified. (0x2)
> >
> > That error message is generated with the following code:
> > log_printf(WRAPPER_SOURCE_WRAPPER, LEVEL_FATAL,
> > "Unable to execute Java command. %s",
> > getLastErrorText());
> >
> > For some reason, your log output does not include the error
> > message and I am
> > trying to understand why. I had added that error message back in
> 2004
> > to help track
> > down the cause of problems like this.
> >
> > If as I assume, you are indeed using the official release then I need
> > to figure out why
> > the getLastErrorText() function is returning "" on your machine.
> That
> > line in your log
> > file does include trailing spaces so I think this is what is
> > happening.
> >
> > Thanks,
> > Leif
> >
> >
> >
> > On Tue, Jun 24, 2008 at 10:14 PM, Vincent Finn <v.f...@gm...
> > <mailto:v.f...@gm...>> wrote:
> > > Hi,
> > >
> > > Yeah, I am just running it in from the console.
> > >
> > > I have attached the log file but there not a lot in it.
> > >
> > > I also tried the trivial sample attached, all it does is run "java
> > > -version".
> > > That fails with the same error.
> > >
> > > Vin
> > >
> > > On Tue, Jun 24, 2008 at 12:47 PM, Leif Mortenson
> > <le...@ta... <mailto:le...@ta...>>
> > > wrote:
> > >>
> > >> Vincent,
> > >> To confirm, when you run with the Wrapper, you are running in a
> > console
> > >> and not
> > >> as a Service correct?
> > >>
> > >> Looking at your wrapper.conf, I did not see anything that stood
> > out as
> > >> incorrect.
> > >>
> > >> Could you please set the wrapper.debug=true property and then
> > reply back
> > >> with
> > >> the full resulting wrapper.log file. Delete the only file
> > before you
> > >> start so we only
> > >> get a single JVM run.
> > >>
> > >> Thanks,
> > >> Leif
> > >>
> > >> On Tue, Jun 24, 2008 at 7:08 PM, Vincent Finn
> > <v.f...@gm... <mailto:v.f...@gm...>> wrote:
> > >> > Hi,
> > >> >
> > >> > I have seen this error mentioned in the forum but it doesn't
> > to be for
> > >> > the
> > >> > same problem as I am having.
> > >> >
> > >> > I am using JSW 3.3.0 on Windows XP (32bit).
> > >> > I am simply trying to run the batch file in the bin folder
> > >> > (serviceName.bat)
> > >> > and I get the error
> > >> > "Critical error: wait for JVM process failed"
> > >> >
> > >> > I have attached my config file, and a file containing the
> > command line
> > >> > output by the wrapper (without the -Dwrapper.key argument).
> > >> >
> > >> > When I run the wrapper the output is:
> > >> >
> > >> > wrapper | Launching a JVM...
> > >> > wrapper | Unable to execute Java command.
> > >> > wrapper | C:\...\java ...
> > >> > wrapper | Critical error: wait for JVM process failed
> > >> >
> > >> >
> > >> > If I run the command directly on the command line it works
> > perfectly, it
> > >> > only fails when run through the wrapper.
> > >> >
> > >> > Any ideas as to what might be wrong?
> > >> >
> > >> > Thanks, Vin
> > >> >
> >
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
|
|
From: Mikael S. <mik...@un...> - 2008-06-30 08:43:33
|
Leif Mortenson skrev: > The Wrapper has historically always been able to run on > any JVM 1.2 and above. There are a couple changes I > am considering which would make the minimum supported > JVM version be 1.4. > > My question is, are you aware of any applications which > are still making use of 1.2, or even 1.3 JVMs? Haven't been using anything less than 1.5 here for years. |
|
From: Leif M. <le...@ta...> - 2008-06-30 01:09:48
|
Hi all, The Wrapper has historically always been able to run on any JVM 1.2 and above. There are a couple changes I am considering which would make the minimum supported JVM version be 1.4. My question is, are you aware of any applications which are still making use of 1.2, or even 1.3 JVMs? I know of a couple customer applications which have been running on 1.3 JVMs for years. They are stable and unlikely to require any upgrades in the near future however. Cheers, Leif |
165 messages has been excluded from this view by a project administrator.
