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: <bar...@on...> - 2004-03-11 15:36:25
|
Thx for your help. With your hint I got it running. In the FAQ it wasn't clear, that I got to put the figured application to: # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=de.applejuicenet.server.Daemon Thx again Good tool, good support !! Barney Leif Mortenson <le...@ta...> schrieb am 06.03.2004, 15:53:50: > Barney, > You got most of it figured out. But you still need to read through > the integration > documentation. The problem is that you specified your application's > main class as > the JVM main class. This is only possible if your application knows how > to initialize > the JVM side of the Wrapper. Most applications make use of the > WrapperSimpleApp or WrapperStartStartApp helper classes to do this for them. > Their usage is described in Integration Methods 1 and 2 in the docs. > > Let me know if you have any questions after look through that > section of the docs. > > Cheers, > Leif > > bar...@on... wrote: > > >Hi, > > > >I am having an Fileshareing server application in a jarfile. > >Now I wanted to run it as a service. I dont get it running with nohup in > >the background. > >Then I found wrapper ... > > > >I configured as discribed in the integration. > >As it is an JAR file application, that dont need any parameters (only > >config file) on startup, I found in the FAQ, that I need to look into > >the manifest.mf but I dont get it running. > > > >Below I pasted the LogOutputs with debug Infos. > >I hope someone can help me get it running > > > >Thx in advance > >Barney > >-------------------------------------------- > >I have everything in the current directory: > >>>>>>>>> > ># Application > >APP_NAME="AJ_Server" > >APP_LONG_NAME="Applejuice Java Server" > > > ># Wrapper > >WRAPPER_CMD="./wrapper" > >WRAPPER_CONF="./ajserver.conf" > > > ># Priority at which to run the wrapper. See "man nice" for valid > >priorities. > ># nice is only used if a priority is specified. > >PRIORITY= > > > ># Location of the pid file. > >PIDDIR="/var/run" > > > >>>>>>>>>> > ># from META-INF/MANIFEST.MF > >wrapper.java.mainclass=de/applejuicenet/server/Daemon > > > >wrapper.java.classpath.1=./wrapper.jar > >wrapper.java.classpath.2=./ajserver.jar > > > >wrapper.java.library.path.1=./ > >==================================== > > > >Now I am getting the following in the logfile (debug on) > >>>>>>>>> > >DEBUG | wrapper | 2004/03/05 16:22:58 | Spawning intermediate > >process... > >DEBUG | wrapper | 2004/03/05 16:22:58 | Spawning daemon process... > >STATUS | wrapper | 2004/03/05 16:22:58 | --> Wrapper Started as Daemon > >DEBUG | wrapperp | 2004/03/05 16:22:58 | server listening on port > >32000. > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[0] : java > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[1] : -Xms32m > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[2] : -Xmx128m > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[3] : > >-Djava.library.path=./ > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[4] : -classpath > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[5] : > >./wrapper.jar:./ajserver.jar > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[6] : > >-Dwrapper.key=a_DbQegXe3TBBZN8 > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[7] : > >-Dwrapper.port=32000 > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[8] : > >-Dwrapper.debug=TRUE > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[9] : > >-Dwrapper.service=TRUE > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[10] : > >-Dwrapper.cpu.timeout=10 > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[11] : > >-Dwrapper.jvmid=1 > >DEBUG | wrapper | 2004/03/05 16:22:59 | Command[12] : > >de/applejuicenet/server/Daemon > >STATUS | wrapper | 2004/03/05 16:22:59 | Launching a JVM... > >INFO | jvm 1 | 2004/03/05 16:23:02 | 4:23:02 PM start server > >INFO | jvm 1 | 2004/03/05 16:23:04 | 4:23:04 PM timediff: 2170ms > >ERROR | wrapper | 2004/03/05 16:23:30 | Startup failed: Timed out > >waiting for signal from JVM. > >ERROR | wrapper | 2004/03/05 16:23:30 | JVM did not exit on request, > >terminated > >DEBUG | wrapper | 2004/03/05 16:23:30 | JVM was only running for 31 > >seconds leading to a failed restart count of 1. > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[0] : java > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[1] : -Xms32m > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[2] : -Xmx128m > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[3] : > >-Djava.library.path=./ > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[4] : -classpath > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[5] : > >./wrapper.jar:./ajserver.jar > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[6] : > >-Dwrapper.key=mi_bxg8Mj1mV092R > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[7] : > >-Dwrapper.port=32000 > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[8] : > >-Dwrapper.debug=TRUE > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[9] : > >-Dwrapper.service=TRUE > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[10] : > >-Dwrapper.cpu.timeout=10 > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[11] : > >-Dwrapper.jvmid=2 > >DEBUG | wrapper | 2004/03/05 16:23:36 | Command[12] : > >de/applejuicenet/server/Daemon > >STATUS | wrapper | 2004/03/05 16:23:36 | Launching a JVM... > >INFO | jvm 2 | 2004/03/05 16:23:39 | 4:23:39 PM start server > >INFO | jvm 2 | 2004/03/05 16:23:41 | 4:23:41 PM timediff: 39220ms > >INFO | jvm 2 | 2004/03/05 16:24:00 | 4:24:00 PM check IP > >INFO | jvm 2 | 2004/03/05 16:24:00 | 4:24:00 PM serverip: > >80.134.23.111 > >INFO | jvm 2 | 2004/03/05 16:24:01 | java.lang.NullPointerException > >INFO | jvm 2 | 2004/03/05 16:24:01 | at > >de.applejuicenet.server.Daemon.cancel(TRUX) > >INFO | jvm 2 | 2004/03/05 16:24:01 | at > >de.applejuicenet.server.Daemon.main(TRUX) > >INFO | jvm 2 | 2004/03/05 16:24:01 | 4:24:01 PM shutdown server > >ERROR | wrapper | 2004/03/05 16:24:07 | Startup failed: Timed out > >waiting for signal from JVM. > >ERROR | wrapper | 2004/03/05 16:24:07 | JVM did not exit on request, > >terminated > >DEBUG | wrapper | 2004/03/05 16:24:07 | JVM was only running for 31 > >seconds leading to a failed restart count of 2. > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[0] : java > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[1] : -Xms32m > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[2] : -Xmx128m > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[3] : > >-Djava.library.path=./ > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[4] : -classpath > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[5] : > >./wrapper.jar:./ajserver.jar > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[6] : > >-Dwrapper.key=fCWMT4xc5U6639Xa > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[7] : > >-Dwrapper.port=32000 > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[8] : > >-Dwrapper.debug=TRUE > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[9] : > >-Dwrapper.service=TRUE > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[10] : > >-Dwrapper.cpu.timeout=10 > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[11] : > >-Dwrapper.jvmid=3 > >DEBUG | wrapper | 2004/03/05 16:24:13 | Command[12] : > >de/applejuicenet/server/Daemon > >STATUS | wrapper | 2004/03/05 16:24:13 | Launching a JVM... > >INFO | jvm 3 | 2004/03/05 16:24:16 | 4:24:16 PM start server > >INFO | jvm 3 | 2004/03/05 16:24:21 | 4:24:21 PM timediff: 20647ms > >INFO | jvm 3 | 2004/03/05 16:24:30 | 4:24:30 PM check IP > >INFO | jvm 3 | 2004/03/05 16:24:30 | 4:24:30 PM serverip: > >80.134.23.111 > >INFO | jvm 3 | 2004/03/05 16:24:31 | java.lang.NullPointerException > >INFO | jvm 3 | 2004/03/05 16:24:31 | at > >de.applejuicenet.server.Daemon.cancel(TRUX) > >INFO | jvm 3 | 2004/03/05 16:24:31 | at > >de.applejuicenet.server.Daemon.main(TRUX) > >INFO | jvm 3 | 2004/03/05 16:24:31 | 4:24:31 PM shutdown server > >ERROR | wrapper | 2004/03/05 16:24:44 | Startup failed: Timed out > >waiting for signal from JVM. > >ERROR | wrapper | 2004/03/05 16:24:44 | JVM did not exit on request, > >terminated > >DEBUG | wrapper | 2004/03/05 16:24:44 | JVM was only running for 31 > >seconds leading to a failed restart count of 3. > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[0] : java > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[1] : -Xms32m > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[2] : -Xmx128m > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[3] : > >-Djava.library.path=./ > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[4] : -classpath > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[5] : > >./wrapper.jar:./ajserver.jar > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[6] : > >-Dwrapper.key=FBbxFJJLDQRGZORT > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[7] : > >-Dwrapper.port=32000 > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[8] : > >-Dwrapper.debug=TRUE > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[9] : > >-Dwrapper.service=TRUE > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[10] : > >-Dwrapper.cpu.timeout=10 > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[11] : > >-Dwrapper.jvmid=4 > >DEBUG | wrapper | 2004/03/05 16:24:50 | Command[12] : > >de/applejuicenet/server/Daemon > >STATUS | wrapper | 2004/03/05 16:24:50 | Launching a JVM... > >INFO | jvm 4 | 2004/03/05 16:24:53 | 4:24:53 PM start server > >INFO | jvm 4 | 2004/03/05 16:24:55 | 4:24:55 PM timediff: 53168ms > >INFO | jvm 4 | 2004/03/05 16:25:03 | 4:25:03 PM check IP > >INFO | jvm 4 | 2004/03/05 16:25:03 | 4:25:03 PM serverip: > >80.134.23.111 > >INFO | jvm 4 | 2004/03/05 16:25:04 | java.lang.NullPointerException > >INFO | jvm 4 | 2004/03/05 16:25:04 | at > >de.applejuicenet.server.Daemon.cancel(TRUX) > >INFO | jvm 4 | 2004/03/05 16:25:04 | at > >de.applejuicenet.server.Daemon.main(TRUX) > >INFO | jvm 4 | 2004/03/05 16:25:04 | 4:25:04 PM shutdown server > >ERROR | wrapper | 2004/03/05 16:25:21 | Startup failed: Timed out > >waiting for signal from JVM. > >ERROR | wrapper | 2004/03/05 16:25:21 | JVM did not exit on request, > >terminated > >DEBUG | wrapper | 2004/03/05 16:25:21 | JVM was only running for 31 > >seconds leading to a failed restart count of 4. > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[0] : java > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[1] : -Xms32m > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[2] : -Xmx128m > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[3] : > >-Djava.library.path=./ > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[4] : -classpath > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[5] : > >./wrapper.jar:./ajserver.jar > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[6] : > >-Dwrapper.key=_dQEXzpzogfm35fb > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[7] : > >-Dwrapper.port=32000 > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[8] : > >-Dwrapper.debug=TRUE > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[9] : > >-Dwrapper.service=TRUE > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[10] : > >-Dwrapper.cpu.timeout=10 > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[11] : > >-Dwrapper.jvmid=5 > >DEBUG | wrapper | 2004/03/05 16:25:27 | Command[12] : > >de/applejuicenet/server/Daemon > >STATUS | wrapper | 2004/03/05 16:25:27 | Launching a JVM... > >INFO | jvm 5 | 2004/03/05 16:25:30 | 4:25:30 PM start server > >INFO | jvm 5 | 2004/03/05 16:25:35 | 4:25:35 PM timediff: 34645ms > >INFO | jvm 5 | 2004/03/05 16:25:47 | 4:25:47 PM check IP > >INFO | jvm 5 | 2004/03/05 16:25:47 | 4:25:47 PM serverip: > >80.134.23.111 > >INFO | jvm 5 | 2004/03/05 16:25:48 | java.lang.NullPointerException > >INFO | jvm 5 | 2004/03/05 16:25:48 | at > >de.applejuicenet.server.Daemon.cancel(TRUX) > >INFO | jvm 5 | 2004/03/05 16:25:48 | at > >de.applejuicenet.server.Daemon.main(TRUX) > >INFO | jvm 5 | 2004/03/05 16:25:48 | 4:25:48 PM shutdown server > >ERROR | wrapper | 2004/03/05 16:25:58 | Startup failed: Timed out > >waiting for signal from JVM. > >ERROR | wrapper | 2004/03/05 16:25:58 | JVM did not exit on request, > >terminated > >DEBUG | wrapper | 2004/03/05 16:25:58 | JVM was only running for 31 > >seconds leading to a failed restart count of 5. > >FATAL | wrapper | 2004/03/05 16:25:58 | There were 5 failed launches > >in a row, each lasting less than 300 seconds. Giving up. > >FATAL | wrapper | 2004/03/05 16:25:58 | There may be a configuration > >problem: please check the logs. > >STATUS | wrapper | 2004/03/05 16:25:59 | > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: <v1...@za...> - 2004-03-11 07:29:56
|
Service died as you described when I set ping.interval and ping.timeout toan extremely large number. I set interval back to default, timeout around 500. With multiple threads, so far running for an hour now. If the thread priority is set right, should it not be receiving and sending pings to each other. > Hi, > > Is there anyway to disable jvm ping function? I hava an application > which could be under extremely heavy load sometimes (around 5 hours). I > have try to set the property wrapper.ping.timeout=18000 > But the service die instantly. |
|
From: Taikei M. <ta...@ie...> - 2004-03-11 07:25:32
|
Service died as you described when I set ping.interval and ping.timeout to an extremely large number. I set interval back to default, timeout around 500. With multiple threads, so far running for an hour now. Taikei > Hi, > > Is there anyway to disable jvm ping function? I hava an application > which could be under extremely heavy load sometimes (around 5 hours). I > have try to set the property wrapper.ping.timeout=18000 > But the service die instantly. > > Is there any workaround for this problem? > > Thank you. > > Regards, > > Roger |
|
From: Roger C. <ro...@if...> - 2004-03-11 06:28:17
|
Hi, Is there anyway to disable jvm ping function? I hava an application which could be under extremely heavy load sometimes (around 5 hours). I have try to set the property wrapper.ping.timeout=18000 But the service die instantly. Is there any workaround for this problem? Thank you. Regards, Roger |
|
From: Leif M. <le...@ta...> - 2004-03-10 14:22:57
|
Jennifer,
I have been looking into this some more. I added some more debug
output to the
WrapperManager class to make it easier to debug this sort of problem.
You can try
it from CVS if you like. (SourceForge's public CVS is 24 hrs behind the
dev archive)
Looking over the debug log output that you sent me again, I noticed
the following
line:
INFO | jvm 7 | 2004/02/26 19:33:00 | Thread, WrapperSimpleAppMain,
handling the shutdown process.
This tells me that the WrapperSimpleApp helper class's main thread
called
WrapperManager.stop. This will happen if your class's main method throws an
uncaught exception. Does that sound what might be happening?
If this is the case then I would expect to have seen the following
output in your log.
The log you posted was edited so you may have removed it. Could you
please confirm
one way or the other?
INFO | jvm 7 | 2004/02/26 19:32:59 | WrapperSimpleApp: Encountered
an error running main: (Your exception)
If you are trying to invoke a restart on the above exception, it
will not work because
the call to WrapperManager.stop will override the restart request and
stop the Wrapper
along with its JVM.
Cheers,
Leif
Jennifer Kolar wrote:
> Leif,
>
> It appears that I never have a successful FILTER based restart. I
> have no problem getting restarts when I call WrapperManager.restart()
> internally.. however--
> if there is an exception that I didn't catch that a filter matches,
> then I never get a successful restart. I have had each of the
> following filters triggered always with the same result.
>
> I noticed that there was a recent email (Patrick Woodworth 1/23/2004)
> where another person was having similiar problems and he found
> disabling the shutdown hooks to be a soln for him.. I've had that
> disabled this whole time and don't see any difference.
>
>
> Here are my filter settings from my conf file.
>
> wrapper.filter.trigger.1=com.singingfish.werkflow.processors.ProcessorException
> wrapper.filter.action.1=RESTART
>
> wrapper.filter.trigger.2=java.lang.Error
> wrapper.filter.action.2=RESTART
>
> wrapper.filter.trigger.3=java.lang.OutOfMemoryError
> wrapper.filter.action.3=RESTART
>
>
> I also have these set if it provides any help.. ( I have tried
> playing around w/ different startup timeouts and invocation times and
> it seems to make no difference)
>
> wrapper.jvm_exit.timeout=30
> wrapper.cpu.timeout=10
> wrapper.ping.timeout=300
> wrapper.ping.interval=5
> wrapper.restart.delay=1
> wrapper.max_failed_invocations=3
> wrapper.successful_invocation_time=10
> wrapper.startup.timeout=30
> wrapper.request_thread_dump_on_failed_jvm_exit=FALSE
> wrapper.ignore_signals=TRUE
> wrapper.disable_shutdown_hook=TRUE
>
> And again, here is the result I see whenever a filter is triggered:
>
>
> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched.
> Restarting JVM.*
> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess() called*
> ... (stuff from my stacktrack)
> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched.
> Restarting JVM.*
> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess()
> called. (IGNORED)*
> INFO | jvm 7 | 2004/02/26 19:32:59 | java.lang.Error:
> com.singingfish.werkflow.processors.ProcessorException: Unexpected
> exception in cracker
> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched.
> Restarting JVM.*
> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess()
> called. (IGNORED)*
> ... (stuff from my stack track)
> INFO | jvm 7 | 2004/02/26 19:32:59 | Send a packet STOP : 0
> DEBUG | wrapperp | 2004/02/26 19:32:59 | read a packet STOP : 0
> DEBUG | wrapper | 2004/02/26 19:32:59 | JVM requested a shutdown. (0)
> DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperStopProcess(0) called.
> DEBUG | wrapper | 2004/02/26 19:32:59 | Sending stop signal to JVM
> DEBUG | wrapperp | 2004/02/26 19:32:59 | send a packet STOP : NULL
> INFO | jvm 7 | 2004/02/26 19:32:59 | Received a packet STOP :
> INFO | jvm 7 | 2004/02/26 19:33:00 | Thread,
> WrapperSimpleAppMain, handling the shutdown process.
> INFO | jvm 7 | 2004/02/26 19:33:00 | calling listener.stop()
> INFO | jvm 7 | 2004/02/26 19:33:00 | WrapperSimpleApp: stop(0)
> INFO | jvm 7 | 2004/02/26 19:33:00 | returned from listener.stop()
> INFO | jvm 7 | 2004/02/26 19:33:00 | Send a packet STOPPED : 0
> DEBUG | wrapperp | 2004/02/26 19:33:00 | read a packet STOPPED : 0
> DEBUG | wrapper | 2004/02/26 19:33:00 | JVM signalled that it was
> stopped.
> INFO | jvm 7 | 2004/02/26 19:33:00 | Closing socket.
> DEBUG | wrapperp | 2004/02/26 19:33:00 | socket read no code (closed?).
> INFO | jvm 7 | 2004/02/26 19:33:00 | calling System.exit(0)
> INFO | jvm 7 | 2004/02/26 19:33:00 | Server daemon shut down
> DEBUG | wrapper | 2004/02/26 19:33:00 | JVM exited normally.
> STATUS | wrapper | 2004/02/26 19:33:01 | <-- Wrapper Stopped
> STATUS | wrapper | 2004/02/26 19:36:28 | CrackerAgent3 removed.
>
>
> in comparison-- a normal restart has the following ...
>
>
> INFO | jvm 6 | 2004/02/26 19:31:48 | 2004-02-26 19:31:48,107
> DEBUG [WrapperSimpleAppMain] WerkflowAgent -
> WerkflowEngine requested VM restart (null). Shutting down...
> INFO | jvm 6 | 2004/02/26 19:31:48 | Send a packet RESTART : restart
> DEBUG | wrapperp | 2004/02/26 19:31:48 | read a packet RESTART : restart
> STATUS | wrapper | 2004/02/26 19:31:48 | JVM requested a restart.
> DEBUG | wrapper | 2004/02/26 19:31:48 | wrapperRestartProcess() called.
> DEBUG | wrapper | 2004/02/26 19:31:48 | Sending stop signal to JVM
> DEBUG | wrapperp | 2004/02/26 19:31:48 | send a packet STOP : NULL
> INFO | jvm 6 | 2004/02/26 19:31:48 | Received a packet STOP :
> INFO | jvm 6 | 2004/02/26 19:31:49 | Thread,
> WrapperSimpleAppMain, handling the shutdown process.
> INFO | jvm 6 | 2004/02/26 19:31:49 | calling listener.stop()
> INFO | jvm 6 | 2004/02/26 19:31:49 | WrapperSimpleApp: stop(0)
> INFO | jvm 6 | 2004/02/26 19:31:49 | returned from listener.stop()
> INFO | jvm 6 | 2004/02/26 19:31:49 | Send a packet STOPPED : 0
> DEBUG | wrapperp | 2004/02/26 19:31:49 | read a packet STOPPED : 0
> DEBUG | wrapper | 2004/02/26 19:31:49 | JVM signalled that it was
> stopped.
> INFO | jvm 6 | 2004/02/26 19:31:49 | Closing socket.
> DEBUG | wrapperp | 2004/02/26 19:31:49 | socket read no code (closed?).
> INFO | jvm 6 | 2004/02/26 19:31:50 | calling System.exit(0)
> INFO | jvm 6 | 2004/02/26 19:31:50 | Server daemon shut down
> DEBUG | wrapper | 2004/02/26 19:31:50 | JVM exited normally.
> STATUS | wrapper | 2004/02/26 19:31:52 | Launching a JVM...
> DEBUG | wrapper | 2004/02/26 19:31:52 | command:
> "C:\WINNT\system32\java.exe"
> -Dcom.singingfish.core.utils.config.dir=c:/sf/config
> -Duser.dir=C:\aolrun -Dsun.rmi.loader.logLevel=VERBOSE
> -Dsun.rmi.server.logLevel=VERBOSE -Dsun.rmi.transport.logLevel=VERBOSE
> -Dsun.rmi.transport.tcp.logLevel=VERBOSE
> -Dsun.rmi.transport.proxy.logLevel=VERBOSE -Xms3m -Xmx96m
> -Djava.library.path="c:/sf/lib;c:/winnt;c:/winnt/system32;c:/j2sdk1.4.2_02/bin"
> -classpath
> "c:/sf/java/classes;c:/sf/java/jars/commons-logging-1.0.3/commons-logging.jar;c:/sf/java/jars/jakarta-log4j-1.2.8/dist/lib/log4j-1.2.8.jar;c:/sf/java/jars/jakarta-oro-2.0.4/jakarta-oro-2.0.4.jar;c:/sf/java/jars/quicktime_6_5/QTJava.zip;c:/sf/java/jars/xerces-1_3_1/xerces.jar;c:/sf/java/jars/toplink/TOPLink.jar;c:/sf/java/jars/toplink/Tools.jar;c:/sf/java/jars/toplink/TOPLinkX.jar;c:/sf/java/jars/oracle_jdbc_9_2_03/ojdbc14.jar;c:/sf/java/jars/commons-httpclient-2.0/commons-httpclient-2.0-final.jar"
> -Dwrapper.key="VRxfE5Fd856GSIaF" -Dwrapper.port=32013
> -Dwrapper.debug="TRUE" -Dwrapper.ignore_signals="TRUE"
> -Dwrapper.service="TRUE" -Dwrapper.disable_shutdown_hook="TRUE"
> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=7
> org.tanukisoftware.wrapper.WrapperSimpleApp
> com.singingfish.werkflow.agent.WerkflowAgent
> c:/sf/config/workflow/specs/cracker.spec CrackerAgent3
> DEBUG | wrapper | 2004/02/26 19:31:52 | Java Virtual Machine started
> (PID=9244)
> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper Manager: JVM #7
> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper Manager: Using wrapper
> INFO | jvm 7 | 2004/02/26 19:31:52 | Calling native
> initialization method.
> INFO | jvm 7 | 2004/02/26 19:31:52 | Initializing WrapperManager
> native library.
> INFO | jvm 7 | 2004/02/26 19:31:52 | Java Executable:
> C:\WINNT\system32\java.exe
> INFO | jvm 7 | 2004/02/26 19:31:52 | Java Version :
> 1.4.2_02-b03 Java HotSpot(TM) Client VM
> INFO | jvm 7 | 2004/02/26 19:31:52 | Java VM Vendor : Sun
> Microsystems Inc.
> INFO | jvm 7 | 2004/02/26 19:31:52 |
> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper (Version 3.0.5)
> INFO | jvm 7 | 2004/02/26 19:31:52 |
> INFO | jvm 7 | 2004/02/26 19:31:52 | Open socket to wrapper
> attempted on port 32013...
> INFO | jvm 7 | 2004/02/26 19:31:52 | Opened Socket to port 3242
> INFO | jvm 7 | 2004/02/26 19:31:52 | Send a packet KEY :
> VRxfE5Fd856GSIaF
> INFO | jvm 7 | 2004/02/26 19:31:52 |
> handleSocket(Socket[addr=/127.0.0.1,port=32013,localport=3242])
> DEBUG | wrapperp | 2004/02/26 19:31:52 | accepted a socket from
> 127.0.0.1 on port 3242
> DEBUG | wrapperp | 2004/02/26 19:31:52 | read a packet KEY :
> VRxfE5Fd856GSIaF
> DEBUG | wrapper | 2004/02/26 19:31:52 | Got key from JVM:
> VRxfE5Fd856GSIaF
> DEBUG | wrapperp | 2004/02/26 19:31:52 | send a packet LOW_LOG_LEVEL : 1
> DEBUG | wrapperp | 2004/02/26 19:31:52 | send a packet PING_TIMEOUT : 300
> DEBUG | wrapper | 2004/02/26 19:31:52 | Start Application.
> ....
|
|
From: Jennifer K. <jk...@si...> - 2004-03-09 19:12:16
|
yes- the syslog.loglevel one is the one that controls eventlog logging =20= levels and yes, set it to NONE On Mar 9, 2004, at 10:30 AM, john yanlin wrote: > Hi, Jennifer, > > Thanks for the reply! There are three loglevel related properties: > > -- wrapper.console.loglevel > -- wrapper.logfile.loglevel =20 > -- wrapper.syslog.loglevel =20 > > you are talking about the syslog property, right? by disabling it you > mean set it to NONE? > I'll give it a shot. > > Also, I am quite interested in finding out what was happening which > caused the log messed up (content mixed) -- I believe that would be = the > root of the problem which caused the service hung. Hopefully somebody > will be able to point me to some direction. > > Thanks, > John Yanlin > > > On Tue, 9 Mar 2004 08:23:27 -0800, "Jennifer Kolar" > <jk...@si...> said: >> I too have seen a lot of CPU usage where 100% of CPU is being = consumed >> on a 4 proc box.. however, that is typically tied to a lot of event >> logging ... you might look at what level >> of logging you have set for the event manager.. my CPU usage goes = down >> significantly when I disable that.. Can anyone enlighten on why the >> drastic CPU usage for event logging? >> >> I am also seeing significantly increased java memory usage.. and out =20= >> of >> memory errors where I never saw that with the same code outside of >> the service. So I'd be interested in any response here too. >> >> Jennifer >> On Mar 9, 2004, at 7:51 AM, john yanlin wrote: >> >>> Hi, All, >>> >>> We have been using the wrapper for some win NT services. Recently we >>> occasionally ran into some problem where the services consume almost >>> all >>> (99%, 100%) the CPU resources of a dual-CPU machine. The following =20= >>> is a >>> segment of the wrapper log file: >>> >>> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 >>> =3D=3D >>> =3D=3D=3D=3D=3D=3D >>> INFO | jvm 1 | 2004/02/18 06:31:25 | Send a packet 103 : ok >>> DEBUG | wrapperp | 2004/02/18 06:31:25 | read a packet 103 : ok >>> DEBUG | wrapper | 2004/02/18 06:31:25 | Got ping response from JVM >>> DEBUG | wrapper | 2004/02/18 06:31:26 | ServiceControlHandler(4) >>> DEBUG | wrapper | 2004/02/18 06:31:26 | =20 >>> SERVICE_CONTROL_INTERROGATE >>> DEBUG | wrapperp | 2004/02/18 06:31:31 | sent 6 bytes >>> INFO | jvm 1 | 2004/02/18 06:31:31 | Received a packet 103 : =20= >>> ping >>> INFO | jvm 1 | 2004/02/18 06:31:31 | Send a packet 103 : ok >>> DEBUG | wrapperp | 2004/02/18 06:31:31 | read a packet 103 : ok >>> DEBUG | wrapper | 2004/02/18 06:31:31 | Got ping response from JVM >>> DEBUG | wrapperp | 2004/02/18 06:31:37 | sent 6 bytes >>> DEBUG | wrapper | 2004/02/18 06:31:37 | ServiceControlHandler(4) >>> Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet =20= >>> 103 : >>> ping >>> Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet =20= >>> 103 : >>> ping >>> 2004/02/18 06:31:37 | SERVICE_CONTROL_INTERROGATE >>> STATUS | wrapper | 2004/02/18 10:38:00 | --> Wrapper Started as >>> Service >>> DEBUG | wrapperp | 2004/02/18 10:38:00 | server listening on port >>> 17005. >>> DEBUG | wrapper | 2004/02/18 10:38:00 | JVM was only running for >>> -322562155 seconds leading to a failed restart count of 1. >>> STATUS | wrapper | 2004/02/18 10:38:00 | Launching a JVM... >>> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 >>> =3D=3D >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> >>> =46rom which we can see that at 6:31:37 something went wrong. There = are >>> two >>> lines in the log are exactly the same and the contents are sort of >>> mixed. >>> It should be something like: >>> >>> DEBUG | wrapper | 2004/02/18 | 06:31:37 | Received a packet 103 : =20= >>> ping >>> >>> Instead, it came out mixed as: >>> >>> Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet =20= >>> 103 : >>> ping >>> Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet =20= >>> 103 : >>> ping >>> >>> The DEBUG and the date time were mixed. There was a 'B' in the =20 >>> 'DEBUG' >>> missing. the 'J' for 'Jvm 1' was also missing. During that time, the >>> service shown active in the windows service manager panel. But the >>> actual >>> service was hung. >>> >>> It seems that there was something happening inside the wrapper = native >>> part. Have anyone ever got the similar situation like this? Could >>> anyone >>> suggest what was happening here? >>> >>> Thanks, >>> >>> --=20 >>> http://www.fastmail.fm - And now for something completely different=85= >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by: IBM Linux Tutorials >>> Free Linux tutorial presented by Daniel Robbins, President and CEO = of >>> GenToo technologies. Learn everything from fundamentals to system >>> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dclick >>> _______________________________________________ >>> Wrapper-user mailing list >>> Wra...@li... >>> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: IBM Linux Tutorials >> Free Linux tutorial presented by Daniel Robbins, President and CEO of >> GenToo technologies. Learn everything from fundamentals to system >> administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dclick >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > --=20 > http://www.fastmail.fm - Same, same, but different=85 > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dclick > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: john y. <joh...@fa...> - 2004-03-09 18:47:54
|
Hi, Jennifer, Thanks for the reply! There are three loglevel related properties: -- wrapper.console.loglevel -- wrapper.logfile.loglevel=20 -- wrapper.syslog.loglevel=20 you are talking about the syslog property, right? by disabling it you mean set it to NONE? I'll give it a shot. Also, I am quite interested in finding out what was happening which caused the log messed up (content mixed) -- I believe that would be the root of the problem which caused the service hung. Hopefully somebody will be able to point me to some direction. Thanks, John Yanlin On Tue, 9 Mar 2004 08:23:27 -0800, "Jennifer Kolar" <jk...@si...> said: > I too have seen a lot of CPU usage where 100% of CPU is being consumed=20= =20 > on a 4 proc box.. however, that is typically tied to a lot of event=20=20 > logging ... you might look at what level > of logging you have set for the event manager.. my CPU usage goes down=20= =20 > significantly when I disable that.. Can anyone enlighten on why the=20=20 > drastic CPU usage for event logging? >=20 > I am also seeing significantly increased java memory usage.. and out of= =20=20 > memory errors where I never saw that with the same code outside of > the service. So I'd be interested in any response here too. >=20 > Jennifer > On Mar 9, 2004, at 7:51 AM, john yanlin wrote: >=20 > > Hi, All, > > > > We have been using the wrapper for some win NT services. Recently we > > occasionally ran into some problem where the services consume almost=20= =20 > > all > > (99%, 100%) the CPU resources of a dual-CPU machine. The following is a > > segment of the wrapper log file: > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 > > =3D=3D=3D=3D=3D=3D > > INFO | jvm 1 | 2004/02/18 06:31:25 | Send a packet 103 : ok > > DEBUG | wrapperp | 2004/02/18 06:31:25 | read a packet 103 : ok > > DEBUG | wrapper | 2004/02/18 06:31:25 | Got ping response from JVM > > DEBUG | wrapper | 2004/02/18 06:31:26 | ServiceControlHandler(4) > > DEBUG | wrapper | 2004/02/18 06:31:26 | SERVICE_CONTROL_INTERROGATE > > DEBUG | wrapperp | 2004/02/18 06:31:31 | sent 6 bytes > > INFO | jvm 1 | 2004/02/18 06:31:31 | Received a packet 103 : ping > > INFO | jvm 1 | 2004/02/18 06:31:31 | Send a packet 103 : ok > > DEBUG | wrapperp | 2004/02/18 06:31:31 | read a packet 103 : ok > > DEBUG | wrapper | 2004/02/18 06:31:31 | Got ping response from JVM > > DEBUG | wrapperp | 2004/02/18 06:31:37 | sent 6 bytes > > DEBUG | wrapper | 2004/02/18 06:31:37 | ServiceControlHandler(4) > > Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : > > ping > > Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : > > ping > > 2004/02/18 06:31:37 | SERVICE_CONTROL_INTERROGATE > > STATUS | wrapper | 2004/02/18 10:38:00 | --> Wrapper Started as=20=20 > > Service > > DEBUG | wrapperp | 2004/02/18 10:38:00 | server listening on port=20= =20 > > 17005. > > DEBUG | wrapper | 2004/02/18 10:38:00 | JVM was only running for > > -322562155 seconds leading to a failed restart count of 1. > > STATUS | wrapper | 2004/02/18 10:38:00 | Launching a JVM... > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > From which we can see that at 6:31:37 something went wrong. There are= =20=20 > > two > > lines in the log are exactly the same and the contents are sort of=20= =20 > > mixed. > > It should be something like: > > > > DEBUG | wrapper | 2004/02/18 | 06:31:37 | Received a packet 103 : ping > > > > Instead, it came out mixed as: > > > > Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : > > ping > > Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : > > ping > > > > The DEBUG and the date time were mixed. There was a 'B' in the 'DEBUG' > > missing. the 'J' for 'Jvm 1' was also missing. During that time, the > > service shown active in the windows service manager panel. But the=20= =20 > > actual > > service was hung. > > > > It seems that there was something happening inside the wrapper native > > part. Have anyone ever got the similar situation like this? Could=20=20 > > anyone > > suggest what was happening here? > > > > Thanks, > > > > --=20 > > http://www.fastmail.fm - And now for something completely different=85 > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dclick > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dclick > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user --=20 http://www.fastmail.fm - Same, same, but different=85 |
|
From: Jennifer K. <jk...@si...> - 2004-03-09 18:31:11
|
In trying to start multiple instances of my application, and thus multiple services I seem to hit a limit where no matter how long I give for a startup timeout, I always get the response Unable to start the serivce- The service did not respond to the start or control request in a timely fashion. Any ideas? I seem to hit this at what would be service # 24 or 25. I can start more services via copying registry keys around directly.. I just can't start them w/ the wrapper.exe .. thanks Jennifer |
|
From: <sou...@m4...> - 2004-03-09 18:06:35
|
Hi, I recently used this smart tool (ServiceWrapper 2.2.4) for starting Tomcat and everything worked fine (SimpleApp). Now I updated to 3.0.5 and am confronted with the strange problem that Tomcat shuts down immediately after starting. I am clueless because no log contains any error - it seems to stop right after a certain instruction. Recently I tracked it down to be a problem with a certain dynamic servlet which is the main part of a server - client architecture - therefore I cannot go on without using it ... Tomcat itself will start without any problem if I do use its startup.bat. Also using the wrapper and Tomcat as a simple Webserver works ok but in this case when I try to load the servlet on startup time Tomcat and the wrapper also shut down immediately. If I leave out the load-on-startup it shuts down right after the first call to the servlets address. Additionally let me add that I am using another native dll in my servlet for storing data. Could that cause any problems? Any help will be appreciated, Stefan Dingfelder |
|
From: Stefan D. <Ste...@gl...> - 2004-03-09 18:01:21
|
Hi, I recently used this smart tool (ServiceWrapper 2.2.4) for starting Tomcat and everything worked fine (SimpleApp). Now I updated to 3.0.5 and am confronted with the strange problem that Tomcat shuts down immediately after starting. I am clueless because no log contains any error - it seems to stop right after a certain instruction. Recently I tracked it down to be a problem with a certain dynamic servlet which is the main part of a server - client architecture - therefore I cannot go on without using it ... Tomcat itself will start without any problem if I do use its startup.bat. Also using the wrapper and Tomcat as a simple Webserver works ok but in this case when I try to load the servlet on startup time Tomcat and the wrapper also shut down immediately. If I leave out the load-on-startup it shuts down right after the first call to the servlets address. Additionally let me add that I am using another native dll in my servlet for storing data. Could that cause any problems? Any help will be appreciated, Stefan Dingfelder |
|
From: Andreas W. <and...@em...> - 2004-03-09 17:15:14
|
Jennifer,
I don't want to set it in Java but for the wrapper executable.
This is currently not possible (at least on Windows) because there are the following lines in wrapper_win.c (in fuction setWorkingDir):
1653 /* Get the full path and filename of this program */
1654 if (GetModuleFileName(NULL, szPath, 512) == 0){
...
1674 if (chdir(szPath)) {
...
The wrapper always uses the directory where the executable is in.
Cheers,
Andreas
> -----Original Message-----
> From: Jennifer Kolar [mailto:jk...@si...]
> Sent: Tuesday, March 09, 2004 5:27 PM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Wrapper directories
>
>
> you can specify the running directory (and thus not have it be where
> wrapper.exe is) in your java command line...
>
> -Duser.dir=blah
>
> in windows you can use %CD% to get the current running directory
> in unix you can use $PWD
>
> then just specify the directory value where I have "blah" above
>
>
> Jennifer
> On Mar 9, 2004, at 2:26 AM, Andreas Wendt wrote:
>
> > Leif,
> >
> > is there a chance (in the current version 3.0.5 or in a
> future one) to
> > specifiy the starting directory for the wrapper from
> "outside" (e.g.
> > via an environment variable).
> >
> > I want to integrate with JBoss, but I don't want to copy
> the wrapper
> > files to the jboss directories. Since the wrapper isn't able to use
> > another starting directory other than the executable's (Windows) or
> > the starting script's one (Unix), JBoss will not be able to start
> > properly due to some relative paths when constructing its classpath
> > from its config files.
> >
> > TIA,
> > Andreas
> > -------------------------------------------------------
> This SF.Net
> > email is sponsored by: IBM Linux Tutorials Free Linux tutorial
> > presented by Daniel Robbins, President and CEO of GenToo
> technologies.
> > Learn everything from fundamentals to system
> >
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> Wrapper-user mailing
> > list Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
|
|
From: Jennifer K. <jk...@si...> - 2004-03-09 17:12:12
|
I am actually seeing this same problem when it isn't an internal =20 exception in my code that would cause an exception.. but just when an =20= out of memory exception happens... which doesn't involve a system.exit anywhere in my code. Here is a log from my testing last night: ---------------- INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:33 | INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:33 | WrapperSimpleApp: = Encountered =20 an error running main: java.lang.OutOfMemoryError STATUS | wrapper=A0| 2004/03/09 00:27:33 | Filter trigger =20 matched.=A0Restarting JVM. DEBUG=A0| wrapper=A0| 2004/03/09 00:27:33 | wrapperRestartProcess() = called. INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:33 | = java.lang.OutOfMemoryError STATUS | wrapper=A0| 2004/03/09 00:27:33 | Filter trigger =20 matched.=A0Restarting JVM. DEBUG=A0| wrapper=A0| 2004/03/09 00:27:33 | wrapperRestartProcess() =20 called.=A0(IGNORED) INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:33 | Send a packet STOP : 0 DEBUG=A0| wrapperp | 2004/03/09 00:27:33 | read a packet STOP : 0 DEBUG=A0| wrapper=A0| 2004/03/09 00:27:33 | JVM requested a shutdown. = (0) DEBUG=A0| wrapper=A0| 2004/03/09 00:27:33 | wrapperStopProcess(0) = called. DEBUG=A0| wrapper=A0| 2004/03/09 00:27:33 | Sending stop signal to JVM DEBUG=A0| wrapperp | 2004/03/09 00:27:33 | send a packet STOP : NULL INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:33 | Received a packet STOP = : INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:34 | Thread, = WrapperSimpleAppMain, =20 handling the shutdown process. INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:34 | calling = listener.stop() INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:34 | WrapperSimpleApp: = stop(0) INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:34 | returned from = listener.stop() INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:34 | Send a packet STOPPED = : 0 DEBUG=A0| wrapperp | 2004/03/09 00:27:34 | read a packet STOPPED : 0 DEBUG=A0| wrapper=A0| 2004/03/09 00:27:34 | JVM signalled that it was =20= stopped. INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:34 | Closing socket. DEBUG=A0| wrapperp | 2004/03/09 00:27:34 | socket read no code = (closed?). INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:35 | calling System.exit(0) INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:35 | Server daemon shut = down INFO=A0=A0| jvm 4=A0=A0=A0| 2004/03/09 00:27:36 | AWTPATH C:\Program =20 Files\Java\j2re1.4.2_02\bin\jawt.dll ERROR=A0| wrapper=A0| 2004/03/09 00:28:08 | Shutdown failed: Timed out =20= waiting for the JVM to terminate. ERROR=A0| wrapper=A0| 2004/03/09 00:28:08 | Java Virtual Machine did not = =20 exit on request, terminated STATUS | wrapper=A0| 2004/03/09 00:28:09 | <-- Wrapper Stopped DEBUG=A0| wrapper=A0| 2004/03/09 00:28:09 | Exiting service process. ---------------- On Mar 8, 2004, at 11:12 AM, Jennifer Kolar wrote: > I am not calling wrapper.stop anywhere.. I only call = wrapper.restart(); > I do have some places in the code that issue System.exit(0) or =20 > System.exit(1)...however, I have ignore system events set.... > > My one question here-- I remember reading that you said there was a =20= > problem w/ restarts after a system.exit(1).. and that you said that =20= > was fixed > in your current checked in code.. I am running from a build I did of =20= > your code in CVS as of 3/1/04. > > I expect a System.exit(1) is being issued in these cases.. I will try =20= > converting that in my internal code to use an exit code of 0.. I had =20= > already made that change > in the wrapperSimpleApp and saw no difference in behavior. > > is the system.exit(1) bug still lingering ?? > > thanks > Jennifer > On Mar 6, 2004, at 6:34 AM, Leif Mortenson wrote: > >> Jennifer, >> Sorry to keep you waiting. Busy week. >> >> I tried this out and everything seems to be working correctly for =20= >> me. =46rom your log >> output, it looks like restart triggers get fired several times in =20 >> rapid succession. I tested >> this and the Wrapper appears to be handling that correctly. Once the = =20 >> restart has >> started, additional restart requests are correctly ignored. >> >> I think the problem is the following lines from your output: >> INFO | jvm 7 | 2004/02/26 19:32:59 | Send a packet STOP : 0 >> DEBUG | wrapperp | 2004/02/26 19:32:59 | read a packet STOP : 0 >> DEBUG | wrapper | 2004/02/26 19:32:59 | JVM requested a shutdown. =20= >> (0) >> DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperStopProcess(0) =20 >> called. >> >> Are you sure you are not calling System.exit or =20 >> WrapperManager.stop() someplace >> in your code? If so that will override the restart request and cause = =20 >> the Wrapper to >> shutdown. >> >> If you call System.exit, you will get the following in your log =20= >> output. System.exit >> triggers a Shutdown Hook, which you have disabled, so I don't think =20= >> this what is >> happening: >> >> INFO | jvm 1 | main | 2004/03/06 23:27:15 | Wrapper Manager: =20= >> ShutdownHook started >> INFO | jvm 1 | main | 2004/03/06 23:27:15 | Send a packet =20 >> STOP : 0 >> DEBUG | wrapperp | main | 2004/03/06 23:27:15 | read a packet =20 >> STOP : 0 >> DEBUG | wrapper | main | 2004/03/06 23:27:15 | JVM requested a =20= >> shutdown. (0) >> DEBUG | wrapper | main | 2004/03/06 23:27:15 | =20 >> wrapperStopProcess(0) called. >> DEBUG | wrapper | main | 2004/03/06 23:27:15 | Sending stop =20 >> signal to JVM >> DEBUG | wrapperp | main | 2004/03/06 23:27:15 | send a packet =20 >> STOP : NULL >> >> A call you WrapperManager.stop(0) on the other hand, looks like =20= >> the following. This is >> exactly what is showing up in your log: >> >> INFO | jvm 1 | main | 2004/03/06 23:29:06 | Send a packet =20 >> STOP : 0 >> DEBUG | wrapperp | main | 2004/03/06 23:29:06 | read a packet =20 >> STOP : 0 >> DEBUG | wrapper | main | 2004/03/06 23:29:06 | JVM requested a =20= >> shutdown. (0) >> DEBUG | wrapper | main | 2004/03/06 23:29:06 | =20 >> wrapperStopProcess(0) called. >> DEBUG | wrapper | main | 2004/03/06 23:29:06 | Sending stop =20 >> signal to JVM >> DEBUG | wrapperp | main | 2004/03/06 23:29:06 | send a packet =20 >> STOP : NULL >> >> Let me know if you don't think that is the cause or have questions = =20 >> about to use >> the filters. >> >> Cheers, >> Leif >> >> Jennifer Kolar wrote: >> >>> Leif, >>> >>> It appears that I never have a successful FILTER based restart. I =20= >>> have no problem getting restarts when I call =20 >>> WrapperManager.restart() internally.. however-- >>> if there is an exception that I didn't catch that a filter matches, =20= >>> then I never get a successful restart. I have had each of the =20 >>> following filters triggered always with the same result. >>> >>> I noticed that there was a recent email (Patrick Woodworth =20 >>> 1/23/2004) where another person was having similiar problems and he = =20 >>> found disabling the shutdown hooks to be a soln for him.. I've had =20= >>> that disabled this whole time and don't see any difference. >>> >>> >>> Here are my filter settings from my conf file. >>> >>> =20 >>> = wrapper.filter.trigger.1=3Dcom.singingfish.werkflow.processors.Processo=20= >>> rException >>> wrapper.filter.action.1=3DRESTART >>> >>> wrapper.filter.trigger.2=3Djava.lang.Error >>> wrapper.filter.action.2=3DRESTART >>> >>> wrapper.filter.trigger.3=3Djava.lang.OutOfMemoryError >>> wrapper.filter.action.3=3DRESTART >>> >>> >>> I also have these set if it provides any help.. ( I have tried =20 >>> playing around w/ different startup timeouts and invocation times =20= >>> and it seems to make no difference) >>> >>> wrapper.jvm_exit.timeout=3D30 >>> wrapper.cpu.timeout=3D10 >>> wrapper.ping.timeout=3D300 >>> wrapper.ping.interval=3D5 >>> wrapper.restart.delay=3D1 >>> wrapper.max_failed_invocations=3D3 >>> wrapper.successful_invocation_time=3D10 >>> wrapper.startup.timeout=3D30 >>> wrapper.request_thread_dump_on_failed_jvm_exit=3DFALSE >>> wrapper.ignore_signals=3DTRUE >>> wrapper.disable_shutdown_hook=3DTRUE >>> >>> And again, here is the result I see whenever a filter is triggered: >>> >>> >>> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched. =20= >>> Restarting JVM.* >>> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess() =20= >>> called* >>> ... (stuff from my stacktrack) >>> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched. =20= >>> Restarting JVM.* >>> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess() =20= >>> called. (IGNORED)* >>> INFO | jvm 7 | 2004/02/26 19:32:59 | java.lang.Error: =20 >>> com.singingfish.werkflow.processors.ProcessorException: Unexpected =20= >>> exception in cracker >>> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched. =20= >>> Restarting JVM.* >>> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess() =20= >>> called. (IGNORED)* >>> ... (stuff from my stack track) >>> INFO | jvm 7 | 2004/02/26 19:32:59 | Send a packet STOP : 0 >>> DEBUG | wrapperp | 2004/02/26 19:32:59 | read a packet STOP : 0 >>> DEBUG | wrapper | 2004/02/26 19:32:59 | JVM requested a shutdown. =20= >>> (0) >>> DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperStopProcess(0) =20 >>> called. >>> DEBUG | wrapper | 2004/02/26 19:32:59 | Sending stop signal to JVM >>> DEBUG | wrapperp | 2004/02/26 19:32:59 | send a packet STOP : NULL >>> INFO | jvm 7 | 2004/02/26 19:32:59 | Received a packet STOP : >>> INFO | jvm 7 | 2004/02/26 19:33:00 | Thread, =20 >>> WrapperSimpleAppMain, handling the shutdown process. >>> INFO | jvm 7 | 2004/02/26 19:33:00 | calling listener.stop() >>> INFO | jvm 7 | 2004/02/26 19:33:00 | WrapperSimpleApp: stop(0) >>> INFO | jvm 7 | 2004/02/26 19:33:00 | returned from =20 >>> listener.stop() >>> INFO | jvm 7 | 2004/02/26 19:33:00 | Send a packet STOPPED : 0 >>> DEBUG | wrapperp | 2004/02/26 19:33:00 | read a packet STOPPED : 0 >>> DEBUG | wrapper | 2004/02/26 19:33:00 | JVM signalled that it was =20= >>> stopped. >>> INFO | jvm 7 | 2004/02/26 19:33:00 | Closing socket. >>> DEBUG | wrapperp | 2004/02/26 19:33:00 | socket read no code =20 >>> (closed?). >>> INFO | jvm 7 | 2004/02/26 19:33:00 | calling System.exit(0) >>> INFO | jvm 7 | 2004/02/26 19:33:00 | Server daemon shut down >>> DEBUG | wrapper | 2004/02/26 19:33:00 | JVM exited normally. >>> STATUS | wrapper | 2004/02/26 19:33:01 | <-- Wrapper Stopped >>> STATUS | wrapper | 2004/02/26 19:36:28 | CrackerAgent3 removed. >>> >>> >>> in comparison-- a normal restart has the following ... >>> >>> >>> INFO | jvm 6 | 2004/02/26 19:31:48 | 2004-02-26 19:31:48,107 =20= >>> DEBUG [WrapperSimpleAppMain] WerkflowAgent - =20 >>> WerkflowEngine requested VM restart (null). Shutting down... >>> INFO | jvm 6 | 2004/02/26 19:31:48 | Send a packet RESTART : =20= >>> restart >>> DEBUG | wrapperp | 2004/02/26 19:31:48 | read a packet RESTART : =20= >>> restart >>> STATUS | wrapper | 2004/02/26 19:31:48 | JVM requested a restart. >>> DEBUG | wrapper | 2004/02/26 19:31:48 | wrapperRestartProcess() =20= >>> called. >>> DEBUG | wrapper | 2004/02/26 19:31:48 | Sending stop signal to JVM >>> DEBUG | wrapperp | 2004/02/26 19:31:48 | send a packet STOP : NULL >>> INFO | jvm 6 | 2004/02/26 19:31:48 | Received a packet STOP : >>> INFO | jvm 6 | 2004/02/26 19:31:49 | Thread, =20 >>> WrapperSimpleAppMain, handling the shutdown process. >>> INFO | jvm 6 | 2004/02/26 19:31:49 | calling listener.stop() >>> INFO | jvm 6 | 2004/02/26 19:31:49 | WrapperSimpleApp: stop(0) >>> INFO | jvm 6 | 2004/02/26 19:31:49 | returned from =20 >>> listener.stop() >>> INFO | jvm 6 | 2004/02/26 19:31:49 | Send a packet STOPPED : 0 >>> DEBUG | wrapperp | 2004/02/26 19:31:49 | read a packet STOPPED : 0 >>> DEBUG | wrapper | 2004/02/26 19:31:49 | JVM signalled that it was =20= >>> stopped. >>> INFO | jvm 6 | 2004/02/26 19:31:49 | Closing socket. >>> DEBUG | wrapperp | 2004/02/26 19:31:49 | socket read no code =20 >>> (closed?). >>> INFO | jvm 6 | 2004/02/26 19:31:50 | calling System.exit(0) >>> INFO | jvm 6 | 2004/02/26 19:31:50 | Server daemon shut down >>> DEBUG | wrapper | 2004/02/26 19:31:50 | JVM exited normally. >>> STATUS | wrapper | 2004/02/26 19:31:52 | Launching a JVM... >>> DEBUG | wrapper | 2004/02/26 19:31:52 | command: =20 >>> "C:\WINNT\system32\java.exe" =20 >>> -Dcom.singingfish.core.utils.config.dir=3Dc:/sf/config =20 >>> -Duser.dir=3DC:\aolrun -Dsun.rmi.loader.logLevel=3DVERBOSE =20 >>> -Dsun.rmi.server.logLevel=3DVERBOSE =20 >>> -Dsun.rmi.transport.logLevel=3DVERBOSE =20 >>> -Dsun.rmi.transport.tcp.logLevel=3DVERBOSE =20 >>> -Dsun.rmi.transport.proxy.logLevel=3DVERBOSE -Xms3m -Xmx96m =20 >>> -Djava.library.path=3D"c:/sf/lib;c:/winnt;c:/winnt/system32;c:/=20 >>> j2sdk1.4.2_02/bin" -classpath =20 >>> "c:/sf/java/classes;c:/sf/java/jars/commons-logging-1.0.3/commons-=20= >>> logging.jar;c:/sf/java/jars/jakarta-log4j-1.2.8/dist/lib/log4j=20 >>> -1.2.8.jar;c:/sf/java/jars/jakarta-oro-2.0.4/jakarta-oro-2.0.4.jar;=20= >>> c:/sf/java/jars/quicktime_6_5/QTJava.zip;c:/sf/java/jars/xerces=20 >>> -1_3_1/xerces.jar;c:/sf/java/jars/toplink/TOPLink.jar;c:/sf/java/=20 >>> jars/toplink/Tools.jar;c:/sf/java/jars/toplink/TOPLinkX.jar;c:/sf/=20= >>> java/jars/oracle_jdbc_9_2_03/ojdbc14.jar;c:/sf/java/jars/commons-=20 >>> httpclient-2.0/commons-httpclient-2.0-final.jar" =20 >>> -Dwrapper.key=3D"VRxfE5Fd856GSIaF" -Dwrapper.port=3D32013 =20 >>> -Dwrapper.debug=3D"TRUE" -Dwrapper.ignore_signals=3D"TRUE" =20 >>> -Dwrapper.service=3D"TRUE" -Dwrapper.disable_shutdown_hook=3D"TRUE" =20= >>> -Dwrapper.cpu.timeout=3D"10" -Dwrapper.jvmid=3D7 =20 >>> org.tanukisoftware.wrapper.WrapperSimpleApp =20 >>> com.singingfish.werkflow.agent.WerkflowAgent =20 >>> c:/sf/config/workflow/specs/cracker.spec CrackerAgent3 >>> DEBUG | wrapper | 2004/02/26 19:31:52 | Java Virtual Machine =20 >>> started (PID=3D9244) >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper Manager: JVM #7 >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper Manager: Using =20 >>> wrapper >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Calling native =20 >>> initialization method. >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Initializing =20 >>> WrapperManager native library. >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Java Executable: =20 >>> C:\WINNT\system32\java.exe >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Java Version : =20 >>> 1.4.2_02-b03 Java HotSpot(TM) Client VM >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Java VM Vendor : Sun =20 >>> Microsystems Inc. >>> INFO | jvm 7 | 2004/02/26 19:31:52 | >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper (Version 3.0.5) >>> INFO | jvm 7 | 2004/02/26 19:31:52 | >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Open socket to wrapper =20 >>> attempted on port 32013... >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Opened Socket to port 3242 >>> INFO | jvm 7 | 2004/02/26 19:31:52 | Send a packet KEY : =20 >>> VRxfE5Fd856GSIaF >>> INFO | jvm 7 | 2004/02/26 19:31:52 | =20 >>> handleSocket(Socket[addr=3D/127.0.0.1,port=3D32013,localport=3D3242]) >>> DEBUG | wrapperp | 2004/02/26 19:31:52 | accepted a socket from =20 >>> 127.0.0.1 on port 3242 >>> DEBUG | wrapperp | 2004/02/26 19:31:52 | read a packet KEY : =20 >>> VRxfE5Fd856GSIaF >>> DEBUG | wrapper | 2004/02/26 19:31:52 | Got key from JVM: =20 >>> VRxfE5Fd856GSIaF >>> DEBUG | wrapperp | 2004/02/26 19:31:52 | send a packet =20 >>> LOW_LOG_LEVEL : 1 >>> DEBUG | wrapperp | 2004/02/26 19:31:52 | send a packet PING_TIMEOUT = =20 >>> : 300 >>> DEBUG | wrapper | 2004/02/26 19:31:52 | Start Application. >>> .... >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: IBM Linux Tutorials >> Free Linux tutorial presented by Daniel Robbins, President and CEO of >> GenToo technologies. Learn everything from fundamentals to system >> administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dc= lick >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcl= ick > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Jennifer K. <jk...@si...> - 2004-03-09 16:44:33
|
you can specify the running directory (and thus not have it be where wrapper.exe is) in your java command line... -Duser.dir=blah in windows you can use %CD% to get the current running directory in unix you can use $PWD then just specify the directory value where I have "blah" above Jennifer On Mar 9, 2004, at 2:26 AM, Andreas Wendt wrote: > Leif, > > is there a chance (in the current version 3.0.5 or in a future one) to > specifiy the starting directory for the wrapper from "outside" (e.g. > via an environment variable). > > I want to integrate with JBoss, but I don't want to copy the wrapper > files to the jboss directories. Since the wrapper isn't able to use > another starting directory other than the executable's (Windows) or > the starting script's one (Unix), JBoss will not be able to start > properly due to some relative paths when constructing its classpath > from its config files. > > TIA, > Andreas > ------------------------------------------------------- This SF.Net > email is sponsored by: IBM Linux Tutorials Free Linux tutorial > presented by Daniel Robbins, President and CEO of GenToo technologies. > Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ Wrapper-user mailing > list Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Jennifer K. <jk...@si...> - 2004-03-09 16:40:39
|
I too have seen a lot of CPU usage where 100% of CPU is being consumed =20= on a 4 proc box.. however, that is typically tied to a lot of event =20 logging ... you might look at what level of logging you have set for the event manager.. my CPU usage goes down =20= significantly when I disable that.. Can anyone enlighten on why the =20 drastic CPU usage for event logging? I am also seeing significantly increased java memory usage.. and out of =20= memory errors where I never saw that with the same code outside of the service. So I'd be interested in any response here too. Jennifer On Mar 9, 2004, at 7:51 AM, john yanlin wrote: > Hi, All, > > We have been using the wrapper for some win NT services. Recently we > occasionally ran into some problem where the services consume almost =20= > all > (99%, 100%) the CPU resources of a dual-CPU machine. The following is = a > segment of the wrapper log file: > > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 > =3D=3D=3D=3D=3D=3D > INFO | jvm 1 | 2004/02/18 06:31:25 | Send a packet 103 : ok > DEBUG | wrapperp | 2004/02/18 06:31:25 | read a packet 103 : ok > DEBUG | wrapper | 2004/02/18 06:31:25 | Got ping response from JVM > DEBUG | wrapper | 2004/02/18 06:31:26 | ServiceControlHandler(4) > DEBUG | wrapper | 2004/02/18 06:31:26 | = SERVICE_CONTROL_INTERROGATE > DEBUG | wrapperp | 2004/02/18 06:31:31 | sent 6 bytes > INFO | jvm 1 | 2004/02/18 06:31:31 | Received a packet 103 : ping > INFO | jvm 1 | 2004/02/18 06:31:31 | Send a packet 103 : ok > DEBUG | wrapperp | 2004/02/18 06:31:31 | read a packet 103 : ok > DEBUG | wrapper | 2004/02/18 06:31:31 | Got ping response from JVM > DEBUG | wrapperp | 2004/02/18 06:31:37 | sent 6 bytes > DEBUG | wrapper | 2004/02/18 06:31:37 | ServiceControlHandler(4) > Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 = : > ping > Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 = : > ping > 2004/02/18 06:31:37 | SERVICE_CONTROL_INTERROGATE > STATUS | wrapper | 2004/02/18 10:38:00 | --> Wrapper Started as =20 > Service > DEBUG | wrapperp | 2004/02/18 10:38:00 | server listening on port =20 > 17005. > DEBUG | wrapper | 2004/02/18 10:38:00 | JVM was only running for > -322562155 seconds leading to a failed restart count of 1. > STATUS | wrapper | 2004/02/18 10:38:00 | Launching a JVM... > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > =46rom which we can see that at 6:31:37 something went wrong. There = are =20 > two > lines in the log are exactly the same and the contents are sort of =20 > mixed. > It should be something like: > > DEBUG | wrapper | 2004/02/18 | 06:31:37 | Received a packet 103 : ping > > Instead, it came out mixed as: > > Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 = : > ping > Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 = : > ping > > The DEBUG and the date time were mixed. There was a 'B' in the 'DEBUG' > missing. the 'J' for 'Jvm 1' was also missing. During that time, the > service shown active in the windows service manager panel. But the =20 > actual > service was hung. > > It seems that there was something happening inside the wrapper native > part. Have anyone ever got the similar situation like this? Could =20 > anyone > suggest what was happening here? > > Thanks, > > --=20 > http://www.fastmail.fm - And now for something completely different=85 > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dclick > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: john y. <joh...@fa...> - 2004-03-09 16:08:23
|
Hi, All, We have been using the wrapper for some win NT services. Recently we occasionally ran into some problem where the services consume almost all (99%, 100%) the CPU resources of a dual-CPU machine. The following is a segment of the wrapper log file: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D INFO | jvm 1 | 2004/02/18 06:31:25 | Send a packet 103 : ok DEBUG | wrapperp | 2004/02/18 06:31:25 | read a packet 103 : ok DEBUG | wrapper | 2004/02/18 06:31:25 | Got ping response from JVM DEBUG | wrapper | 2004/02/18 06:31:26 | ServiceControlHandler(4) DEBUG | wrapper | 2004/02/18 06:31:26 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapperp | 2004/02/18 06:31:31 | sent 6 bytes INFO | jvm 1 | 2004/02/18 06:31:31 | Received a packet 103 : ping INFO | jvm 1 | 2004/02/18 06:31:31 | Send a packet 103 : ok DEBUG | wrapperp | 2004/02/18 06:31:31 | read a packet 103 : ok DEBUG | wrapper | 2004/02/18 06:31:31 | Got ping response from JVM DEBUG | wrapperp | 2004/02/18 06:31:37 | sent 6 bytes DEBUG | wrapper | 2004/02/18 06:31:37 | ServiceControlHandler(4) Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : ping Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : ping 2004/02/18 06:31:37 | SERVICE_CONTROL_INTERROGATE STATUS | wrapper | 2004/02/18 10:38:00 | --> Wrapper Started as Service DEBUG | wrapperp | 2004/02/18 10:38:00 | server listening on port 17005. DEBUG | wrapper | 2004/02/18 10:38:00 | JVM was only running for -322562155 seconds leading to a failed restart count of 1. STATUS | wrapper | 2004/02/18 10:38:00 | Launching a JVM... =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D From which we can see that at 6:31:37 something went wrong. There are two lines in the log are exactly the same and the contents are sort of mixed. It should be something like: DEBUG | wrapper | 2004/02/18 | 06:31:37 | Received a packet 103 : ping Instead, it came out mixed as: Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : ping Dvm 1 | 20E0UG4/02 | 18 06wrapper | 31:37 | Received a packet 103 : ping The DEBUG and the date time were mixed. There was a 'B' in the 'DEBUG' missing. the 'J' for 'Jvm 1' was also missing. During that time, the service shown active in the windows service manager panel. But the actual service was hung.=20 It seems that there was something happening inside the wrapper native part. Have anyone ever got the similar situation like this? Could anyone suggest what was happening here? Thanks, --=20 http://www.fastmail.fm - And now for something completely different=85 |
|
From: Andreas W. <and...@em...> - 2004-03-09 10:43:42
|
<html><style>p {margin: 0px}</style><body bgcolor='#ffffff' style='font-size:9pt; font-family:Verdana; font-family: Verdana' ><P>Leif,</P><P>is there a chance (in the current version 3.0.5 or in a future one) to specifiy the starting directory for the wrapper from "outside" (e.g. via an environment variable).</P><P>I want to integrate with JBoss, but I don't want to copy the wrapper files to the jboss directories. Since the wrapper isn't able to use another starting directory other than the executable's (Windows) or the starting script's one (Unix), JBoss will not be able to start properly due to some relative paths when constructing its classpath from its config files.</P><P>TIA,<BR>Andreas</P></body></html>
|
|
From: Sal I. <sal...@vo...> - 2004-03-08 23:43:32
|
by default services run under the system account which does NOT have access
to the network.
you need to set the account for your service to a domained user.
the system account is different than the administrator account.
control panels | administrative tools | services | your service | right
click | properties | Log On
click "This account"
and enter an account/password that has access to //somemachine
i suggest that you start by using your username/password
-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of
Pat...@ae...
Sent: Monday, March 08, 2004 2:41 PM
To: wra...@li...
Subject: [Wrapper-user] Network File Access Problem
Hi,
I am attempting to write a program that accesses a file on different
machine.
In a simple standalone program, I can read the file fine. The following code
produces "file.exists() = true":
String logFilePath = "//somemachine/j2ee_home/myApp.log";
File file = new File(logFilePath);
System.out.println("file.exists() = " + file.exists() );
However when I run the same code inside the Java Service Wrapper, the output
is "file.exists() = false". For some reason I can't access the file.
Does anyone have any information on this problem?
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: <Pat...@ae...> - 2004-03-08 22:56:47
|
Hi,
I am attempting to write a program that accesses a file on different
machine.
In a simple standalone program, I can read the file fine. The following code
produces "file.exists() = true":
String logFilePath = "//somemachine/j2ee_home/myApp.log";
File file = new File(logFilePath);
System.out.println("file.exists() = " + file.exists() );
However when I run the same code inside the Java Service Wrapper, the output
is "file.exists() = false". For some reason I can't access the file.
Does anyone have any information on this problem?
|
|
From: Jennifer K. <jk...@si...> - 2004-03-08 19:29:25
|
I am not calling wrapper.stop anywhere.. I only call wrapper.restart(); I do have some places in the code that issue System.exit(0) or System.exit(1)...however, I have ignore system events set.... My one question here-- I remember reading that you said there was a problem w/ restarts after a system.exit(1).. and that you said that was fixed in your current checked in code.. I am running from a build I did of your code in CVS as of 3/1/04. I expect a System.exit(1) is being issued in these cases.. I will try converting that in my internal code to use an exit code of 0.. I had already made that change in the wrapperSimpleApp and saw no difference in behavior. is the system.exit(1) bug still lingering ?? thanks Jennifer On Mar 6, 2004, at 6:34 AM, Leif Mortenson wrote: > Jennifer, > Sorry to keep you waiting. Busy week. > > I tried this out and everything seems to be working correctly for > me. From your log > output, it looks like restart triggers get fired several times in > rapid succession. I tested > this and the Wrapper appears to be handling that correctly. Once the > restart has > started, additional restart requests are correctly ignored. > > I think the problem is the following lines from your output: > INFO | jvm 7 | 2004/02/26 19:32:59 | Send a packet STOP : 0 > DEBUG | wrapperp | 2004/02/26 19:32:59 | read a packet STOP : 0 > DEBUG | wrapper | 2004/02/26 19:32:59 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperStopProcess(0) called. > > Are you sure you are not calling System.exit or > WrapperManager.stop() someplace > in your code? If so that will override the restart request and cause > the Wrapper to > shutdown. > > If you call System.exit, you will get the following in your log > output. System.exit > triggers a Shutdown Hook, which you have disabled, so I don't think > this what is > happening: > > INFO | jvm 1 | main | 2004/03/06 23:27:15 | Wrapper Manager: > ShutdownHook started > INFO | jvm 1 | main | 2004/03/06 23:27:15 | Send a packet STOP > : 0 > DEBUG | wrapperp | main | 2004/03/06 23:27:15 | read a packet STOP > : 0 > DEBUG | wrapper | main | 2004/03/06 23:27:15 | JVM requested a > shutdown. (0) > DEBUG | wrapper | main | 2004/03/06 23:27:15 | > wrapperStopProcess(0) called. > DEBUG | wrapper | main | 2004/03/06 23:27:15 | Sending stop > signal to JVM > DEBUG | wrapperp | main | 2004/03/06 23:27:15 | send a packet STOP > : NULL > > A call you WrapperManager.stop(0) on the other hand, looks like the > following. This is > exactly what is showing up in your log: > > INFO | jvm 1 | main | 2004/03/06 23:29:06 | Send a packet STOP > : 0 > DEBUG | wrapperp | main | 2004/03/06 23:29:06 | read a packet STOP > : 0 > DEBUG | wrapper | main | 2004/03/06 23:29:06 | JVM requested a > shutdown. (0) > DEBUG | wrapper | main | 2004/03/06 23:29:06 | > wrapperStopProcess(0) called. > DEBUG | wrapper | main | 2004/03/06 23:29:06 | Sending stop > signal to JVM > DEBUG | wrapperp | main | 2004/03/06 23:29:06 | send a packet STOP > : NULL > > Let me know if you don't think that is the cause or have questions > about to use > the filters. > > Cheers, > Leif > > Jennifer Kolar wrote: > >> Leif, >> >> It appears that I never have a successful FILTER based restart. I >> have no problem getting restarts when I call WrapperManager.restart() >> internally.. however-- >> if there is an exception that I didn't catch that a filter matches, >> then I never get a successful restart. I have had each of the >> following filters triggered always with the same result. >> >> I noticed that there was a recent email (Patrick Woodworth 1/23/2004) >> where another person was having similiar problems and he found >> disabling the shutdown hooks to be a soln for him.. I've had that >> disabled this whole time and don't see any difference. >> >> >> Here are my filter settings from my conf file. >> >> >> wrapper.filter.trigger.1=com.singingfish.werkflow.processors.Processor >> Exception >> wrapper.filter.action.1=RESTART >> >> wrapper.filter.trigger.2=java.lang.Error >> wrapper.filter.action.2=RESTART >> >> wrapper.filter.trigger.3=java.lang.OutOfMemoryError >> wrapper.filter.action.3=RESTART >> >> >> I also have these set if it provides any help.. ( I have tried >> playing around w/ different startup timeouts and invocation times and >> it seems to make no difference) >> >> wrapper.jvm_exit.timeout=30 >> wrapper.cpu.timeout=10 >> wrapper.ping.timeout=300 >> wrapper.ping.interval=5 >> wrapper.restart.delay=1 >> wrapper.max_failed_invocations=3 >> wrapper.successful_invocation_time=10 >> wrapper.startup.timeout=30 >> wrapper.request_thread_dump_on_failed_jvm_exit=FALSE >> wrapper.ignore_signals=TRUE >> wrapper.disable_shutdown_hook=TRUE >> >> And again, here is the result I see whenever a filter is triggered: >> >> >> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched. >> Restarting JVM.* >> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess() >> called* >> ... (stuff from my stacktrack) >> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched. >> Restarting JVM.* >> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess() >> called. (IGNORED)* >> INFO | jvm 7 | 2004/02/26 19:32:59 | java.lang.Error: >> com.singingfish.werkflow.processors.ProcessorException: Unexpected >> exception in cracker >> *STATUS | wrapper | 2004/02/26 19:32:59 | Filter trigger matched. >> Restarting JVM.* >> *DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperRestartProcess() >> called. (IGNORED)* >> ... (stuff from my stack track) >> INFO | jvm 7 | 2004/02/26 19:32:59 | Send a packet STOP : 0 >> DEBUG | wrapperp | 2004/02/26 19:32:59 | read a packet STOP : 0 >> DEBUG | wrapper | 2004/02/26 19:32:59 | JVM requested a shutdown. >> (0) >> DEBUG | wrapper | 2004/02/26 19:32:59 | wrapperStopProcess(0) >> called. >> DEBUG | wrapper | 2004/02/26 19:32:59 | Sending stop signal to JVM >> DEBUG | wrapperp | 2004/02/26 19:32:59 | send a packet STOP : NULL >> INFO | jvm 7 | 2004/02/26 19:32:59 | Received a packet STOP : >> INFO | jvm 7 | 2004/02/26 19:33:00 | Thread, >> WrapperSimpleAppMain, handling the shutdown process. >> INFO | jvm 7 | 2004/02/26 19:33:00 | calling listener.stop() >> INFO | jvm 7 | 2004/02/26 19:33:00 | WrapperSimpleApp: stop(0) >> INFO | jvm 7 | 2004/02/26 19:33:00 | returned from >> listener.stop() >> INFO | jvm 7 | 2004/02/26 19:33:00 | Send a packet STOPPED : 0 >> DEBUG | wrapperp | 2004/02/26 19:33:00 | read a packet STOPPED : 0 >> DEBUG | wrapper | 2004/02/26 19:33:00 | JVM signalled that it was >> stopped. >> INFO | jvm 7 | 2004/02/26 19:33:00 | Closing socket. >> DEBUG | wrapperp | 2004/02/26 19:33:00 | socket read no code >> (closed?). >> INFO | jvm 7 | 2004/02/26 19:33:00 | calling System.exit(0) >> INFO | jvm 7 | 2004/02/26 19:33:00 | Server daemon shut down >> DEBUG | wrapper | 2004/02/26 19:33:00 | JVM exited normally. >> STATUS | wrapper | 2004/02/26 19:33:01 | <-- Wrapper Stopped >> STATUS | wrapper | 2004/02/26 19:36:28 | CrackerAgent3 removed. >> >> >> in comparison-- a normal restart has the following ... >> >> >> INFO | jvm 6 | 2004/02/26 19:31:48 | 2004-02-26 19:31:48,107 >> DEBUG [WrapperSimpleAppMain] WerkflowAgent - >> WerkflowEngine requested VM restart (null). Shutting down... >> INFO | jvm 6 | 2004/02/26 19:31:48 | Send a packet RESTART : >> restart >> DEBUG | wrapperp | 2004/02/26 19:31:48 | read a packet RESTART : >> restart >> STATUS | wrapper | 2004/02/26 19:31:48 | JVM requested a restart. >> DEBUG | wrapper | 2004/02/26 19:31:48 | wrapperRestartProcess() >> called. >> DEBUG | wrapper | 2004/02/26 19:31:48 | Sending stop signal to JVM >> DEBUG | wrapperp | 2004/02/26 19:31:48 | send a packet STOP : NULL >> INFO | jvm 6 | 2004/02/26 19:31:48 | Received a packet STOP : >> INFO | jvm 6 | 2004/02/26 19:31:49 | Thread, >> WrapperSimpleAppMain, handling the shutdown process. >> INFO | jvm 6 | 2004/02/26 19:31:49 | calling listener.stop() >> INFO | jvm 6 | 2004/02/26 19:31:49 | WrapperSimpleApp: stop(0) >> INFO | jvm 6 | 2004/02/26 19:31:49 | returned from >> listener.stop() >> INFO | jvm 6 | 2004/02/26 19:31:49 | Send a packet STOPPED : 0 >> DEBUG | wrapperp | 2004/02/26 19:31:49 | read a packet STOPPED : 0 >> DEBUG | wrapper | 2004/02/26 19:31:49 | JVM signalled that it was >> stopped. >> INFO | jvm 6 | 2004/02/26 19:31:49 | Closing socket. >> DEBUG | wrapperp | 2004/02/26 19:31:49 | socket read no code >> (closed?). >> INFO | jvm 6 | 2004/02/26 19:31:50 | calling System.exit(0) >> INFO | jvm 6 | 2004/02/26 19:31:50 | Server daemon shut down >> DEBUG | wrapper | 2004/02/26 19:31:50 | JVM exited normally. >> STATUS | wrapper | 2004/02/26 19:31:52 | Launching a JVM... >> DEBUG | wrapper | 2004/02/26 19:31:52 | command: >> "C:\WINNT\system32\java.exe" >> -Dcom.singingfish.core.utils.config.dir=c:/sf/config >> -Duser.dir=C:\aolrun -Dsun.rmi.loader.logLevel=VERBOSE >> -Dsun.rmi.server.logLevel=VERBOSE >> -Dsun.rmi.transport.logLevel=VERBOSE >> -Dsun.rmi.transport.tcp.logLevel=VERBOSE >> -Dsun.rmi.transport.proxy.logLevel=VERBOSE -Xms3m -Xmx96m >> -Djava.library.path="c:/sf/lib;c:/winnt;c:/winnt/system32;c:/ >> j2sdk1.4.2_02/bin" -classpath >> "c:/sf/java/classes;c:/sf/java/jars/commons-logging-1.0.3/commons- >> logging.jar;c:/sf/java/jars/jakarta-log4j-1.2.8/dist/lib/log4j >> -1.2.8.jar;c:/sf/java/jars/jakarta-oro-2.0.4/jakarta-oro-2.0.4.jar;c: >> /sf/java/jars/quicktime_6_5/QTJava.zip;c:/sf/java/jars/xerces-1_3_1/ >> xerces.jar;c:/sf/java/jars/toplink/TOPLink.jar;c:/sf/java/jars/ >> toplink/Tools.jar;c:/sf/java/jars/toplink/TOPLinkX.jar;c:/sf/java/ >> jars/oracle_jdbc_9_2_03/ojdbc14.jar;c:/sf/java/jars/commons- >> httpclient-2.0/commons-httpclient-2.0-final.jar" >> -Dwrapper.key="VRxfE5Fd856GSIaF" -Dwrapper.port=32013 >> -Dwrapper.debug="TRUE" -Dwrapper.ignore_signals="TRUE" >> -Dwrapper.service="TRUE" -Dwrapper.disable_shutdown_hook="TRUE" >> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=7 >> org.tanukisoftware.wrapper.WrapperSimpleApp >> com.singingfish.werkflow.agent.WerkflowAgent >> c:/sf/config/workflow/specs/cracker.spec CrackerAgent3 >> DEBUG | wrapper | 2004/02/26 19:31:52 | Java Virtual Machine >> started (PID=9244) >> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper Manager: JVM #7 >> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper Manager: Using >> wrapper >> INFO | jvm 7 | 2004/02/26 19:31:52 | Calling native >> initialization method. >> INFO | jvm 7 | 2004/02/26 19:31:52 | Initializing WrapperManager >> native library. >> INFO | jvm 7 | 2004/02/26 19:31:52 | Java Executable: >> C:\WINNT\system32\java.exe >> INFO | jvm 7 | 2004/02/26 19:31:52 | Java Version : >> 1.4.2_02-b03 Java HotSpot(TM) Client VM >> INFO | jvm 7 | 2004/02/26 19:31:52 | Java VM Vendor : Sun >> Microsystems Inc. >> INFO | jvm 7 | 2004/02/26 19:31:52 | >> INFO | jvm 7 | 2004/02/26 19:31:52 | Wrapper (Version 3.0.5) >> INFO | jvm 7 | 2004/02/26 19:31:52 | >> INFO | jvm 7 | 2004/02/26 19:31:52 | Open socket to wrapper >> attempted on port 32013... >> INFO | jvm 7 | 2004/02/26 19:31:52 | Opened Socket to port 3242 >> INFO | jvm 7 | 2004/02/26 19:31:52 | Send a packet KEY : >> VRxfE5Fd856GSIaF >> INFO | jvm 7 | 2004/02/26 19:31:52 | >> handleSocket(Socket[addr=/127.0.0.1,port=32013,localport=3242]) >> DEBUG | wrapperp | 2004/02/26 19:31:52 | accepted a socket from >> 127.0.0.1 on port 3242 >> DEBUG | wrapperp | 2004/02/26 19:31:52 | read a packet KEY : >> VRxfE5Fd856GSIaF >> DEBUG | wrapper | 2004/02/26 19:31:52 | Got key from JVM: >> VRxfE5Fd856GSIaF >> DEBUG | wrapperp | 2004/02/26 19:31:52 | send a packet LOW_LOG_LEVEL >> : 1 >> DEBUG | wrapperp | 2004/02/26 19:31:52 | send a packet PING_TIMEOUT >> : 300 >> DEBUG | wrapper | 2004/02/26 19:31:52 | Start Application. >> .... > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Richard E. <rem...@ed...> - 2004-03-08 16:31:51
|
Leif, see below. Richard Leif Mortenson wrote: > Richard, > >> Thank you for the explanation; the message: >> "JVM did not exit on request, terminated " >> refers to the fact that a previous request to stop the process >> failed and now it will be shutdown with a SIGKILL. >> >> We run load tests every night a multiple machine types. Every couple of >> days on one of our Linux boxes after running for a couple of hours >> we get the twin messages: >> >> JVM appears hung: Timed out waiting for signal from JVM. >> JVM did not exit on request, terminated >> >> one right after the other within milliseconds. >> >> The problem that arises after sending a SIGKILL to the process >> controlled by the wrapper is that that primary process has spawned >> secondary processes (not child processes) so that killing the primary >> with at SIGKILL does not kill the secondary process - shutdown hooks >> are registered but java will not execute them when a SIGKILL is received. >> >> In the file wrapper_unix.c in the function wrapperKillProcess() how >> about first signaling with at SIGTERM, wait a while and then a SIGKILL. >> That way the primary process' shutdown hook might run? > > > The Wrapper does not send a SIGTERM to the JVM, but it does attempt to > get the > JVM to shutdown cleanly. The wrapperKillProcess function is only > called when a > clean shutdown of the JVM has failed. At that point, the JVM is most > likely not > listening for SIGTERM or any other signals. The SIGKILL is a last > resort to get > rid of it. > > Most likely your application is frozen at this point which is why it had > not responded > to the exit requests. Looking through the code in wrapper.c, the message: "JVM appears hung: Timed out waiting for signal from JVM." is printed when the primary process has not responded to a ping. Immediately after this the function wrapperKillProcess() is called. As far as I can see there were no "exit requests" prior to the SIGKILL. Obviously, you are much more familiar than I am with the code, could you point out where a previous exit request was sent after the ping timeout so I can better understand the flow of control. Thanks. If there was no previous exit request, would there be any harm is first sending the process a SIGTERM followed (100 ms later or so) by a SIGKILL? As an aside, using the "unsupported" classes sun.misc.Signal and sun.misc.SignalHandler one can register signal handlers. At least on Linux using java 1.4.2_03 registering to catch TERM works but reqistering to catch KILL results in a nice core dump at the point of registration :-) > > If you are able to reproduce this so easily. Could you try turning on > debug output > with wrapper.debug=true and then letting that run until the JVM is > restarted? The > debug output will show exactly why the Wrapper decides that it is time > to kill the > JVM process. Most likely the JVM has stopped responding to ping requests. > > Cheers, > Leif > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2004-03-08 15:49:15
|
Richard, > Thank you for the explanation; the message: > "JVM did not exit on request, terminated " > refers to the fact that a previous request to stop the process > failed and now it will be shutdown with a SIGKILL. > > We run load tests every night a multiple machine types. Every couple of > days on one of our Linux boxes after running for a couple of hours > we get the twin messages: > > JVM appears hung: Timed out waiting for signal from JVM. > JVM did not exit on request, terminated > > one right after the other within milliseconds. > > The problem that arises after sending a SIGKILL to the process > controlled by the wrapper is that that primary process has spawned > secondary processes (not child processes) so that killing the primary > with at SIGKILL does not kill the secondary process - shutdown hooks > are registered but java will not execute them when a SIGKILL is received. > > In the file wrapper_unix.c in the function wrapperKillProcess() how > about first signaling with at SIGTERM, wait a while and then a SIGKILL. > That way the primary process' shutdown hook might run? The Wrapper does not send a SIGTERM to the JVM, but it does attempt to get the JVM to shutdown cleanly. The wrapperKillProcess function is only called when a clean shutdown of the JVM has failed. At that point, the JVM is most likely not listening for SIGTERM or any other signals. The SIGKILL is a last resort to get rid of it. Most likely your application is frozen at this point which is why it had not responded to the exit requests. If you are able to reproduce this so easily. Could you try turning on debug output with wrapper.debug=true and then letting that run until the JVM is restarted? The debug output will show exactly why the Wrapper decides that it is time to kill the JVM process. Most likely the JVM has stopped responding to ping requests. Cheers, Leif |
|
From: Richard E. <rem...@ed...> - 2004-03-08 15:30:41
|
Leif, Thank you for the explanation; the message: "JVM did not exit on request, terminated " refers to the fact that a previous request to stop the process failed and now it will be shutdown with a SIGKILL. We run load tests every night a multiple machine types. Every couple of days on one of our Linux boxes after running for a couple of hours we get the twin messages: JVM appears hung: Timed out waiting for signal from JVM. JVM did not exit on request, terminated one right after the other within milliseconds. The problem that arises after sending a SIGKILL to the process controlled by the wrapper is that that primary process has spawned secondary processes (not child processes) so that killing the primary with at SIGKILL does not kill the secondary process - shutdown hooks are registered but java will not execute them when a SIGKILL is received. In the file wrapper_unix.c in the function wrapperKillProcess() how about first signaling with at SIGTERM, wait a while and then a SIGKILL. That way the primary process' shutdown hook might run? Richard Leif Mortenson wrote: > Richard, > When are you seeing this message? Does it happen shortly after your > application > was launched (within 30 seconds) or after your app has been running for > a while? > > The first message "JVM appears hung: Timed out waiting for signal > from JVM." > is displayed when the Wrapper process first decides that there is a > problem with the > JVM. It then attempts to ask the JVM to shut itself down cleanly by > sending it a > stop command. This gives the JVM a chance to do any cleanup and shut > itself > down cleanly. > > If the JVM fails to shutdown on its own then the Wrapper will give up > and > forcibly kill it with a "kill -9". That is the message that you are > seeing: > "JVM did not exit on request, terminated " It is printed right after > the kill > command because at that point, the JVM has failed to exit. The kill > command > will always work because it is killing a child process. > > I assume that you digging into the code because you are having a > problem. > could you describe it? > > Cheers, > Leif > > Richard Emberson wrote: > >> I get the following in wrapper logs on linux (not windows or solaris): >> >> JVM appears hung: Timed out waiting for signal from JVM. >> JVM did not exit on request, terminated >> >> Looking through the code in wrapper_unix.c I see the following in the >> function wrapperKillProcess() : >> >> kill(jvmPid, SIGKILL); >> log_printf(WRAPPER_SOURCE_WRAPPER, LEVEL_ERROR, "JVM did not >> exit on request, terminated"); >> >> What does the message "JVM did not exit on request, terminated" mean? >> There is no test after the kill function is called to tell whether or >> not the JVM exited or not so how can one say that the JVM did not exit? >> >> Thanks. >> Richard > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2004-03-07 16:41:27
|
Shmul,
Ok, in that case. Currently, it is not possible to detect and log
that the JVM is
frozen and then not shut it down. You should be able to configure the
Wrapper so
that it never detects that the JVM is frozen however.
The Wrapper has the ability to detect a number of JVM failure
modes. The
freeze detection code works by sending pings to the JVM across a
socket. The
Wrapper then allows a configurable number of seconds for the JVM to
respond to
the ping. If that period ever times out then the Wrapper decides that
the JVM is
frozen and restarts it.
This timeout is configurable using the following property. A value
of 0 means
that the pings should never timeout and should be what you want.
wrapper.ping.timeout=0
If your app is hanging while it is starting up or shutting down then
other times
may need to be modified.
Your original message says that you had set the ping timeout to 0.
That was
not working for you? If not, try enabling debug output. I would need
that
information to help further.
Cheers,
Leif
Shmulik Regev wrote:
>>First of all 99% of the time. You do not want to be playing with the
>>timeouts. So start by removing those from your wrapper.conf file.
>>
>>I am making a wild guess here because you did not post much
>>information. But is your application timing out and shutting down
>>immediately after startup? This is usually caused because you
>>specified your application's main class directly in the wrapper.conf
>>file rather than using one of the helper classes like
>>WrapperSimpleApp. Make sure that you have read over the integration
>>section of the documentation. Most people make use of integration
>>method #1.
>>
>>
>
>Actually this is not the case for me. The application starts-up ok
>and the problem is surely not with the wrapper but with the
>application. What we see is that during stress testing (which we
>usually run at night, hence part of the problem), the jvm will not
>respond to pings and is shut down by the wrapper. The freeze of the
>jvm is probably caused by our own bug, however once the jvm is
>shutdown it is much harder for us to trace the cause of the problem.
>I would prefer to disable the shutting down of the jvm at least
>during development time to be able to get to the source of the
>application problem. It would actually be great if the wrapper would
>log the fact the the jvm doesn't respond, but will not terminate it.
>
>I'll also follow your advise regarding the timeout settings.
>
>Cheers,
>Shmul
>
>
|
|
From: Shmulik R. <sh...@vs...> - 2004-03-06 21:11:47
|
> First of all 99% of the time. You do not want to be playing with the > timeouts. So start by removing those from your wrapper.conf file. > > I am making a wild guess here because you did not post much > information. But is your application timing out and shutting down > immediately after startup? This is usually caused because you > specified your application's main class directly in the wrapper.conf > file rather than using one of the helper classes like > WrapperSimpleApp. Make sure that you have read over the integration > section of the documentation. Most people make use of integration > method #1. Actually this is not the case for me. The application starts-up ok and the problem is surely not with the wrapper but with the application. What we see is that during stress testing (which we usually run at night, hence part of the problem), the jvm will not respond to pings and is shut down by the wrapper. The freeze of the jvm is probably caused by our own bug, however once the jvm is shutdown it is much harder for us to trace the cause of the problem. I would prefer to disable the shutting down of the jvm at least during development time to be able to get to the source of the application problem. It would actually be great if the wrapper would log the fact the the jvm doesn't respond, but will not terminate it. I'll also follow your advise regarding the timeout settings. Cheers, Shmul |
|
From: Leif M. <le...@ta...> - 2004-03-06 15:09:08
|
Barney,
You got most of it figured out. But you still need to read through
the integration
documentation. The problem is that you specified your application's
main class as
the JVM main class. This is only possible if your application knows how
to initialize
the JVM side of the Wrapper. Most applications make use of the
WrapperSimpleApp or WrapperStartStartApp helper classes to do this for them.
Their usage is described in Integration Methods 1 and 2 in the docs.
Let me know if you have any questions after look through that
section of the docs.
Cheers,
Leif
bar...@on... wrote:
>Hi,
>
>I am having an Fileshareing server application in a jarfile.
>Now I wanted to run it as a service. I dont get it running with nohup in
>the background.
>Then I found wrapper ...
>
>I configured as discribed in the integration.
>As it is an JAR file application, that dont need any parameters (only
>config file) on startup, I found in the FAQ, that I need to look into
>the manifest.mf but I dont get it running.
>
>Below I pasted the LogOutputs with debug Infos.
>I hope someone can help me get it running
>
>Thx in advance
>Barney
>--------------------------------------------
>I have everything in the current directory:
><<<<<<<< script >>>>>>>>>
># Application
>APP_NAME="AJ_Server"
>APP_LONG_NAME="Applejuice Java Server"
>
># Wrapper
>WRAPPER_CMD="./wrapper"
>WRAPPER_CONF="./ajserver.conf"
>
># Priority at which to run the wrapper. See "man nice" for valid
>priorities.
># nice is only used if a priority is specified.
>PRIORITY=
>
># Location of the pid file.
>PIDDIR="/var/run"
>
><<<<<<<<< conf >>>>>>>>>>
># from META-INF/MANIFEST.MF
>wrapper.java.mainclass=de/applejuicenet/server/Daemon
>
>wrapper.java.classpath.1=./wrapper.jar
>wrapper.java.classpath.2=./ajserver.jar
>
>wrapper.java.library.path.1=./
>====================================
>
>Now I am getting the following in the logfile (debug on)
><<<<<<<< log >>>>>>>>>
>DEBUG | wrapper | 2004/03/05 16:22:58 | Spawning intermediate
>process...
>DEBUG | wrapper | 2004/03/05 16:22:58 | Spawning daemon process...
>STATUS | wrapper | 2004/03/05 16:22:58 | --> Wrapper Started as Daemon
>DEBUG | wrapperp | 2004/03/05 16:22:58 | server listening on port
>32000.
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[0] : java
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[1] : -Xms32m
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[2] : -Xmx128m
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[3] :
>-Djava.library.path=./
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[4] : -classpath
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[5] :
>./wrapper.jar:./ajserver.jar
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[6] :
>-Dwrapper.key=a_DbQegXe3TBBZN8
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[7] :
>-Dwrapper.port=32000
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[8] :
>-Dwrapper.debug=TRUE
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[9] :
>-Dwrapper.service=TRUE
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[10] :
>-Dwrapper.cpu.timeout=10
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[11] :
>-Dwrapper.jvmid=1
>DEBUG | wrapper | 2004/03/05 16:22:59 | Command[12] :
>de/applejuicenet/server/Daemon
>STATUS | wrapper | 2004/03/05 16:22:59 | Launching a JVM...
>INFO | jvm 1 | 2004/03/05 16:23:02 | 4:23:02 PM start server
>INFO | jvm 1 | 2004/03/05 16:23:04 | 4:23:04 PM timediff: 2170ms
>ERROR | wrapper | 2004/03/05 16:23:30 | Startup failed: Timed out
>waiting for signal from JVM.
>ERROR | wrapper | 2004/03/05 16:23:30 | JVM did not exit on request,
>terminated
>DEBUG | wrapper | 2004/03/05 16:23:30 | JVM was only running for 31
>seconds leading to a failed restart count of 1.
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[0] : java
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[1] : -Xms32m
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[2] : -Xmx128m
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[3] :
>-Djava.library.path=./
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[4] : -classpath
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[5] :
>./wrapper.jar:./ajserver.jar
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[6] :
>-Dwrapper.key=mi_bxg8Mj1mV092R
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[7] :
>-Dwrapper.port=32000
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[8] :
>-Dwrapper.debug=TRUE
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[9] :
>-Dwrapper.service=TRUE
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[10] :
>-Dwrapper.cpu.timeout=10
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[11] :
>-Dwrapper.jvmid=2
>DEBUG | wrapper | 2004/03/05 16:23:36 | Command[12] :
>de/applejuicenet/server/Daemon
>STATUS | wrapper | 2004/03/05 16:23:36 | Launching a JVM...
>INFO | jvm 2 | 2004/03/05 16:23:39 | 4:23:39 PM start server
>INFO | jvm 2 | 2004/03/05 16:23:41 | 4:23:41 PM timediff: 39220ms
>INFO | jvm 2 | 2004/03/05 16:24:00 | 4:24:00 PM check IP
>INFO | jvm 2 | 2004/03/05 16:24:00 | 4:24:00 PM serverip:
>80.134.23.111
>INFO | jvm 2 | 2004/03/05 16:24:01 | java.lang.NullPointerException
>INFO | jvm 2 | 2004/03/05 16:24:01 | at
>de.applejuicenet.server.Daemon.cancel(TRUX)
>INFO | jvm 2 | 2004/03/05 16:24:01 | at
>de.applejuicenet.server.Daemon.main(TRUX)
>INFO | jvm 2 | 2004/03/05 16:24:01 | 4:24:01 PM shutdown server
>ERROR | wrapper | 2004/03/05 16:24:07 | Startup failed: Timed out
>waiting for signal from JVM.
>ERROR | wrapper | 2004/03/05 16:24:07 | JVM did not exit on request,
>terminated
>DEBUG | wrapper | 2004/03/05 16:24:07 | JVM was only running for 31
>seconds leading to a failed restart count of 2.
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[0] : java
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[1] : -Xms32m
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[2] : -Xmx128m
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[3] :
>-Djava.library.path=./
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[4] : -classpath
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[5] :
>./wrapper.jar:./ajserver.jar
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[6] :
>-Dwrapper.key=fCWMT4xc5U6639Xa
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[7] :
>-Dwrapper.port=32000
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[8] :
>-Dwrapper.debug=TRUE
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[9] :
>-Dwrapper.service=TRUE
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[10] :
>-Dwrapper.cpu.timeout=10
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[11] :
>-Dwrapper.jvmid=3
>DEBUG | wrapper | 2004/03/05 16:24:13 | Command[12] :
>de/applejuicenet/server/Daemon
>STATUS | wrapper | 2004/03/05 16:24:13 | Launching a JVM...
>INFO | jvm 3 | 2004/03/05 16:24:16 | 4:24:16 PM start server
>INFO | jvm 3 | 2004/03/05 16:24:21 | 4:24:21 PM timediff: 20647ms
>INFO | jvm 3 | 2004/03/05 16:24:30 | 4:24:30 PM check IP
>INFO | jvm 3 | 2004/03/05 16:24:30 | 4:24:30 PM serverip:
>80.134.23.111
>INFO | jvm 3 | 2004/03/05 16:24:31 | java.lang.NullPointerException
>INFO | jvm 3 | 2004/03/05 16:24:31 | at
>de.applejuicenet.server.Daemon.cancel(TRUX)
>INFO | jvm 3 | 2004/03/05 16:24:31 | at
>de.applejuicenet.server.Daemon.main(TRUX)
>INFO | jvm 3 | 2004/03/05 16:24:31 | 4:24:31 PM shutdown server
>ERROR | wrapper | 2004/03/05 16:24:44 | Startup failed: Timed out
>waiting for signal from JVM.
>ERROR | wrapper | 2004/03/05 16:24:44 | JVM did not exit on request,
>terminated
>DEBUG | wrapper | 2004/03/05 16:24:44 | JVM was only running for 31
>seconds leading to a failed restart count of 3.
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[0] : java
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[1] : -Xms32m
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[2] : -Xmx128m
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[3] :
>-Djava.library.path=./
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[4] : -classpath
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[5] :
>./wrapper.jar:./ajserver.jar
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[6] :
>-Dwrapper.key=FBbxFJJLDQRGZORT
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[7] :
>-Dwrapper.port=32000
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[8] :
>-Dwrapper.debug=TRUE
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[9] :
>-Dwrapper.service=TRUE
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[10] :
>-Dwrapper.cpu.timeout=10
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[11] :
>-Dwrapper.jvmid=4
>DEBUG | wrapper | 2004/03/05 16:24:50 | Command[12] :
>de/applejuicenet/server/Daemon
>STATUS | wrapper | 2004/03/05 16:24:50 | Launching a JVM...
>INFO | jvm 4 | 2004/03/05 16:24:53 | 4:24:53 PM start server
>INFO | jvm 4 | 2004/03/05 16:24:55 | 4:24:55 PM timediff: 53168ms
>INFO | jvm 4 | 2004/03/05 16:25:03 | 4:25:03 PM check IP
>INFO | jvm 4 | 2004/03/05 16:25:03 | 4:25:03 PM serverip:
>80.134.23.111
>INFO | jvm 4 | 2004/03/05 16:25:04 | java.lang.NullPointerException
>INFO | jvm 4 | 2004/03/05 16:25:04 | at
>de.applejuicenet.server.Daemon.cancel(TRUX)
>INFO | jvm 4 | 2004/03/05 16:25:04 | at
>de.applejuicenet.server.Daemon.main(TRUX)
>INFO | jvm 4 | 2004/03/05 16:25:04 | 4:25:04 PM shutdown server
>ERROR | wrapper | 2004/03/05 16:25:21 | Startup failed: Timed out
>waiting for signal from JVM.
>ERROR | wrapper | 2004/03/05 16:25:21 | JVM did not exit on request,
>terminated
>DEBUG | wrapper | 2004/03/05 16:25:21 | JVM was only running for 31
>seconds leading to a failed restart count of 4.
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[0] : java
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[1] : -Xms32m
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[2] : -Xmx128m
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[3] :
>-Djava.library.path=./
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[4] : -classpath
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[5] :
>./wrapper.jar:./ajserver.jar
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[6] :
>-Dwrapper.key=_dQEXzpzogfm35fb
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[7] :
>-Dwrapper.port=32000
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[8] :
>-Dwrapper.debug=TRUE
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[9] :
>-Dwrapper.service=TRUE
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[10] :
>-Dwrapper.cpu.timeout=10
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[11] :
>-Dwrapper.jvmid=5
>DEBUG | wrapper | 2004/03/05 16:25:27 | Command[12] :
>de/applejuicenet/server/Daemon
>STATUS | wrapper | 2004/03/05 16:25:27 | Launching a JVM...
>INFO | jvm 5 | 2004/03/05 16:25:30 | 4:25:30 PM start server
>INFO | jvm 5 | 2004/03/05 16:25:35 | 4:25:35 PM timediff: 34645ms
>INFO | jvm 5 | 2004/03/05 16:25:47 | 4:25:47 PM check IP
>INFO | jvm 5 | 2004/03/05 16:25:47 | 4:25:47 PM serverip:
>80.134.23.111
>INFO | jvm 5 | 2004/03/05 16:25:48 | java.lang.NullPointerException
>INFO | jvm 5 | 2004/03/05 16:25:48 | at
>de.applejuicenet.server.Daemon.cancel(TRUX)
>INFO | jvm 5 | 2004/03/05 16:25:48 | at
>de.applejuicenet.server.Daemon.main(TRUX)
>INFO | jvm 5 | 2004/03/05 16:25:48 | 4:25:48 PM shutdown server
>ERROR | wrapper | 2004/03/05 16:25:58 | Startup failed: Timed out
>waiting for signal from JVM.
>ERROR | wrapper | 2004/03/05 16:25:58 | JVM did not exit on request,
>terminated
>DEBUG | wrapper | 2004/03/05 16:25:58 | JVM was only running for 31
>seconds leading to a failed restart count of 5.
>FATAL | wrapper | 2004/03/05 16:25:58 | There were 5 failed launches
>in a row, each lasting less than 300 seconds. Giving up.
>FATAL | wrapper | 2004/03/05 16:25:58 | There may be a configuration
>problem: please check the logs.
>STATUS | wrapper | 2004/03/05 16:25:59 | <-- Wrapper Stopped
>
>
|
165 messages has been excluded from this view by a project administrator.
