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: <sg...@gm...> - 2010-04-30 14:45:53
|
Thanks to this [1] thread I set +x on the .so file and it worked. You should really mention the executable bit in the troubleshooting guide. [1] http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1272638500999+28353475&threadId=1210531 Mike -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 |
|
From: <sg...@gm...> - 2010-04-30 14:32:51
|
Hi, I am trying to integrate the wrapper with Nexus [1]. Nexus already delivers JSW support but lacks HP-UX. I downloaded the wrapper and tried to start the wrapping shell script. It fails with the attached log file. IA32 fails completely because it can't locate the so files. I guess there is a bug in the 64 bit binary. How can I resolve this issue? [1] http://nexus.sonatype.org/ -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 |
|
From: Leif M. <le...@ta...> - 2010-04-30 07:30:34
|
Mark, Sorry for the trouble on this. Extending the wrapper.ping.timeout to a value longer than the JVM is going without CPU should do the trick. If it is still being terminated after 30 minutes (1800 sec) then most likely the JVM is being 100% starved of CPU for even longer. What is the memory situation on this system? Normally processes to do not take 100% of CPU quite so completely. The exception is when there is massive amounts of disk swapping going on. Java gets VERY VERY slow when this happens. On the order of 1/1000th speed in many cases. It is strange that the Wrapper is not restarting your JVM after it has been terminated however: --- ERROR | wrapper | 2010/04/25 17:18:32 | JVM did not exit on request, terminated STATUS | wrapper | 2010/04/25 17:18:37 | Launching a JVM... INFO | jvm 2 | 2010/04/25 17:18:37 | WrapperManager: Initializing... STATUS | wrapper | 2010/04/25 17:18:40 | <-- Wrapper Stopped --- Would it be possible for you to set the wrapper.debug=true property and let this happen once more so I can take a look at the detailed wrapper.log and see what is happening? Feel free to send that to me directly as it would be be a bit large for the list. If the system is very heavy still after being restarted, it may be necessary to also set the startup timeout so that the JVM has time to be launched. wrapper.startup.timeout=600 Cheers, Leif On Tue, Apr 27, 2010 at 4:34 AM, Ludwig, Mark <mar...@us...> wrote: > Recently I started having trouble with wrapper services going down in a > couple of scenarios. Here’s the first scenario. > > I have a machine (a partition or virtual server actually) with about a dozen > Eclipse infocenters set up with wrappers so that they can be stopped, > started, or left running as Windows services. A couple of months ago, after > many months of pretty much error-free operation, several of the services > would go down. I would have to end the javaw.exe process for the service > that went down and then I could restart the service. > > I eventually figured out that the virus scan update program was hogging the > CPU for up to 20 or 30 minutes each day. The IT folks tweaked the scheduling > and config of the virus scan update some and then I added in the following > parameters for each service. This has greatly reduced the number of times > the services go down, but it still happens (one service goes down every 2 or > 3 days instead of 3 or 4 services going down every day): > > wrapper.ping.timeout=1800 > > wrapper.ping.interval=10 > > I also tried changing the logging levels to get more detail. Unfortunately, > I could never get the services to crash when the logging was at TRACE and I > didn’t want to worry about the log files getting bigger and bigger. > Occasionally I would see a reference to Service Control Code 4. > > Log files have things like the following when the service goes down: > > ERROR | wrapper | 2010/04/25 17:18:31 | JVM appears hung: Timed out > waiting for signal from JVM. > > ERROR | wrapper | 2010/04/25 17:18:32 | JVM did not exit on request, > terminated > > STATUS | wrapper | 2010/04/25 17:18:37 | Launching a JVM... > > INFO | jvm 2 | 2010/04/25 17:18:37 | WrapperManager: Initializing... > > STATUS | wrapper | 2010/04/25 17:18:40 | <-- Wrapper Stopped > > > > So my questions at this point are the following: > > What would be the best possibilities for configuration parameters in an > occasional CPU starvation scenario? > > What would be the best parameters to set to get troubleshooting info? > > Would it help to upgrade to newer wrapper (I’m on 3.3.1)? > > > > Other basic info: > > Windows 2003 server > > One processor > > 2 GB RAM > > Server is set up with a 10GB C: drive (2 GB free) and a 30GB E: drive (10 GB > free). All the files for the infocenters are on the E: drive. > > > > Sample config file for one of the wrapper services: > > Recently I started having trouble with wrapper services going down in a > couple of scenarios. Here’s the first scenario. > > I have a machine (a partition or virtual server actually) with about a dozen > Eclipse infocenters set up with wrappers so that they can be stopped, > started, or left running as Windows services. A couple of months ago, after > many months of pretty much error-free operation, several of the services > would go down. I would have to end the javaw.exe process for the service > that went down and then I could restart the service. > > I eventually figured out that the virus update program was hogging the CPU > for up to 20 or 30 minutes each day. The IT folks tweaked the scheduling of > the update some and then I added in the following parameters for each > service, which has greatly reduced the number of times the services go down, > but it still happens (one service goes down every 2 or 3 days instead of 3 > or 4 services going down every day): > > wrapper.ping.timeout=1800 > > wrapper.ping.interval=10 > > I also tried changing the logging levels to get more detail. Unfortunately, > I could never get the services to crash when the logging was at TRACE and I > didn’t want to worry about the log files getting bigger and bigger. > Occasionally I would see a reference to Service Control Code 4. > > Log files have things like the following when the service goes down: > > ERROR | wrapper | 2010/04/25 17:18:31 | JVM appears hung: Timed out > waiting for signal from JVM. > > ERROR | wrapper | 2010/04/25 17:18:32 | JVM did not exit on request, > terminated > > STATUS | wrapper | 2010/04/25 17:18:37 | Launching a JVM... > > INFO | jvm 2 | 2010/04/25 17:18:37 | WrapperManager: Initializing... > > STATUS | wrapper | 2010/04/25 17:18:40 | <-- Wrapper Stopped > > > > So my questions at this point are the following: > > What would be the best possibilities for configuration parameters in an > occasional CPU starvation scenario? > > What would be the best parameters to set to get troubleshooting info? > > Would it help to upgrade to newer wrapper (I’m on 3.3.1)? > > > > Other basic info: > > Windows 2003 server > > One processor > > 2 GB RAM > > Server is set up with a 10GB C: drive (2 GB free) and a 30GB E: drive (10 GB > free). All the files for the infocenters are on the E: drive. > > > > Sample config file for one of the wrapper services: > > Recently I started having trouble with wrapper services going down in a > couple of scenarios. Here’s the first scenario. > > I have a machine (a partition or virtual server actually) with about a dozen > Eclipse infocenters set up with wrappers so that they can be stopped, > started, or left running as Windows services. A couple of months ago, after > many months of pretty much error-free operation, several of the services > would go down. I would have to end the javaw.exe process for the service > that went down and then I could restart the service. > > I eventually figured out that the virus update program was hogging the CPU > for up to 20 or 30 minutes each day. The IT folks tweaked the scheduling of > the update some and then I added in the following parameters for each > service, which has greatly reduced the number of times the services go down, > but it still happens (one service goes down every 2 or 3 days instead of 3 > or 4 services going down every day): > > wrapper.ping.timeout=1800 > > wrapper.ping.interval=10 > > I also tried changing the logging levels to get more detail. Unfortunately, > I could never get the services to crash when the logging was at TRACE and I > didn’t want to worry about the log files getting bigger and bigger. > Occasionally I would see a reference to Service Control Code 4. > > Log files have things like the following when the service goes down: > > ERROR | wrapper | 2010/04/25 17:18:31 | JVM appears hung: Timed out > waiting for signal from JVM. > > ERROR | wrapper | 2010/04/25 17:18:32 | JVM did not exit on request, > terminated > > STATUS | wrapper | 2010/04/25 17:18:37 | Launching a JVM... > > INFO | jvm 2 | 2010/04/25 17:18:37 | WrapperManager: Initializing... > > STATUS | wrapper | 2010/04/25 17:18:40 | <-- Wrapper Stopped > > > > So my questions at this point are the following: > > What would be the best possibilities for configuration parameters in an > occasional CPU starvation scenario? > > What would be the best parameters to set to get troubleshooting info? > > Would it help to upgrade to newer wrapper (I’m on 3.3.1)? > > > > Other basic info: > > Windows 2003 server > > One processor > > 2 GB RAM > > Server is set up with a 10GB C: drive (2 GB free) and a 30GB E: drive (10 GB > free). All the files for the infocenters are on the E: drive. > > Sample config file for one of the wrapper services: > > wrapper.java.command=java > > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > > wrapper.java.classpath.1=../lib/wrapper.jar > > wrapper.java.classpath.2=E:/eclipse/plugins/org.eclipse.help.base_*.jar > > wrapper.java.library.path.1=../lib > > wrapper.port=32000 > > wrapper.app.parameter.1=org.eclipse.help.standalone.Infocenter > > wrapper.app.parameter.2=-command > > wrapper.app.parameter.3=start > > wrapper.app.parameter.4=-eclipsehome > > wrapper.app.parameter.5=E:/eclipse > > wrapper.app.parameter.6=-port > > wrapper.app.parameter.7=7121 > > wrapper.app.parameter.8=-noexec > > wrapper.app.parameter.9=-data > > wrapper.app.parameter.10=E:/infocenter/7120_7129_LmrkLibrary/7121_LmrkWinSQL/infocenter > > wrapper.app.parameter.11=-product > > wrapper.app.parameter.12=com.lawson.help.brand.branding > > wrapper.app.parameter.13=-configuration > > wrapper.app.parameter.14=E:/infocenter/7120_7129_LmrkLibrary/7121_LmrkWinSQL/configuration > > > > #******************************************************************** > > # Wrapper Logging Properties > > #******************************************************************** > > wrapper.console.format=PM > > wrapper.console.loglevel=INFO > > > > wrapper.logfile=../logs/LmrkWinSQL.log > > wrapper.logfile.format=LPTM > > wrapper.logfile.loglevel=INFO > > wrapper.logfile.maxsize=0 > > wrapper.logfile.maxfiles=0 > > # Log Level for sys/event log output. (See docs for log levels) > > wrapper.syslog.loglevel=NONE > > wrapper.ping.timeout=30 > > wrapper.ping.interval=10 > > #******************************************************************** > > # Wrapper Windows Properties > > #******************************************************************** > > wrapper.console.title=Test Wrapper Sample Application > > #******************************************************************** > > # Wrapper Windows NT/2000/XP Service Properties > > #******************************************************************** > > wrapper.ntservice.name=LmrkWinSQL > > wrapper.ntservice.displayname=Infocenter - LmrkWinSQL > > wrapper.ntservice.description=Infocenter for Landmark Library for Windows/MS > SQL > > wrapper.ntservice.dependency.1= > > wrapper.ntservice.starttype=AUTO_START > > wrapper.ntservice.interactive=false -- Leif Mortenson Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com lei...@ta... |
|
From: Ludwig, M. <mar...@us...> - 2010-04-26 19:50:04
|
Recently I started having trouble with wrapper services going down in a couple of scenarios. Here's the first scenario. I have a machine (a partition or virtual server actually) with about a dozen Eclipse infocenters set up with wrappers so that they can be stopped, started, or left running as Windows services. A couple of months ago, after many months of pretty much error-free operation, several of the services would go down. I would have to end the javaw.exe process for the service that went down and then I could restart the service. I eventually figured out that the virus scan update program was hogging the CPU for up to 20 or 30 minutes each day. The IT folks tweaked the scheduling and config of the virus scan update some and then I added in the following parameters for each service. This has greatly reduced the number of times the services go down, but it still happens (one service goes down every 2 or 3 days instead of 3 or 4 services going down every day): wrapper.ping.timeout=1800 wrapper.ping.interval=10 I also tried changing the logging levels to get more detail. Unfortunately, I could never get the services to crash when the logging was at TRACE and I didn't want to worry about the log files getting bigger and bigger. Occasionally I would see a reference to Service Control Code 4. Log files have things like the following when the service goes down: ERROR | wrapper | 2010/04/25 17:18:31 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2010/04/25 17:18:32 | JVM did not exit on request, terminated STATUS | wrapper | 2010/04/25 17:18:37 | Launching a JVM... INFO | jvm 2 | 2010/04/25 17:18:37 | WrapperManager: Initializing... STATUS | wrapper | 2010/04/25 17:18:40 | <-- Wrapper Stopped So my questions at this point are the following: What would be the best possibilities for configuration parameters in an occasional CPU starvation scenario? What would be the best parameters to set to get troubleshooting info? Would it help to upgrade to newer wrapper (I'm on 3.3.1)? Other basic info: Windows 2003 server One processor 2 GB RAM Server is set up with a 10GB C: drive (2 GB free) and a 30GB E: drive (10 GB free). All the files for the infocenters are on the E: drive. Sample config file for one of the wrapper services: Recently I started having trouble with wrapper services going down in a couple of scenarios. Here's the first scenario. I have a machine (a partition or virtual server actually) with about a dozen Eclipse infocenters set up with wrappers so that they can be stopped, started, or left running as Windows services. A couple of months ago, after many months of pretty much error-free operation, several of the services would go down. I would have to end the javaw.exe process for the service that went down and then I could restart the service. I eventually figured out that the virus update program was hogging the CPU for up to 20 or 30 minutes each day. The IT folks tweaked the scheduling of the update some and then I added in the following parameters for each service, which has greatly reduced the number of times the services go down, but it still happens (one service goes down every 2 or 3 days instead of 3 or 4 services going down every day): wrapper.ping.timeout=1800 wrapper.ping.interval=10 I also tried changing the logging levels to get more detail. Unfortunately, I could never get the services to crash when the logging was at TRACE and I didn't want to worry about the log files getting bigger and bigger. Occasionally I would see a reference to Service Control Code 4. Log files have things like the following when the service goes down: ERROR | wrapper | 2010/04/25 17:18:31 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2010/04/25 17:18:32 | JVM did not exit on request, terminated STATUS | wrapper | 2010/04/25 17:18:37 | Launching a JVM... INFO | jvm 2 | 2010/04/25 17:18:37 | WrapperManager: Initializing... STATUS | wrapper | 2010/04/25 17:18:40 | <-- Wrapper Stopped So my questions at this point are the following: What would be the best possibilities for configuration parameters in an occasional CPU starvation scenario? What would be the best parameters to set to get troubleshooting info? Would it help to upgrade to newer wrapper (I'm on 3.3.1)? Other basic info: Windows 2003 server One processor 2 GB RAM Server is set up with a 10GB C: drive (2 GB free) and a 30GB E: drive (10 GB free). All the files for the infocenters are on the E: drive. Sample config file for one of the wrapper services: Recently I started having trouble with wrapper services going down in a couple of scenarios. Here's the first scenario. I have a machine (a partition or virtual server actually) with about a dozen Eclipse infocenters set up with wrappers so that they can be stopped, started, or left running as Windows services. A couple of months ago, after many months of pretty much error-free operation, several of the services would go down. I would have to end the javaw.exe process for the service that went down and then I could restart the service. I eventually figured out that the virus update program was hogging the CPU for up to 20 or 30 minutes each day. The IT folks tweaked the scheduling of the update some and then I added in the following parameters for each service, which has greatly reduced the number of times the services go down, but it still happens (one service goes down every 2 or 3 days instead of 3 or 4 services going down every day): wrapper.ping.timeout=1800 wrapper.ping.interval=10 I also tried changing the logging levels to get more detail. Unfortunately, I could never get the services to crash when the logging was at TRACE and I didn't want to worry about the log files getting bigger and bigger. Occasionally I would see a reference to Service Control Code 4. Log files have things like the following when the service goes down: ERROR | wrapper | 2010/04/25 17:18:31 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2010/04/25 17:18:32 | JVM did not exit on request, terminated STATUS | wrapper | 2010/04/25 17:18:37 | Launching a JVM... INFO | jvm 2 | 2010/04/25 17:18:37 | WrapperManager: Initializing... STATUS | wrapper | 2010/04/25 17:18:40 | <-- Wrapper Stopped So my questions at this point are the following: What would be the best possibilities for configuration parameters in an occasional CPU starvation scenario? What would be the best parameters to set to get troubleshooting info? Would it help to upgrade to newer wrapper (I'm on 3.3.1)? Other basic info: Windows 2003 server One processor 2 GB RAM Server is set up with a 10GB C: drive (2 GB free) and a 30GB E: drive (10 GB free). All the files for the infocenters are on the E: drive. Sample config file for one of the wrapper services: wrapper.java.command=java wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp wrapper.java.classpath.1=../lib/wrapper.jar wrapper.java.classpath.2=E:/eclipse/plugins/org.eclipse.help.base_*.jar wrapper.java.library.path.1=../lib wrapper.port=32000 wrapper.app.parameter.1=org.eclipse.help.standalone.Infocenter wrapper.app.parameter.2=-command wrapper.app.parameter.3=start wrapper.app.parameter.4=-eclipsehome wrapper.app.parameter.5=E:/eclipse wrapper.app.parameter.6=-port wrapper.app.parameter.7=7121 wrapper.app.parameter.8=-noexec wrapper.app.parameter.9=-data wrapper.app.parameter.10=E:/infocenter/7120_7129_LmrkLibrary/7121_LmrkWinSQL/infocenter wrapper.app.parameter.11=-product wrapper.app.parameter.12=com.lawson.help.brand.branding wrapper.app.parameter.13=-configuration wrapper.app.parameter.14=E:/infocenter/7120_7129_LmrkLibrary/7121_LmrkWinSQL/configuration #******************************************************************** # Wrapper Logging Properties #******************************************************************** wrapper.console.format=PM wrapper.console.loglevel=INFO wrapper.logfile=../logs/LmrkWinSQL.log wrapper.logfile.format=LPTM wrapper.logfile.loglevel=INFO wrapper.logfile.maxsize=0 wrapper.logfile.maxfiles=0 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=NONE wrapper.ping.timeout=30 wrapper.ping.interval=10 #******************************************************************** # Wrapper Windows Properties #******************************************************************** wrapper.console.title=Test Wrapper Sample Application #******************************************************************** # Wrapper Windows NT/2000/XP Service Properties #******************************************************************** wrapper.ntservice.name=LmrkWinSQL wrapper.ntservice.displayname=Infocenter - LmrkWinSQL wrapper.ntservice.description=Infocenter for Landmark Library for Windows/MS SQL wrapper.ntservice.dependency.1= wrapper.ntservice.starttype=AUTO_START wrapper.ntservice.interactive=false |
|
From: Tomer B <tom...@gm...> - 2010-04-25 11:51:30
|
Hi with the following configuration the error happened only a few minutes from startup: bash-3.00# cat server.conf #******************************************************************** # Wrapper License Properties (Ignored by Community Edition) #******************************************************************** # Include file problems can be debugged by removing the first '#' # from the following line: #******************************************************************** # Wrapper Java Properties #******************************************************************** # Java Application wrapper.java.mainclass=com.test.javavmtester.JavaVMTester wrapper.java.command=/bin/java wrapper.java.additional.auto_bits=TRUE # Tell the Wrapper to log the full generated Java command line. #wrapper.java.command.loglevel=DEBUG # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=./wrappertest.jar wrapper.java.classpath.2=./wrapper.jar wrapper.java.classpath.3=./ # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=. # Java Bits. On applicable platforms, tells the JVM to run in 32 or 64-bit mode. wrapper.java.additional.auto_bits=TRUE # Java Additional Parameters #wrapper.java.additional.1= # Initial Java Heap Size (in MB) wrapper.java.initmemory=1000 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=2000 # Application parameters. Add parameters as needed starting from 1 #wrapper.app.parameter.1= #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Enables Debug output from the Wrapper. # wrapper.debug=TRUE # Format of output for the console. (See docs for formats) wrapper.console.format=PM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=DEBUG # Log file to use for wrapper output logging. wrapper.logfile=./server-wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=DEBUG # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m = 10 megabytes. wrapper.logfile.maxsize=0 # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=0 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=NONE #******************************************************************** # Wrapper General Properties #******************************************************************** # Allow for the use of non-contiguous numbered properties wrapper.ignore_sequence_gaps=TRUE # Title to use when running as a console wrapper.console.title=Test Wrapper Sample Application #******************************************************************** # Wrapper Windows NT/2000/XP Service Properties #******************************************************************** # WARNING - Do not modify any of these properties when an application # using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The # service can then be reinstalled. # Name of the service wrapper.name=testwrapper # Display name of the service wrapper.displayname=Test Wrapper Sample Application # Description of the service wrapper.description=Test Wrapper Sample Application Description # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1= # Mode in which the service is installed. AUTO_START, DELAY_START or DEMAND_START wrapper.ntservice.starttype=AUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=false DEBUG | wrapper | 2010/04/25 14:31:21 | Spawning intermediate process... DEBUG | wrapper | 2010/04/25 14:31:21 | Spawning daemon process... DEBUG | wrapper | 2010/04/25 14:31:21 | Reloading configuration after daemonization. STATUS | wrapper | 2010/04/25 14:31:21 | --> Wrapper Started as Daemon STATUS | wrapper | 2010/04/25 14:31:21 | Java Service Wrapper Community Edition 64-bit 3.4.0 STATUS | wrapper | 2010/04/25 14:31:21 | Copyright (C) 1999-2010 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2010/04/25 14:31:21 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2010/04/25 14:31:21 | DEBUG | wrapper | 2010/04/25 14:31:21 | Release time: 2010/03/16 00:00:00 DEBUG | wrapper | 2010/04/25 14:31:21 | Build time: 2010/03/15 14:49:00 DEBUG | wrapper | 2010/04/25 14:31:21 | Timezone: IST (IDT) Offset: -7200, hasDaylight: 1 DEBUG | wrapper | 2010/04/25 14:31:21 | Using tick timer. DEBUG | wrapper | 2010/04/25 14:31:21 | active log file changed: ./server-wrapper.log DEBUG | wrapper | 2010/04/25 14:31:21 | active log file changed: ./server-wrapper.log DEBUG | wrapperp | 2010/04/25 14:31:22 | server listening on port 32000. DEBUG | wrapper | 2010/04/25 14:31:22 | Classpath element, wrapper.java.classpath.1, does not exist: ./wrappertest.jar DEBUG | wrapper | 2010/04/25 14:31:22 | Command[0] : /usr/jdk/instances/jdk1.6.0/bin/java DEBUG | wrapper | 2010/04/25 14:31:22 | Command[1] : -d64 DEBUG | wrapper | 2010/04/25 14:31:22 | Command[2] : -Xms1000m DEBUG | wrapper | 2010/04/25 14:31:22 | Command[3] : -Xmx2000m DEBUG | wrapper | 2010/04/25 14:31:22 | Command[4] : -Djava.library.path=. DEBUG | wrapper | 2010/04/25 14:31:22 | Command[5] : -classpath DEBUG | wrapper | 2010/04/25 14:31:22 | Command[6] : ./wrappertest.jar:./wrapper.jar:./ DEBUG | wrapper | 2010/04/25 14:31:22 | Command[7] : -Dwrapper.key=TYfJjxJ4jF0-5YDu DEBUG | wrapper | 2010/04/25 14:31:22 | Command[8] : -Dwrapper.port=32000 DEBUG | wrapper | 2010/04/25 14:31:22 | Command[9] : -Dwrapper.jvm.port.min=31000 DEBUG | wrapper | 2010/04/25 14:31:22 | Command[10] : -Dwrapper.jvm.port.max=31999 DEBUG | wrapper | 2010/04/25 14:31:22 | Command[11] : -Dwrapper.debug=TRUE DEBUG | wrapper | 2010/04/25 14:31:22 | Command[12] : -Dwrapper.disable_console_input=TRUE DEBUG | wrapper | 2010/04/25 14:31:22 | Command[13] : -Dwrapper.pid=28665 DEBUG | wrapper | 2010/04/25 14:31:22 | Command[14] : -Dwrapper.version=3.4.0 DEBUG | wrapper | 2010/04/25 14:31:22 | Command[15] : -Dwrapper.native_library=wrapper DEBUG | wrapper | 2010/04/25 14:31:22 | Command[16] : -Dwrapper.service=TRUE DEBUG | wrapper | 2010/04/25 14:31:22 | Command[17] : -Dwrapper.cpu.timeout=10 DEBUG | wrapper | 2010/04/25 14:31:22 | Command[18] : -Dwrapper.jvmid=1 DEBUG | wrapper | 2010/04/25 14:31:22 | Command[19] : com.test.javavmtester.JavaVMTester DEBUG | wrapper | 2010/04/25 14:31:22 | Ping settings: wrapper.ping.interval=5, wrapper.ping.interval.logged=1, wrapper.ping.timeout=30 STATUS | wrapper | 2010/04/25 14:31:22 | Launching a JVM... INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@3c0fabe9 INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager: Initializing... INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: JVM #1 INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Running a 64-bit JVM. INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Registering shutdown hook INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Using wrapper INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Registered MBean with Platform MBean Server: org.tanukisoftware.wrapper:type=WrapperManager INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Load native library. One or more attempts may fail if platform specific libraries do not exist. This is NORMAL and is only a problem if they all fail. INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Unable to load native library: libwrapper-solaris-x86-64.so Cause: no wrapper-solaris-x86-64 in java.library.path INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Loaded native library: libwrapper.so INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Calling native initialization method. INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperJNI Debug: Inside native WrapperManager initialization method INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Java Version : 1.6.0_18-b07 Java HotSpot(TM) 64-Bit Server VM INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Java VM Vendor : Sun Microsystems Inc. INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: OS Name : SunOS INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: OS Arch : amd64 INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: WrapperManager.start(Thread[Thread-1,5,main], args[]) called by thread: main INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Control event monitor thread started. INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Startup runner thread started. INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Communications runner thread started. INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Open socket to wrapper...Wrapper-Connection INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Opened Socket from 31000 to 32000 INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: Send a packet KEY : TYfJjxJ4jF0-5YDu INFO | jvm 1 | 2010/04/25 14:31:26 | WrapperManager Debug: handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000]) DEBUG | wrapperp | 2010/04/25 14:31:26 | accepted a socket from 127.0.0.1 on port 31000 DEBUG | wrapperp | 2010/04/25 14:31:26 | read a packet KEY : TYfJjxJ4jF0-5YDu DEBUG | wrapper | 2010/04/25 14:31:26 | Got key from JVM: TYfJjxJ4jF0-5YDu DEBUG | wrapperp | 2010/04/25 14:31:26 | send a packet LOW_LOG_LEVEL : 1 DEBUG | wrapperp | 2010/04/25 14:31:26 | send a packet PING_TIMEOUT : 30 DEBUG | wrapperp | 2010/04/25 14:31:26 | send a packet LOGFILE : ./server-wrapper.log DEBUG | wrapperp | 2010/04/25 14:31:26 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2010/04/25 14:31:26 | Start Application. DEBUG | wrapperp | 2010/04/25 14:31:26 | send a packet START : start INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Received a packet LOW_LOG_LEVEL : 1 INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: LowLogLevel from Wrapper is 1 INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Received a packet PING_TIMEOUT : 30 INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: PingTimeout from Wrapper is 30000 INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Received a packet LOGFILE : ./server-wrapper.log INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Received a packet PROPERTIES : (Property Values) INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Received a packet START : start INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: calling WrapperListener.start() INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: WrapperListener.start runner thread started. INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: returned from WrapperListener.start() INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Send a packet STARTED : INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: WrapperListener.start runner thread stopped. INFO | jvm 1 | 2010/04/25 14:31:27 | 2010.04.25 AD at 14:31:26 IDT INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Startup runner thread stopped. DEBUG | wrapperp | 2010/04/25 14:31:27 | read a packet STARTED : DEBUG | wrapper | 2010/04/25 14:31:27 | JVM signalled that it was started. DEBUG | wrapperp | 2010/04/25 14:31:27 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:27 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:27 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:31 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:31 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:31 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:31 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:32 | 2010.04.25 AD at 14:31:32 IDT DEBUG | wrapperp | 2010/04/25 14:31:35 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:35 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:35 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:35 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:37 | 2010.04.25 AD at 14:31:37 IDT DEBUG | wrapperp | 2010/04/25 14:31:39 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:39 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:39 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:39 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:42 | 2010.04.25 AD at 14:31:42 IDT DEBUG | wrapperp | 2010/04/25 14:31:43 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:43 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:43 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:43 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:47 | 2010.04.25 AD at 14:31:47 IDT DEBUG | wrapperp | 2010/04/25 14:31:47 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:47 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:47 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:47 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:51 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:51 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:51 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:51 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:52 | 2010.04.25 AD at 14:31:52 IDT DEBUG | wrapperp | 2010/04/25 14:31:55 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:56 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:56 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:31:56 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:31:57 | 2010.04.25 AD at 14:31:57 IDT DEBUG | wrapperp | 2010/04/25 14:32:00 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:00 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:00 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:00 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:02 | 2010.04.25 AD at 14:32:02 IDT DEBUG | wrapperp | 2010/04/25 14:32:04 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:04 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:04 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:04 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:07 | 2010.04.25 AD at 14:32:07 IDT DEBUG | wrapperp | 2010/04/25 14:32:08 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:08 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:08 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:08 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:12 | 2010.04.25 AD at 14:32:12 IDT DEBUG | wrapperp | 2010/04/25 14:32:12 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:12 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:12 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:12 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:16 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:16 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:16 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:16 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:17 | 2010.04.25 AD at 14:32:17 IDT DEBUG | wrapperp | 2010/04/25 14:32:20 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:20 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:20 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:20 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:22 | 2010.04.25 AD at 14:32:22 IDT DEBUG | wrapperp | 2010/04/25 14:32:24 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:24 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:24 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:24 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:27 | 2010.04.25 AD at 14:32:27 IDT DEBUG | wrapperp | 2010/04/25 14:32:28 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:29 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:29 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:29 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:32 | 2010.04.25 AD at 14:32:32 IDT DEBUG | wrapperp | 2010/04/25 14:32:33 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:33 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:33 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:33 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:37 | 2010.04.25 AD at 14:32:37 IDT DEBUG | wrapperp | 2010/04/25 14:32:37 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:37 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:37 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:37 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:41 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:41 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:41 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:41 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:42 | 2010.04.25 AD at 14:32:42 IDT DEBUG | wrapperp | 2010/04/25 14:32:45 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:45 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:45 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:45 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:47 | 2010.04.25 AD at 14:32:47 IDT DEBUG | wrapperp | 2010/04/25 14:32:49 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:49 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:49 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:49 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:52 | 2010.04.25 AD at 14:32:52 IDT DEBUG | wrapperp | 2010/04/25 14:32:53 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:53 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:53 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:53 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:57 | 2010.04.25 AD at 14:32:57 IDT DEBUG | wrapperp | 2010/04/25 14:32:57 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:57 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:32:57 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:32:57 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:01 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:02 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:02 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:02 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:02 | 2010.04.25 AD at 14:33:02 IDT DEBUG | wrapperp | 2010/04/25 14:33:06 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:06 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:06 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:06 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:07 | 2010.04.25 AD at 14:33:07 IDT DEBUG | wrapperp | 2010/04/25 14:33:10 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:10 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:10 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:10 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:12 | 2010.04.25 AD at 14:33:12 IDT DEBUG | wrapperp | 2010/04/25 14:33:14 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:14 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:14 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:14 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:17 | 2010.04.25 AD at 14:33:17 IDT DEBUG | wrapperp | 2010/04/25 14:33:18 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:18 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:18 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:18 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:22 | 2010.04.25 AD at 14:33:22 IDT DEBUG | wrapperp | 2010/04/25 14:33:22 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:22 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:22 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:22 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:26 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:26 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:26 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:26 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:27 | 2010.04.25 AD at 14:33:27 IDT DEBUG | wrapperp | 2010/04/25 14:33:30 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:30 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:30 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:30 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:32 | 2010.04.25 AD at 14:33:32 IDT DEBUG | wrapperp | 2010/04/25 14:33:34 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:34 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:34 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:34 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:37 | 2010.04.25 AD at 14:33:37 IDT DEBUG | wrapperp | 2010/04/25 14:33:38 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:39 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:39 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:39 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:42 | 2010.04.25 AD at 14:33:42 IDT DEBUG | wrapperp | 2010/04/25 14:33:43 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:43 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:43 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:43 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:47 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:47 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:47 | WrapperManager Debug: Send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:47 | 2010.04.25 AD at 14:33:47 IDT DEBUG | wrapperp | 2010/04/25 14:33:47 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:51 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:51 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:51 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:51 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:52 | 2010.04.25 AD at 14:33:52 IDT DEBUG | wrapperp | 2010/04/25 14:33:55 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:55 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:55 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:55 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:57 | 2010.04.25 AD at 14:33:57 IDT DEBUG | wrapperp | 2010/04/25 14:33:59 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:59 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:33:59 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:33:59 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:02 | 2010.04.25 AD at 14:34:02 IDT DEBUG | wrapperp | 2010/04/25 14:34:03 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:03 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:03 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:03 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:07 | 2010.04.25 AD at 14:34:07 IDT DEBUG | wrapperp | 2010/04/25 14:34:07 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:07 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:07 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:07 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:11 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:12 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:12 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:12 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:12 | 2010.04.25 AD at 14:34:12 IDT DEBUG | wrapperp | 2010/04/25 14:34:16 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:16 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:16 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:16 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:17 | 2010.04.25 AD at 14:34:17 IDT DEBUG | wrapperp | 2010/04/25 14:34:20 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:20 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:20 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:20 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:22 | 2010.04.25 AD at 14:34:22 IDT DEBUG | wrapperp | 2010/04/25 14:34:24 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:24 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:24 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:24 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:27 | 2010.04.25 AD at 14:34:27 IDT DEBUG | wrapperp | 2010/04/25 14:34:28 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:28 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:28 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:28 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:32 | 2010.04.25 AD at 14:34:32 IDT DEBUG | wrapperp | 2010/04/25 14:34:32 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:32 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:32 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:32 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:36 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:36 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:36 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:36 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:37 | 2010.04.25 AD at 14:34:37 IDT DEBUG | wrapperp | 2010/04/25 14:34:40 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:40 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:40 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:40 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:42 | 2010.04.25 AD at 14:34:42 IDT DEBUG | wrapperp | 2010/04/25 14:34:44 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:45 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:45 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:45 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:47 | 2010.04.25 AD at 14:34:47 IDT DEBUG | wrapperp | 2010/04/25 14:34:49 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:49 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:49 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:49 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:52 | 2010.04.25 AD at 14:34:52 IDT DEBUG | wrapperp | 2010/04/25 14:34:53 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:53 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:53 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:53 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:34:57 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:57 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:57 | WrapperManager Debug: Send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:34:57 | 2010.04.25 AD at 14:34:57 IDT DEBUG | wrapperp | 2010/04/25 14:34:57 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:01 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:01 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:01 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:01 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:02 | 2010.04.25 AD at 14:35:02 IDT DEBUG | wrapperp | 2010/04/25 14:35:05 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:05 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:05 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:05 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:07 | 2010.04.25 AD at 14:35:07 IDT DEBUG | wrapperp | 2010/04/25 14:35:09 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:09 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:09 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:09 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:12 | 2010.04.25 AD at 14:35:12 IDT DEBUG | wrapperp | 2010/04/25 14:35:13 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:13 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:13 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:13 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:17 | 2010.04.25 AD at 14:35:17 IDT DEBUG | wrapperp | 2010/04/25 14:35:17 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:17 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:17 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:17 | read a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:22 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:22 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:22 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:22 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:22 | 2010.04.25 AD at 14:35:22 IDT DEBUG | wrapperp | 2010/04/25 14:35:26 | send a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:26 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:26 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/25 14:35:26 | read a packet PING : ping INFO | jvm 1 | 2010/04/25 14:35:27 | 2010.04.25 AD at 14:35:27 IDT INFO | jvm 1 | 2010/04/25 14:35:32 | 2010.04.25 AD at 14:35:32 IDT INFO | jvm 1 | 2010/04/25 14:35:37 | 2010.04.25 AD at 14:35:37 IDT INFO | jvm 1 | 2010/04/25 14:35:42 | 2010.04.25 AD at 14:35:42 IDT INFO | jvm 1 | 2010/04/25 14:35:47 | 2010.04.25 AD at 14:35:47 IDT INFO | jvm 1 | 2010/04/25 14:35:52 | 2010.04.25 AD at 14:35:52 IDT INFO | jvm 1 | 2010/04/25 14:35:56 | WrapperManager Debug: Read Timed out. (Last Ping was 29000 milliseconds ago) INFO | jvm 1 | 2010/04/25 14:35:57 | 2010.04.25 AD at 14:35:57 IDT INFO | jvm 1 | 2010/04/25 14:36:02 | 2010.04.25 AD at 14:36:02 IDT INFO | jvm 1 | 2010/04/25 14:36:07 | 2010.04.25 AD at 14:36:07 IDT INFO | jvm 1 | 2010/04/25 14:36:12 | 2010.04.25 AD at 14:36:12 IDT INFO | jvm 1 | 2010/04/25 14:36:17 | 2010.04.25 AD at 14:36:17 IDT INFO | jvm 1 | 2010/04/25 14:36:22 | 2010.04.25 AD at 14:36:22 IDT INFO | jvm 1 | 2010/04/25 14:36:26 | WrapperManager Debug: Read Timed out. (Last Ping was 58900 milliseconds ago) INFO | jvm 1 | 2010/04/25 14:36:26 | WrapperManager: The Wrapper code did not ping the JVM for 58 seconds. Quit and let the Wrapper resynch. INFO | jvm 1 | 2010/04/25 14:36:26 | WrapperManager Debug: Send a packet RESTART : restart DEBUG | wrapperp | 2010/04/25 14:36:26 | read a packet RESTART : restart STATUS | wrapper | 2010/04/25 14:36:26 | JVM requested a restart. DEBUG | wrapper | 2010/04/25 14:36:26 | wrapperRestartProcess() called. DEBUG | wrapper | 2010/04/25 14:36:26 | Sending stop signal to JVM DEBUG | wrapperp | 2010/04/25 14:36:26 | send a packet STOP : NULL INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: Thread, Wrapper-Connection, handling the shutdown process. INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: calling listener.stop() INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: Waiting for WrapperListener.stop runner thread to complete. INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: WrapperListener.stop runner thread started. INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: WrapperListener.stop runner thread stopped. INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: returned from listener.stop() -> 0 INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: shutdownJVM(0) Thread:Wrapper-Connection INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: wait for 0 shutdown locs to be released. INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: Send a packet STOPPED : 0 DEBUG | wrapperp | 2010/04/25 14:36:27 | read a packet STOPPED : 0 DEBUG | wrapper | 2010/04/25 14:36:27 | JVM signalled that it was stopped. INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: Stopped checking for control events. INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: Closing socket. DEBUG | wrapperp | 2010/04/25 14:36:27 | socket read no code (closed?). INFO | jvm 1 | 2010/04/25 14:36:27 | 2010.04.25 AD at 14:36:27 IDT INFO | jvm 1 | 2010/04/25 14:36:27 | WrapperManager Debug: calling System.exit(0) DEBUG | wrapper | 2010/04/25 14:36:28 | Signal trapped. Details: DEBUG | wrapper | 2010/04/25 14:36:28 | signal number=18 (SIGCHLD), source="unknown" DEBUG | wrapper | 2010/04/25 14:36:28 | Received SIGCHLD, checking JVM process status. DEBUG | wrapper | 2010/04/25 14:36:28 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. DEBUG | wrapper | 2010/04/25 14:36:28 | JVM exited normally. DEBUG | wrapper | 2010/04/25 14:36:28 | JVM was only running for 245 seconds leading to a failed restart count of 1. DEBUG | wrapper | 2010/04/25 14:36:28 | Waiting 5 seconds before launching another JVM. bash-3.00# On Sat, Apr 24, 2010 at 1:50 PM, Tomer B <tom...@gm...> wrote: > reattaching dummy java app with .rtnzip with pass 1234 > as can be seen timeout happened to me with stop and native library was > loaded fine. > > > > On Sat, Apr 24, 2010 at 12:39 PM, Tomer B <tom...@gm...> wrote: > >> This email contained a .zip file attachment. Raytheon does not allow email >> attachments that are considered likely to contain malicious code. For your >> protection this attachment has been removed. >> >> If this email is from an unknown source, please simply delete this email. >> >> If this email was expected, and it is from a known sender, you may follow >> the below suggested instructions to obtain these types of attachments. >> >> + Instruct the sender to enclose the file(s) in a ".zip" compressed file, >> and rename the ".zip" compressed file with a different extension, such as, >> ".rtnzip". Password protecting the renamed ".zip" compressed file adds an >> additional layer of protection. When you receive the file, please rename it >> with the extension ".zip". >> >> Additional instructions and options on how to receive these attachments >> can be found at: >> >> http://security.it.ray.com/antivirus/extensions.html >> http://security.it.ray.com/news/2007/zipfiles.html >> >> Should you have any questions or difficulty with these instructions, >> please contact the Help Desk at 877.844.4712 >> >> --- >> >> Hi, >> Now the whole app loads fine (no warning as before about 32-64 bit >> mismatch). I got the timeout and shutdown. In the logs i'm sending there >> are a couple of startups see last one. >> >> >> STATUS | wrapper | 2010/04/23 11:43:49 | Java Service Wrapper Community >> Edition 64-bit 3.4.0 >> STATUS | wrapper | 2010/04/23 11:43:49 | Copyright (C) 1999-2010 Tanuki >> Software, Ltd. All Rights Reserved. >> STATUS | wrapper | 2010/04/23 11:43:49 | >> http://wrapper.tanukisoftware.org >> STATUS | wrapper | 2010/04/23 11:43:49 | >> DEBUG | wrapper | 2010/04/23 11:43:49 | Release time: 2010/03/16 >> 00:00:00 >> DEBUG | wrapper | 2010/04/23 11:43:49 | Build time: 2010/03/15 >> 14:49:00 >> DEBUG | wrapper | 2010/04/23 11:43:49 | Timezone: IST (IDT) Offset: >> -7200, hasDaylight: 1 >> DEBUG | wrapper | 2010/04/23 11:43:49 | Using tick timer. >> DEBUG | wrapper | 2010/04/23 11:43:49 | active log file changed: >> ./server-wrapper.log >> DEBUG | wrapper | 2010/04/23 11:43:49 | active log file changed: >> ./server-wrapper.log >> DEBUG | wrapperp | 2010/04/23 11:43:49 | server listening on port 32000. >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[0] : >> /usr/jdk/instances/jdk1.6.0/bin/java >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[1] : -d64 >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[2] : -Xloggc:gc.txt >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[3] : >> -Dsun.rmi.dgc.client.gcInterval=0x7ffffffffffffffe >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[4] : >> -Dsun.rmi.dgc.server.gcInterval=0x7ffffffffffffffe >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[5] : >> -Dsun.net.inetaddr.ttl=0 >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[6] : >> -Dsun.net.client.defaultConnectTimeout=30000 >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[7] : >> -Dsun.net.client.defaultReadTimeout=120000 >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[8] : -Dummy >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[9] : -XX:+PrintGCDetails >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[10] : >> -XX:+PrintGCTimeStamps >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[11] : >> -XX:MaxPermSize=256M >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[12] : >> -DentityExpansionLimit=256000 >> DEBUG | wrapper | 2010/04/23 11:43:49 | Command[13] : -verbose >> >> DEBUG | wrapperp | 2010/04/23 12:01:23 | read a packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:27 | send a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:28 | WrapperManager Debug: Received a >> packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:28 | WrapperManager Debug: Send a >> packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:28 | 2010.04.23 AD at 12:01:28 IDT >> DEBUG | wrapperp | 2010/04/23 12:01:28 | read a packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:32 | send a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:32 | WrapperManager Debug: Received a >> packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:32 | WrapperManager Debug: Send a >> packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:32 | read a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:33 | 2010.04.23 AD at 12:01:33 IDT >> DEBUG | wrapperp | 2010/04/23 12:01:36 | send a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:36 | WrapperManager Debug: Received a >> packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:36 | WrapperManager Debug: Send a >> packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:36 | read a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:38 | 2010.04.23 AD at 12:01:38 IDT >> DEBUG | wrapperp | 2010/04/23 12:01:40 | send a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:40 | WrapperManager Debug: Received a >> packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:40 | WrapperManager Debug: Send a >> packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:40 | read a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:43 | 2010.04.23 AD at 12:01:43 IDT >> DEBUG | wrapperp | 2010/04/23 12:01:44 | send a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:44 | WrapperManager Debug: Received a >> packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:44 | WrapperManager Debug: Send a >> packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:44 | read a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:48 | 2010.04.23 AD at 12:01:48 IDT >> DEBUG | wrapperp | 2010/04/23 12:01:48 | send a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:48 | WrapperManager Debug: Received a >> packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:48 | WrapperManager Debug: Send a >> packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:48 | read a packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:52 | send a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:52 | WrapperManager Debug: Received a >> packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:52 | WrapperManager Debug: Send a >> packet PING : ping >> DEBUG | wrapperp | 2010/04/23 12:01:52 | read a packet PING : ping >> INFO | jvm 1 | 2010/04/23 12:01:53 | 2010.04.23 AD at 12:01:53 IDT >> INFO | jvm 1 | 2010/04/23 12:01:58 | 2010.04.23 AD at 12:01:58 IDT >> INFO | jvm 1 | 2010/04/23 12:02:03 | 2010.04.23 AD at 12:02:03 IDT >> INFO | jvm 1 | 2010/04/23 12:02:08 | 2010.04.23 AD at 12:02:08 IDT >> INFO | jvm 1 | 2010/04/23 12:02:13 | 2010.04.23 AD at 12:02:13 IDT >> INFO | jvm 1 | 2010/04/23 12:02:18 | 2010.04.23 AD at 12:02:18 IDT >> INFO | jvm 1 | 2010/04/23 12:02:23 | 2010.04.23 AD at 12:02:23 IDT >> INFO | jvm 1 | 2010/04/23 12:02:28 | 2010.04.23 AD at 12:02:28 IDT >> INFO | jvm 1 | 2010/04/23 12:02:33 | 2010.04.23 AD at 12:02:33 IDT >> INFO | jvm 1 | 2010/04/23 12:02:38 | 2010.04.23 AD at 12:02:38 IDT >> INFO | jvm 1 | 2010/04/23 12:02:43 | 2010.04.23 AD at 12:02:43 IDT >> INFO | jvm 1 | 2010/04/23 12:02:48 | 2010.04.23 AD at 12:02:48 IDT >> INFO | jvm 1 | 2010/04/23 12:02:53 | 2010.04.23 AD at 12:02:53 IDT >> INFO | jvm 1 | 2010/04/23 12:02:58 | 2010.04.23 AD at 12:02:58 IDT >> INFO | jvm 1 | 2010/04/23 12:03:03 | 2010.04.23 AD at 12:03:03 IDT >> INFO | jvm 1 | 2010/04/23 12:03:08 | 2010.04.23 AD at 12:03:08 IDT >> INFO | jvm 1 | 2010/04/23 12:03:13 | 2010.04.23 AD at 12:03:13 IDT >> INFO | jvm 1 | 2010/04/23 12:03:18 | 2010.04.23 AD at 12:03:18 IDT >> INFO | jvm 1 | 2010/04/23 12:03:23 | 2010.04.23 AD at 12:03:23 IDT >> INFO | jvm 1 | 2010/04/23 12:03:28 | 2010.04.23 AD at 12:03:28 IDT >> INFO | jvm 1 | 2010/04/23 12:03:33 | 2010.04.23 AD at 12:03:33 IDT >> INFO | jvm 1 | 2010/04/23 12:03:38 | 2010.04.23 AD at 12:03:38 IDT >> INFO | jvm 1 | 2010/04/23 12:03:43 | 2010.04.23 AD at 12:03:43 IDT >> INFO | jvm 1 | 2010/04/23 12:03:48 | 2010.04.23 AD at 12:03:48 IDT >> INFO | jvm 1 | 2010/04/23 12:03:53 | 2010.04.23 AD at 12:03:53 IDT >> INFO | jvm 1 | 2010/04/23 12:03:58 | 2010.04.23 AD at 12:03:58 IDT >> INFO | jvm 1 | 2010/04/23 12:04:03 | 2010.04.23 AD at 12:04:03 IDT >> INFO | jvm 1 | 2010/04/23 12:04:08 | 2010.04.23 AD at 12:04:08 IDT >> INFO | jvm 1 | 2010/04/23 12:04:13 | 2010.04.23 AD at 12:04:13 IDT >> INFO | jvm 1 | 2010/04/23 12:04:18 | 2010.04.23 AD at 12:04:18 IDT >> INFO | jvm 1 | 2010/04/23 12:04:23 | 2010.04.23 AD at 12:04:23 IDT >> INFO | jvm 1 | 2010/04/23 12:04:28 | 2010.04.23 AD at 12:04:28 IDT >> INFO | jvm 1 | 2010/04/23 12:04:33 | 2010.04.23 AD at 12:04:33 IDT >> INFO | jvm 1 | 2010/04/23 12:04:38 | 2010.04.23 AD at 12:04:38 IDT >> INFO | jvm 1 | 2010/04/23 12:04:43 | 2010.04.23 AD at 12:04:43 IDT >> INFO | jvm 1 | 2010/04/23 12:04:48 | 2010.04.23 AD at 12:04:48 IDT >> INFO | jvm 1 | 2010/04/23 12:04:53 | 2010.04.23 AD at 12:04:53 IDT >> INFO | jvm 1 | 2010/04/23 12:04:58 | 2010.04.23 AD at 12:04:58 IDT >> INFO | jvm 1 | 2010/04/23 12:05:03 | 2010.04.23 AD at 12:05:03 IDT >> INFO | jvm 1 | 2010/04/23 12:05:08 | 2010.04.23 AD at 12:05:08 IDT >> INFO | jvm 1 | 2010/04/23 12:05:13 | 2010.04.23 AD at 12:05:13 IDT >> INFO | jvm 1 | 2010/04/23 12:05:18 | 2010.04.23 AD at 12:05:18 IDT >> INFO | jvm 1 | 2010/04/23 12:05:23 | 2010.04.23 AD at 12:05:23 IDT >> INFO | jvm 1 | 2010/04/23 12:05:28 | 2010.04.23 AD at 12:05:28 IDT >> INFO | jvm 1 | 2010/04/23 12:05:33 | 2010.04.23 AD at 12:05:33 IDT >> INFO | jvm 1 | 2010/04/23 12:05:38 | 2010.04.23 AD at 12:05:38 IDT >> INFO | jvm 1 | 2010/04/23 12:05:43 | 2010.04.23 AD at 12:05:43 IDT >> INFO | jvm 1 | 2010/04/23 12:05:48 | 2010.04.23 AD at 12:05:48 IDT >> INFO | jvm 1 | 2010/04/23 12:05:53 | 2010.04.23 AD at 12:05:53 IDT >> INFO | jvm 1 | 2010/04/23 12:05:58 | 2010.04.23 AD at 12:05:58 IDT >> INFO | jvm 1 | 2010/04/23 12:06:03 | 2010.04.23 AD at 12:06:03 IDT >> INFO | jvm 1 | 2010/04/23 12:06:08 | 2010.04.23 AD at 12:06:08 IDT >> INFO | jvm 1 | 2010/04/23 12:06:13 | 2010.04.23 AD at 12:06:13 IDT >> INFO | jvm 1 | 2010/04/23 12:06:18 | 2010.04.23 AD at 12:06:18 IDT >> INFO | jvm 1 | 2010/04/23 12:06:23 | 2010.04.23 AD at 12:06:23 IDT >> INFO | jvm 1 | 2010/04/23 12:06:28 | 2010.04.23 AD at 12:06:28 IDT >> INFO | jvm 1 | 2010/04/23 12:06:33 | 2010.04.23 AD at 12:06:33 IDT >> INFO | jvm 1 | 2010/04/23 12:06:38 | 2010.04.23 AD at 12:06:38 IDT >> INFO | jvm 1 | 2010/04/23 12:06:43 | 2010.04.23 AD at 12:06:43 IDT >> INFO | jvm 1 | 2010/04/23 12:06:48 | 2010.04.23 AD at 12:06:48 IDT >> INFO | jvm 1 | 2010/04/23 12:06:52 | [Loaded >> java.net.SocketTimeoutException from >> /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] >> INFO | jvm 1 | 2010/04/23 12:06:52 | [Loaded >> sun.net.ConnectionResetException from >> /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] >> INFO | jvm 1 | 2010/04/23 12:06:52 | WrapperManager Debug: Read Timed >> out. (Last Ping was 298100 milliseconds ago) >> INFO | jvm 1 | 2010/04/23 12:06:53 | 2010.04.23 AD at 12:06:53 IDT >> INFO | jvm 1 | 2010/04/23 12:06:58 | 2010.04.23 AD at 12:06:58 IDT >> INFO | jvm 1 | 2010/04/23 12:07:03 | 2010.04.23 AD at 12:07:03 IDT >> INFO | jvm 1 | 2010/04/23 12:07:08 | 2010.04.23 AD at 12:07:08 IDT >> INFO | jvm 1 | 2010/04/23 12:07:13 | 2010.04.23 AD at 12:07:13 IDT >> INFO | jvm 1 | 2010/04/23 12:07:18 | 2010.04.23 AD at 12:07:18 IDT >> INFO | jvm 1 | 2010/04/23 12:07:23 | 2010.04.23 AD at 12:07:23 IDT >> INFO | jvm 1 | 2010/04/23 12:07:28 | 2010.04.23 AD at 12:07:28 IDT >> INFO | jvm 1 | 2010/04/23 12:07:33 | 2010.04.23 AD at 12:07:33 IDT >> INFO | jvm 1 | 2010/04/23 12:07:38 | 2010.04.23 AD at 12:07:38 IDT >> INFO | jvm 1 | 2010/04/23 12:07:43 | 2010.04.23 AD at 12:07:43 IDT >> INFO | jvm 1 | 2010/04/23 12:07:48 | 2010.04.23 AD at 12:07:48 IDT >> INFO | jvm 1 | 2010/04/23 12:07:53 | 2010.04.23 AD at 12:07:53 IDT >> INFO | jvm 1 | 2010/04/23 12:07:58 | 2010.04.23 AD at 12:07:58 IDT >> INFO | jvm 1 | 2010/04/23 12:08:03 | 2010.04.23 AD at 12:08:03 IDT >> INFO | jvm 1 | 2010/04/23 12:08:08 | 2010.04.23 AD at 12:08:08 IDT >> INFO | jvm 1 | 2010/04/23 12:08:13 | 2010.04.23 AD at 12:08:13 IDT >> INFO | jvm 1 | 2010/04/23 12:08:18 | 2010.04.23 AD at 12:08:18 IDT >> INFO | jvm 1 | 2010/04/23 12:08:23 | 2010.04.23 AD at 12:08:23 IDT >> INFO | jvm 1 | 2010/04/23 12:08:28 | 2010.04.23 AD at 12:08:28 IDT >> INFO | jvm 1 | 2010/04/23 12:08:33 | 2010.04.23 AD at 12:08:33 IDT >> INFO | jvm 1 | 2010/04/23 12:08:38 | 2010.04.23 AD at 12:08:38 IDT >> INFO | jvm 1 | 2010/04/23 12:08:43 | 2010.04.23 AD at 12:08:43 IDT >> INFO | jvm 1 | 2010/04/23 12:08:48 | 2010.04.23 AD at 12:08:48 IDT >> INFO | jvm 1 | 2010/04/23 12:08:53 | 2010.04.23 AD at 12:08:53 IDT >> INFO | jvm 1 | 2010/04/23 12:08:58 | 2010.04.23 AD at 12:08:58 IDT >> INFO | jvm 1 | 2010/04/23 12:09:03 | 2010.04.23 AD at 12:09:03 IDT >> INFO | jvm 1 | 2010/04/23 12:09:08 | 2010.04.23 AD at 12:09:08 IDT >> INFO | jvm 1 | 2010/04/23 12:09:13 | 2010.04.23 AD at 12:09:13 IDT >> INFO | jvm 1 | 2010/04/23 12:09:18 | 2010.04.23 AD at 12:09:18 IDT >> INFO | jvm 1 | 2010/04/23 12:09:23 | 2010.04.23 AD at 12:09:23 IDT >> INFO | jvm 1 | 2010/04/23 12:09:28 | 2010.04.23 AD at 12:09:28 IDT >> INFO | jvm 1 | 2010/04/23 12:09:33 | 2010.04.23 AD at 12:09:33 IDT >> INFO | jvm 1 | 2010/04/23 12:09:38 | 2010.04.23 AD at 12:09:38 IDT >> INFO | jvm 1 | 2010/04/23 12:09:43 | 2010.04.23 AD at 12:09:43 IDT >> INFO | jvm 1 | 2010/04/23 12:09:48 | 2010.04.23 AD at 12:09:48 IDT >> INFO | jvm 1 | 2010/04/23 12:09:53 | 2010.04.23 AD at 12:09:53 IDT >> INFO | jvm 1 | 2010/04/23 12:09:58 | 2010.04.23 AD at 12:09:58 IDT >> INFO | jvm 1 | 2010/04/23 12:10:03 | 2010.04.23 AD at 12:10:03 IDT >> INFO | jvm 1 | 2010/04/23 12:10:08 | 2010.04.23 AD at 12:10:08 IDT >> INFO | jvm 1 | 2010/04/23 12:10:13 | 2010.04.23 AD at 12:10:13 IDT >> INFO | jvm 1 | 2010/04/23 12:10:18 | 2010.04.23 AD at 12:10:18 IDT >> INFO | jvm 1 | 2010/04/23 12:10:23 | 2010.04.23 AD at 12:10:23 IDT >> INFO | jvm 1 | 2010/04/23 12:10:28 | 2010.04.23 AD at 12:10:28 IDT >> INFO | jvm 1 | 2010/04/23 12:10:33 | 2010.04.23 AD at 12:10:33 IDT >> INFO | jvm 1 | 2010/04/23 12:10:38 | 2010.04.23 AD at 12:10:38 IDT >> INFO | jvm 1 | 2010/04/23 12:10:43 | 2010.04.23 AD at 12:10:43 IDT >> INFO | jvm 1 | 2010/04/23 12:10:48 | 2010.04.23 AD at 12:10:48 IDT >> INFO | jvm 1 | 2010/04/23 12:10:53 | 2010.04.23 AD at 12:10:53 IDT >> INFO | jvm 1 | 2010/04/23 12:10:58 | 2010.04.23 AD at 12:10:58 IDT >> INFO | jvm 1 | 2010/04/23 12:11:04 | 2010.04.23 AD at 12:11:03 IDT >> INFO | jvm 1 | 2010/04/23 12:11:08 | 2010.04.23 AD at 12:11:08 IDT >> INFO | jvm 1 | 2010/04/23 12:11:13 | 2010.04.23 AD at 12:11:13 IDT >> INFO | jvm 1 | 2010/04/23 12:11:18 | 2010.04.23 AD at 12:11:18 IDT >> INFO | jvm 1 | 2010/04/23 12:11:24 | 2010.04.23 AD at 12:11:23 IDT >> INFO | jvm 1 | 2010/04/23 12:11:29 | 2010.04.23 AD at 12:11:28 IDT >> INFO | jvm 1 | 2010/04/23 12:11:34 | 2010.04.23 AD at 12:11:33 IDT >> INFO | jvm 1 | 2010/04/23 12:11:39 | 2010.04.23 AD at 12:11:38 IDT >> INFO | jvm 1 | 2010/04/23 12:11:44 | 2010.04.23 AD at 12:11:43 IDT >> INFO | jvm 1 | 2010/04/23 12:11:49 | 2010.04.23 AD at 12:11:48 IDT >> INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Read Timed >> out. (Last Ping was 596300 milliseconds ago) >> INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager: JVM did not >> exit. >> Give up. >> INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded >> java.util.IdentityHashMap$KeySet from >> /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] >> INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded >> java.util.IdentityHashMap$IdentityHashMapIterator from >> /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] >> INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded >> java.util.IdentityHashMap$KeyIterator from >> /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] >> INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: >> ShutdownHook >> started >> INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: >> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook >> INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Send a >> packet STOP : 0 >> INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Stopped >> checking for control events. >> DEBUG | wrapperp | 2010/04/23 12:11:52 | read a packet STOP : 0 >> DEBUG | wrapper | 2010/04/23 12:11:52 | JVM requested a shutdown. (0) >> DEBUG | wrapper | 2010/04/23 12:11:52 | wrapperStopProcess(0) called. >> DEBUG | wrapper | 2010/04/23 12:11:52 | Sending stop signal to JVM >> DEBUG | wrapperp | 2010/04/23 12:11:52 | send a packet STOP : NULL >> INFO | jvm 1 | 2010/04/23 12:11:53 | [Loaded >> org.tanukisoftware.wrapper.WrapperManager$8 from >> file:/opt/javatest/wrapper.jar] >> INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Thread, >> Wrapper-Shutdown-Hook, handling the shutdown process. >> INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: calling >> listener.stop() >> INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: returned >> from listener.stop() -> 0 >> INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: >> shutdownJVM(0) Thread:Wrapper-Shutdown-Hook >> INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: wait for 0 >> shutdown locs to be released. >> INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Send a >> packet STOPPED : 0 >> DEBUG | wrapperp | 2010/04/23 12:11:53 | read a packet STOPPED : 0 >> DEBUG | wrapper | 2010/04/23 12:11:53 | JVM signalled that it was >> stopped. >> INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Closing >> socket. >> DEBUG | wrapperp | 2010/04/23 12:11:53 | socket read no code (closed?). >> INFO | jvm 1 | 2010/04/23 12:11:54 | 2010.04.23 AD at 12:11:53 IDT >> INFO | jvm 1 | 2010/04/23 12:11:54 | WrapperManager Debug: >> ShutdownHook >> complete >> DEBUG | wrapper | 2010/04/23 12:11:55 | Signal trapped. Details: >> DEBUG | wrapper | 2010/04/23 12:11:55 | signal number=18 (SIGCHLD), >> source="unknown" >> DEBUG | wrapper | 2010/04/23 12:11:55 | Received SIGCHLD, checking JVM >> process status. >> DEBUG | wrapper | 2010/04/23 12:11:55 | JVM process exited with a code >> of >> 1, setting the wrapper exit code to 1. >> DEBUG | wrapper | 2010/04/23 12:11:55 | JVM exited normally. >> STATUS | wrapper | 2010/04/23 12:11:55 | <-- Wrapper Stopped >> >> i'm attaching the whole app again >> >> >> On Fri, Apr 23, 2010 at 9:49 AM, Leif Mortenson <le...@ta... >> >wrote: >> >> > Tomer, >> > Thank you for the logs. I am looking through them. >> > >> > One thing that I do see is that your native library is not being >> > loaded correctly: >> > --- >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: WARNING - >> > Unable to load the Wrapper's native library 'libwrapper.so'. >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > The file is located on the path at the following location but >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > could not be loaded: >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > /opt/javatest/./libwrapper.so >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > Please verify that the file is readable by the current user >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > and that the file has not been corrupted in any way. >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > One common cause of this problem is running a 32-bit version >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: of >> > the Wrapper with a 64-bit version of Java, or vica versa. >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > This is a 32-bit JVM. >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > Reported cause: >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > /opt/javatest/libwrapper.so: ld.so.1: java: fatal: >> > /opt/javatest/libwrapper.so: wrong ELF class: ELFCLASS64 (Possible >> > cause: architecture word width misma$ >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> > System signals will not be handled correctly. >> > --- >> > >> > There are a few things in the logs which are confusing me as well: >> > 1) In the first post that you sent, there were log entries like the >> > following stating that the Wrapper had not pinged the JVM for almost 5 >> > minutes and that the socket read times out. This actually made some >> > sense: >> > --- >> > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read >> > Timed out. (Last Ping was 298400 milliseconds ago) >> > --- >> > In this latest log file however, this time has become 0 in all cases: >> > --- >> > INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read >> > Timed out. (Last Ping was 0 milliseconds ago) >> > --- >> > Thar time is calculated using the internal timing mechanism of the the >> > Wrapper and the only way that it could be 0 is if the WrapperManager's >> > Event Monitor thread was not running. >> > I can see that that thread started because of the following line: >> > --- >> > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager Debug: >> > Control event monitor thread started. >> > --- >> > There is no message that it was ever stopped however which doesn't make >> > sense. >> > >> > 2) You have set your wrapper.ping.timeout=300. This means that >> > regardless of what may go wrong in the JVM, the Wrapper should be >> > killing the JVM if it fails to respo... [truncated message content] |
|
From: Tomer B <tom...@gm...> - 2010-04-24 09:40:32
|
This email contained a .zip file attachment. Raytheon does not allow email attachments that are considered likely to contain malicious code. For your protection this attachment has been removed. If this email is from an unknown source, please simply delete this email. If this email was expected, and it is from a known sender, you may follow the below suggested instructions to obtain these types of attachments. + Instruct the sender to enclose the file(s) in a ".zip" compressed file, and rename the ".zip" compressed file with a different extension, such as, ".rtnzip". Password protecting the renamed ".zip" compressed file adds an additional layer of protection. When you receive the file, please rename it with the extension ".zip". Additional instructions and options on how to receive these attachments can be found at: http://security.it.ray.com/antivirus/extensions.html http://security.it.ray.com/news/2007/zipfiles.html Should you have any questions or difficulty with these instructions, please contact the Help Desk at 877.844.4712 --- Hi, Now the whole app loads fine (no warning as before about 32-64 bit mismatch). I got the timeout and shutdown. In the logs i'm sending there are a couple of startups see last one. STATUS | wrapper | 2010/04/23 11:43:49 | Java Service Wrapper Community Edition 64-bit 3.4.0 STATUS | wrapper | 2010/04/23 11:43:49 | Copyright (C) 1999-2010 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2010/04/23 11:43:49 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2010/04/23 11:43:49 | DEBUG | wrapper | 2010/04/23 11:43:49 | Release time: 2010/03/16 00:00:00 DEBUG | wrapper | 2010/04/23 11:43:49 | Build time: 2010/03/15 14:49:00 DEBUG | wrapper | 2010/04/23 11:43:49 | Timezone: IST (IDT) Offset: -7200, hasDaylight: 1 DEBUG | wrapper | 2010/04/23 11:43:49 | Using tick timer. DEBUG | wrapper | 2010/04/23 11:43:49 | active log file changed: ./server-wrapper.log DEBUG | wrapper | 2010/04/23 11:43:49 | active log file changed: ./server-wrapper.log DEBUG | wrapperp | 2010/04/23 11:43:49 | server listening on port 32000. DEBUG | wrapper | 2010/04/23 11:43:49 | Command[0] : /usr/jdk/instances/jdk1.6.0/bin/java DEBUG | wrapper | 2010/04/23 11:43:49 | Command[1] : -d64 DEBUG | wrapper | 2010/04/23 11:43:49 | Command[2] : -Xloggc:gc.txt DEBUG | wrapper | 2010/04/23 11:43:49 | Command[3] : -Dsun.rmi.dgc.client.gcInterval=0x7ffffffffffffffe DEBUG | wrapper | 2010/04/23 11:43:49 | Command[4] : -Dsun.rmi.dgc.server.gcInterval=0x7ffffffffffffffe DEBUG | wrapper | 2010/04/23 11:43:49 | Command[5] : -Dsun.net.inetaddr.ttl=0 DEBUG | wrapper | 2010/04/23 11:43:49 | Command[6] : -Dsun.net.client.defaultConnectTimeout=30000 DEBUG | wrapper | 2010/04/23 11:43:49 | Command[7] : -Dsun.net.client.defaultReadTimeout=120000 DEBUG | wrapper | 2010/04/23 11:43:49 | Command[8] : -Dummy DEBUG | wrapper | 2010/04/23 11:43:49 | Command[9] : -XX:+PrintGCDetails DEBUG | wrapper | 2010/04/23 11:43:49 | Command[10] : -XX:+PrintGCTimeStamps DEBUG | wrapper | 2010/04/23 11:43:49 | Command[11] : -XX:MaxPermSize=256M DEBUG | wrapper | 2010/04/23 11:43:49 | Command[12] : -DentityExpansionLimit=256000 DEBUG | wrapper | 2010/04/23 11:43:49 | Command[13] : -verbose DEBUG | wrapperp | 2010/04/23 12:01:23 | read a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:27 | send a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:28 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:28 | WrapperManager Debug: Send a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:28 | 2010.04.23 AD at 12:01:28 IDT DEBUG | wrapperp | 2010/04/23 12:01:28 | read a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:32 | send a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:32 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:32 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:32 | read a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:33 | 2010.04.23 AD at 12:01:33 IDT DEBUG | wrapperp | 2010/04/23 12:01:36 | send a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:36 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:36 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:36 | read a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:38 | 2010.04.23 AD at 12:01:38 IDT DEBUG | wrapperp | 2010/04/23 12:01:40 | send a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:40 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:40 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:40 | read a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:43 | 2010.04.23 AD at 12:01:43 IDT DEBUG | wrapperp | 2010/04/23 12:01:44 | send a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:44 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:44 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:44 | read a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:48 | 2010.04.23 AD at 12:01:48 IDT DEBUG | wrapperp | 2010/04/23 12:01:48 | send a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:48 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:48 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:48 | read a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:52 | send a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:52 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:52 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/23 12:01:52 | read a packet PING : ping INFO | jvm 1 | 2010/04/23 12:01:53 | 2010.04.23 AD at 12:01:53 IDT INFO | jvm 1 | 2010/04/23 12:01:58 | 2010.04.23 AD at 12:01:58 IDT INFO | jvm 1 | 2010/04/23 12:02:03 | 2010.04.23 AD at 12:02:03 IDT INFO | jvm 1 | 2010/04/23 12:02:08 | 2010.04.23 AD at 12:02:08 IDT INFO | jvm 1 | 2010/04/23 12:02:13 | 2010.04.23 AD at 12:02:13 IDT INFO | jvm 1 | 2010/04/23 12:02:18 | 2010.04.23 AD at 12:02:18 IDT INFO | jvm 1 | 2010/04/23 12:02:23 | 2010.04.23 AD at 12:02:23 IDT INFO | jvm 1 | 2010/04/23 12:02:28 | 2010.04.23 AD at 12:02:28 IDT INFO | jvm 1 | 2010/04/23 12:02:33 | 2010.04.23 AD at 12:02:33 IDT INFO | jvm 1 | 2010/04/23 12:02:38 | 2010.04.23 AD at 12:02:38 IDT INFO | jvm 1 | 2010/04/23 12:02:43 | 2010.04.23 AD at 12:02:43 IDT INFO | jvm 1 | 2010/04/23 12:02:48 | 2010.04.23 AD at 12:02:48 IDT INFO | jvm 1 | 2010/04/23 12:02:53 | 2010.04.23 AD at 12:02:53 IDT INFO | jvm 1 | 2010/04/23 12:02:58 | 2010.04.23 AD at 12:02:58 IDT INFO | jvm 1 | 2010/04/23 12:03:03 | 2010.04.23 AD at 12:03:03 IDT INFO | jvm 1 | 2010/04/23 12:03:08 | 2010.04.23 AD at 12:03:08 IDT INFO | jvm 1 | 2010/04/23 12:03:13 | 2010.04.23 AD at 12:03:13 IDT INFO | jvm 1 | 2010/04/23 12:03:18 | 2010.04.23 AD at 12:03:18 IDT INFO | jvm 1 | 2010/04/23 12:03:23 | 2010.04.23 AD at 12:03:23 IDT INFO | jvm 1 | 2010/04/23 12:03:28 | 2010.04.23 AD at 12:03:28 IDT INFO | jvm 1 | 2010/04/23 12:03:33 | 2010.04.23 AD at 12:03:33 IDT INFO | jvm 1 | 2010/04/23 12:03:38 | 2010.04.23 AD at 12:03:38 IDT INFO | jvm 1 | 2010/04/23 12:03:43 | 2010.04.23 AD at 12:03:43 IDT INFO | jvm 1 | 2010/04/23 12:03:48 | 2010.04.23 AD at 12:03:48 IDT INFO | jvm 1 | 2010/04/23 12:03:53 | 2010.04.23 AD at 12:03:53 IDT INFO | jvm 1 | 2010/04/23 12:03:58 | 2010.04.23 AD at 12:03:58 IDT INFO | jvm 1 | 2010/04/23 12:04:03 | 2010.04.23 AD at 12:04:03 IDT INFO | jvm 1 | 2010/04/23 12:04:08 | 2010.04.23 AD at 12:04:08 IDT INFO | jvm 1 | 2010/04/23 12:04:13 | 2010.04.23 AD at 12:04:13 IDT INFO | jvm 1 | 2010/04/23 12:04:18 | 2010.04.23 AD at 12:04:18 IDT INFO | jvm 1 | 2010/04/23 12:04:23 | 2010.04.23 AD at 12:04:23 IDT INFO | jvm 1 | 2010/04/23 12:04:28 | 2010.04.23 AD at 12:04:28 IDT INFO | jvm 1 | 2010/04/23 12:04:33 | 2010.04.23 AD at 12:04:33 IDT INFO | jvm 1 | 2010/04/23 12:04:38 | 2010.04.23 AD at 12:04:38 IDT INFO | jvm 1 | 2010/04/23 12:04:43 | 2010.04.23 AD at 12:04:43 IDT INFO | jvm 1 | 2010/04/23 12:04:48 | 2010.04.23 AD at 12:04:48 IDT INFO | jvm 1 | 2010/04/23 12:04:53 | 2010.04.23 AD at 12:04:53 IDT INFO | jvm 1 | 2010/04/23 12:04:58 | 2010.04.23 AD at 12:04:58 IDT INFO | jvm 1 | 2010/04/23 12:05:03 | 2010.04.23 AD at 12:05:03 IDT INFO | jvm 1 | 2010/04/23 12:05:08 | 2010.04.23 AD at 12:05:08 IDT INFO | jvm 1 | 2010/04/23 12:05:13 | 2010.04.23 AD at 12:05:13 IDT INFO | jvm 1 | 2010/04/23 12:05:18 | 2010.04.23 AD at 12:05:18 IDT INFO | jvm 1 | 2010/04/23 12:05:23 | 2010.04.23 AD at 12:05:23 IDT INFO | jvm 1 | 2010/04/23 12:05:28 | 2010.04.23 AD at 12:05:28 IDT INFO | jvm 1 | 2010/04/23 12:05:33 | 2010.04.23 AD at 12:05:33 IDT INFO | jvm 1 | 2010/04/23 12:05:38 | 2010.04.23 AD at 12:05:38 IDT INFO | jvm 1 | 2010/04/23 12:05:43 | 2010.04.23 AD at 12:05:43 IDT INFO | jvm 1 | 2010/04/23 12:05:48 | 2010.04.23 AD at 12:05:48 IDT INFO | jvm 1 | 2010/04/23 12:05:53 | 2010.04.23 AD at 12:05:53 IDT INFO | jvm 1 | 2010/04/23 12:05:58 | 2010.04.23 AD at 12:05:58 IDT INFO | jvm 1 | 2010/04/23 12:06:03 | 2010.04.23 AD at 12:06:03 IDT INFO | jvm 1 | 2010/04/23 12:06:08 | 2010.04.23 AD at 12:06:08 IDT INFO | jvm 1 | 2010/04/23 12:06:13 | 2010.04.23 AD at 12:06:13 IDT INFO | jvm 1 | 2010/04/23 12:06:18 | 2010.04.23 AD at 12:06:18 IDT INFO | jvm 1 | 2010/04/23 12:06:23 | 2010.04.23 AD at 12:06:23 IDT INFO | jvm 1 | 2010/04/23 12:06:28 | 2010.04.23 AD at 12:06:28 IDT INFO | jvm 1 | 2010/04/23 12:06:33 | 2010.04.23 AD at 12:06:33 IDT INFO | jvm 1 | 2010/04/23 12:06:38 | 2010.04.23 AD at 12:06:38 IDT INFO | jvm 1 | 2010/04/23 12:06:43 | 2010.04.23 AD at 12:06:43 IDT INFO | jvm 1 | 2010/04/23 12:06:48 | 2010.04.23 AD at 12:06:48 IDT INFO | jvm 1 | 2010/04/23 12:06:52 | [Loaded java.net.SocketTimeoutException from /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] INFO | jvm 1 | 2010/04/23 12:06:52 | [Loaded sun.net.ConnectionResetException from /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] INFO | jvm 1 | 2010/04/23 12:06:52 | WrapperManager Debug: Read Timed out. (Last Ping was 298100 milliseconds ago) INFO | jvm 1 | 2010/04/23 12:06:53 | 2010.04.23 AD at 12:06:53 IDT INFO | jvm 1 | 2010/04/23 12:06:58 | 2010.04.23 AD at 12:06:58 IDT INFO | jvm 1 | 2010/04/23 12:07:03 | 2010.04.23 AD at 12:07:03 IDT INFO | jvm 1 | 2010/04/23 12:07:08 | 2010.04.23 AD at 12:07:08 IDT INFO | jvm 1 | 2010/04/23 12:07:13 | 2010.04.23 AD at 12:07:13 IDT INFO | jvm 1 | 2010/04/23 12:07:18 | 2010.04.23 AD at 12:07:18 IDT INFO | jvm 1 | 2010/04/23 12:07:23 | 2010.04.23 AD at 12:07:23 IDT INFO | jvm 1 | 2010/04/23 12:07:28 | 2010.04.23 AD at 12:07:28 IDT INFO | jvm 1 | 2010/04/23 12:07:33 | 2010.04.23 AD at 12:07:33 IDT INFO | jvm 1 | 2010/04/23 12:07:38 | 2010.04.23 AD at 12:07:38 IDT INFO | jvm 1 | 2010/04/23 12:07:43 | 2010.04.23 AD at 12:07:43 IDT INFO | jvm 1 | 2010/04/23 12:07:48 | 2010.04.23 AD at 12:07:48 IDT INFO | jvm 1 | 2010/04/23 12:07:53 | 2010.04.23 AD at 12:07:53 IDT INFO | jvm 1 | 2010/04/23 12:07:58 | 2010.04.23 AD at 12:07:58 IDT INFO | jvm 1 | 2010/04/23 12:08:03 | 2010.04.23 AD at 12:08:03 IDT INFO | jvm 1 | 2010/04/23 12:08:08 | 2010.04.23 AD at 12:08:08 IDT INFO | jvm 1 | 2010/04/23 12:08:13 | 2010.04.23 AD at 12:08:13 IDT INFO | jvm 1 | 2010/04/23 12:08:18 | 2010.04.23 AD at 12:08:18 IDT INFO | jvm 1 | 2010/04/23 12:08:23 | 2010.04.23 AD at 12:08:23 IDT INFO | jvm 1 | 2010/04/23 12:08:28 | 2010.04.23 AD at 12:08:28 IDT INFO | jvm 1 | 2010/04/23 12:08:33 | 2010.04.23 AD at 12:08:33 IDT INFO | jvm 1 | 2010/04/23 12:08:38 | 2010.04.23 AD at 12:08:38 IDT INFO | jvm 1 | 2010/04/23 12:08:43 | 2010.04.23 AD at 12:08:43 IDT INFO | jvm 1 | 2010/04/23 12:08:48 | 2010.04.23 AD at 12:08:48 IDT INFO | jvm 1 | 2010/04/23 12:08:53 | 2010.04.23 AD at 12:08:53 IDT INFO | jvm 1 | 2010/04/23 12:08:58 | 2010.04.23 AD at 12:08:58 IDT INFO | jvm 1 | 2010/04/23 12:09:03 | 2010.04.23 AD at 12:09:03 IDT INFO | jvm 1 | 2010/04/23 12:09:08 | 2010.04.23 AD at 12:09:08 IDT INFO | jvm 1 | 2010/04/23 12:09:13 | 2010.04.23 AD at 12:09:13 IDT INFO | jvm 1 | 2010/04/23 12:09:18 | 2010.04.23 AD at 12:09:18 IDT INFO | jvm 1 | 2010/04/23 12:09:23 | 2010.04.23 AD at 12:09:23 IDT INFO | jvm 1 | 2010/04/23 12:09:28 | 2010.04.23 AD at 12:09:28 IDT INFO | jvm 1 | 2010/04/23 12:09:33 | 2010.04.23 AD at 12:09:33 IDT INFO | jvm 1 | 2010/04/23 12:09:38 | 2010.04.23 AD at 12:09:38 IDT INFO | jvm 1 | 2010/04/23 12:09:43 | 2010.04.23 AD at 12:09:43 IDT INFO | jvm 1 | 2010/04/23 12:09:48 | 2010.04.23 AD at 12:09:48 IDT INFO | jvm 1 | 2010/04/23 12:09:53 | 2010.04.23 AD at 12:09:53 IDT INFO | jvm 1 | 2010/04/23 12:09:58 | 2010.04.23 AD at 12:09:58 IDT INFO | jvm 1 | 2010/04/23 12:10:03 | 2010.04.23 AD at 12:10:03 IDT INFO | jvm 1 | 2010/04/23 12:10:08 | 2010.04.23 AD at 12:10:08 IDT INFO | jvm 1 | 2010/04/23 12:10:13 | 2010.04.23 AD at 12:10:13 IDT INFO | jvm 1 | 2010/04/23 12:10:18 | 2010.04.23 AD at 12:10:18 IDT INFO | jvm 1 | 2010/04/23 12:10:23 | 2010.04.23 AD at 12:10:23 IDT INFO | jvm 1 | 2010/04/23 12:10:28 | 2010.04.23 AD at 12:10:28 IDT INFO | jvm 1 | 2010/04/23 12:10:33 | 2010.04.23 AD at 12:10:33 IDT INFO | jvm 1 | 2010/04/23 12:10:38 | 2010.04.23 AD at 12:10:38 IDT INFO | jvm 1 | 2010/04/23 12:10:43 | 2010.04.23 AD at 12:10:43 IDT INFO | jvm 1 | 2010/04/23 12:10:48 | 2010.04.23 AD at 12:10:48 IDT INFO | jvm 1 | 2010/04/23 12:10:53 | 2010.04.23 AD at 12:10:53 IDT INFO | jvm 1 | 2010/04/23 12:10:58 | 2010.04.23 AD at 12:10:58 IDT INFO | jvm 1 | 2010/04/23 12:11:04 | 2010.04.23 AD at 12:11:03 IDT INFO | jvm 1 | 2010/04/23 12:11:08 | 2010.04.23 AD at 12:11:08 IDT INFO | jvm 1 | 2010/04/23 12:11:13 | 2010.04.23 AD at 12:11:13 IDT INFO | jvm 1 | 2010/04/23 12:11:18 | 2010.04.23 AD at 12:11:18 IDT INFO | jvm 1 | 2010/04/23 12:11:24 | 2010.04.23 AD at 12:11:23 IDT INFO | jvm 1 | 2010/04/23 12:11:29 | 2010.04.23 AD at 12:11:28 IDT INFO | jvm 1 | 2010/04/23 12:11:34 | 2010.04.23 AD at 12:11:33 IDT INFO | jvm 1 | 2010/04/23 12:11:39 | 2010.04.23 AD at 12:11:38 IDT INFO | jvm 1 | 2010/04/23 12:11:44 | 2010.04.23 AD at 12:11:43 IDT INFO | jvm 1 | 2010/04/23 12:11:49 | 2010.04.23 AD at 12:11:48 IDT INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Read Timed out. (Last Ping was 596300 milliseconds ago) INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager: JVM did not exit. Give up. INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded java.util.IdentityHashMap$KeySet from /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded java.util.IdentityHashMap$IdentityHashMapIterator from /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded java.util.IdentityHashMap$KeyIterator from /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: ShutdownHook started INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Send a packet STOP : 0 INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Stopped checking for control events. DEBUG | wrapperp | 2010/04/23 12:11:52 | read a packet STOP : 0 DEBUG | wrapper | 2010/04/23 12:11:52 | JVM requested a shutdown. (0) DEBUG | wrapper | 2010/04/23 12:11:52 | wrapperStopProcess(0) called. DEBUG | wrapper | 2010/04/23 12:11:52 | Sending stop signal to JVM DEBUG | wrapperp | 2010/04/23 12:11:52 | send a packet STOP : NULL INFO | jvm 1 | 2010/04/23 12:11:53 | [Loaded org.tanukisoftware.wrapper.WrapperManager$8 from file:/opt/javatest/wrapper.jar] INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Thread, Wrapper-Shutdown-Hook, handling the shutdown process. INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: calling listener.stop() INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: returned from listener.stop() -> 0 INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: shutdownJVM(0) Thread:Wrapper-Shutdown-Hook INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: wait for 0 shutdown locs to be released. INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Send a packet STOPPED : 0 DEBUG | wrapperp | 2010/04/23 12:11:53 | read a packet STOPPED : 0 DEBUG | wrapper | 2010/04/23 12:11:53 | JVM signalled that it was stopped. INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Closing socket. DEBUG | wrapperp | 2010/04/23 12:11:53 | socket read no code (closed?). INFO | jvm 1 | 2010/04/23 12:11:54 | 2010.04.23 AD at 12:11:53 IDT INFO | jvm 1 | 2010/04/23 12:11:54 | WrapperManager Debug: ShutdownHook complete DEBUG | wrapper | 2010/04/23 12:11:55 | Signal trapped. Details: DEBUG | wrapper | 2010/04/23 12:11:55 | signal number=18 (SIGCHLD), source="unknown" DEBUG | wrapper | 2010/04/23 12:11:55 | Received SIGCHLD, checking JVM process status. DEBUG | wrapper | 2010/04/23 12:11:55 | JVM process exited with a code of 1, setting the wrapper exit code to 1. DEBUG | wrapper | 2010/04/23 12:11:55 | JVM exited normally. STATUS | wrapper | 2010/04/23 12:11:55 | <-- Wrapper Stopped i'm attaching the whole app again On Fri, Apr 23, 2010 at 9:49 AM, Leif Mortenson <le...@ta...>wrote: > Tomer, > Thank you for the logs. I am looking through them. > > One thing that I do see is that your native library is not being > loaded correctly: > --- > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: WARNING - > Unable to load the Wrapper's native library 'libwrapper.so'. > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > The file is located on the path at the following location but > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > could not be loaded: > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > /opt/javatest/./libwrapper.so > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > Please verify that the file is readable by the current user > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > and that the file has not been corrupted in any way. > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > One common cause of this problem is running a 32-bit version > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: of > the Wrapper with a 64-bit version of Java, or vica versa. > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > This is a 32-bit JVM. > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > Reported cause: > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > /opt/javatest/libwrapper.so: ld.so.1: java: fatal: > /opt/javatest/libwrapper.so: wrong ELF class: ELFCLASS64 (Possible > cause: architecture word width misma$ > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: > System signals will not be handled correctly. > --- > > There are a few things in the logs which are confusing me as well: > 1) In the first post that you sent, there were log entries like the > following stating that the Wrapper had not pinged the JVM for almost 5 > minutes and that the socket read times out. This actually made some > sense: > --- > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read > Timed out. (Last Ping was 298400 milliseconds ago) > --- > In this latest log file however, this time has become 0 in all cases: > --- > INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read > Timed out. (Last Ping was 0 milliseconds ago) > --- > Thar time is calculated using the internal timing mechanism of the the > Wrapper and the only way that it could be 0 is if the WrapperManager's > Event Monitor thread was not running. > I can see that that thread started because of the following line: > --- > INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager Debug: > Control event monitor thread started. > --- > There is no message that it was ever stopped however which doesn't make > sense. > > 2) You have set your wrapper.ping.timeout=300. This means that > regardless of what may go wrong in the JVM, the Wrapper should be > killing the JVM if it fails to respond to a ping within 300 seconds. > >From the following subset of your logs, you can see that the Wrapper > is allowing the JVM to run for MUCH longer than the configured 300 > seconds: > --- > DEBUG | wrapperp | 2010/04/22 18:26:19 | read a packet PING : ping > INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read > Timed out. (Last Ping was 0 milliseconds ago) > INFO | jvm 1 | 2010/04/22 18:36:19 | WrapperManager Debug: Read > Timed out. (Last Ping was 0 milliseconds ago) > ... > INFO | jvm 1 | 2010/04/22 19:21:19 | WrapperManager Debug: Read > Timed out. (Last Ping was 0 milliseconds ago) > INFO | jvm 1 | 2010/04/22 19:26:19 | WrapperManager Debug: Read > Timed out. (Last Ping was 0 milliseconds ago) > INFO | jvm 1 | 2010/04/22 19:31:19 | WrapperManager Debug: Read > Timed out. (Last Ping was 0 milliseconds ago) > --- > Because the ping timeout is 300 seconds, the WrapperManager's socket > read is correctly timing out every 300 seconds perfectly. > I would question whether or not there was a problem in the Wrapper > itself except for the fact that the thread that is checking for ping > timeouts is the same thread that is processing the JVM's log output. > The log output is making it to the log file so it is working > correctly. > > We are still spending a lot of time trying to get to the bottom of > this, but because this is the Community Edition, I need to ask if this > is the binary that we released, or if this is a version that you have > compiled from source yourself, possibly after some modifications? > Knowing that it is an unmodified binary would be helpful in tracking > down the cause of this issue. > > The code involved in the JVM has been unmodified since 2003 and there > have been no other reports of problems when using the Tick Timer. The > old System based timed was susceptible to high system load, but such > loads slow down the rate of the ticks and avoid encountering any > timeouts. (This doesn't mean that there isn't a problem, just that > you are the first case I have seen.) > > We will run some tests using your test class on Solaris today as well. > > Thanks in advance, > Cheers, > Leif > > On Fri, Apr 23, 2010 at 1:52 AM, Tomer B <tom...@gm...> wrote: > > Hi, > > > > I created a dummy java app that prints the time every 5 seconds and > > allocates some memory. > > I ran it for some time and although it did not halt I got the same > behaviour > > with manners of the jvm stopped receiving pings from wrapper after some > > time! (which is what happens to my server). > > I'm attaching the java app code + conf + logs > > > > Attaching a zip containing the whole thing. > > <snip> > > > ------------------------------------------------------------------------------ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Tomer B <tom...@gm...> - 2010-04-23 09:57:20
|
About the wrapper version I didn't compile anything I downloaded it from web site its: wrapper-solaris-x86-64-3.4.0.tar.gz size: 336,037 On Fri, Apr 23, 2010 at 12:54 PM, Tomer B <tom...@gm...> wrote: > Hi, > Now the whole app loads fine (no warning as before about 32-64 bit > mismatch). I got the timeout and shutdown. In the logs i'm sending there > are a couple of startups see last one. > > > STATUS | wrapper | 2010/04/23 11:43:49 | Java Service Wrapper Community > Edition 64-bit 3.4.0 > STATUS | wrapper | 2010/04/23 11:43:49 | Copyright (C) 1999-2010 Tanuki > Software, Ltd. All Rights Reserved. > STATUS | wrapper | 2010/04/23 11:43:49 | > http://wrapper.tanukisoftware.org > STATUS | wrapper | 2010/04/23 11:43:49 | > DEBUG | wrapper | 2010/04/23 11:43:49 | Release time: 2010/03/16 00:00:00 > DEBUG | wrapper | 2010/04/23 11:43:49 | Build time: 2010/03/15 14:49:00 > DEBUG | wrapper | 2010/04/23 11:43:49 | Timezone: IST (IDT) Offset: > -7200, hasDaylight: 1 > DEBUG | wrapper | 2010/04/23 11:43:49 | Using tick timer. > DEBUG | wrapper | 2010/04/23 11:43:49 | active log file changed: > ./server-wrapper.log > DEBUG | wrapper | 2010/04/23 11:43:49 | active log file changed: > ./server-wrapper.log > DEBUG | wrapperp | 2010/04/23 11:43:49 | server listening on port 32000. > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[0] : > /usr/jdk/instances/jdk1.6.0/bin/java > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[1] : -d64 > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[2] : -Xloggc:gc.txt > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[3] : > -Dsun.rmi.dgc.client.gcInterval=0x7ffffffffffffffe > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[4] : > -Dsun.rmi.dgc.server.gcInterval=0x7ffffffffffffffe > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[5] : > -Dsun.net.inetaddr.ttl=0 > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[6] : > -Dsun.net.client.defaultConnectTimeout=30000 > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[7] : > -Dsun.net.client.defaultReadTimeout=120000 > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[8] : -Dummy > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[9] : -XX:+PrintGCDetails > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[10] : > -XX:+PrintGCTimeStamps > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[11] : > -XX:MaxPermSize=256M > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[12] : > -DentityExpansionLimit=256000 > DEBUG | wrapper | 2010/04/23 11:43:49 | Command[13] : -verbose > > DEBUG | wrapperp | 2010/04/23 12:01:23 | read a packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:27 | send a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:28 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:28 | WrapperManager Debug: Send a > packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:28 | 2010.04.23 AD at 12:01:28 IDT > DEBUG | wrapperp | 2010/04/23 12:01:28 | read a packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:32 | send a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:32 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:32 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:32 | read a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:33 | 2010.04.23 AD at 12:01:33 IDT > DEBUG | wrapperp | 2010/04/23 12:01:36 | send a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:36 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:36 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:36 | read a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:38 | 2010.04.23 AD at 12:01:38 IDT > DEBUG | wrapperp | 2010/04/23 12:01:40 | send a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:40 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:40 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:40 | read a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:43 | 2010.04.23 AD at 12:01:43 IDT > DEBUG | wrapperp | 2010/04/23 12:01:44 | send a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:44 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:44 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:44 | read a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:48 | 2010.04.23 AD at 12:01:48 IDT > DEBUG | wrapperp | 2010/04/23 12:01:48 | send a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:48 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:48 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:48 | read a packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:52 | send a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:52 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:52 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/23 12:01:52 | read a packet PING : ping > INFO | jvm 1 | 2010/04/23 12:01:53 | 2010.04.23 AD at 12:01:53 IDT > INFO | jvm 1 | 2010/04/23 12:01:58 | 2010.04.23 AD at 12:01:58 IDT > INFO | jvm 1 | 2010/04/23 12:02:03 | 2010.04.23 AD at 12:02:03 IDT > INFO | jvm 1 | 2010/04/23 12:02:08 | 2010.04.23 AD at 12:02:08 IDT > INFO | jvm 1 | 2010/04/23 12:02:13 | 2010.04.23 AD at 12:02:13 IDT > INFO | jvm 1 | 2010/04/23 12:02:18 | 2010.04.23 AD at 12:02:18 IDT > INFO | jvm 1 | 2010/04/23 12:02:23 | 2010.04.23 AD at 12:02:23 IDT > INFO | jvm 1 | 2010/04/23 12:02:28 | 2010.04.23 AD at 12:02:28 IDT > INFO | jvm 1 | 2010/04/23 12:02:33 | 2010.04.23 AD at 12:02:33 IDT > INFO | jvm 1 | 2010/04/23 12:02:38 | 2010.04.23 AD at 12:02:38 IDT > INFO | jvm 1 | 2010/04/23 12:02:43 | 2010.04.23 AD at 12:02:43 IDT > INFO | jvm 1 | 2010/04/23 12:02:48 | 2010.04.23 AD at 12:02:48 IDT > INFO | jvm 1 | 2010/04/23 12:02:53 | 2010.04.23 AD at 12:02:53 IDT > INFO | jvm 1 | 2010/04/23 12:02:58 | 2010.04.23 AD at 12:02:58 IDT > INFO | jvm 1 | 2010/04/23 12:03:03 | 2010.04.23 AD at 12:03:03 IDT > INFO | jvm 1 | 2010/04/23 12:03:08 | 2010.04.23 AD at 12:03:08 IDT > INFO | jvm 1 | 2010/04/23 12:03:13 | 2010.04.23 AD at 12:03:13 IDT > INFO | jvm 1 | 2010/04/23 12:03:18 | 2010.04.23 AD at 12:03:18 IDT > INFO | jvm 1 | 2010/04/23 12:03:23 | 2010.04.23 AD at 12:03:23 IDT > INFO | jvm 1 | 2010/04/23 12:03:28 | 2010.04.23 AD at 12:03:28 IDT > INFO | jvm 1 | 2010/04/23 12:03:33 | 2010.04.23 AD at 12:03:33 IDT > INFO | jvm 1 | 2010/04/23 12:03:38 | 2010.04.23 AD at 12:03:38 IDT > INFO | jvm 1 | 2010/04/23 12:03:43 | 2010.04.23 AD at 12:03:43 IDT > INFO | jvm 1 | 2010/04/23 12:03:48 | 2010.04.23 AD at 12:03:48 IDT > INFO | jvm 1 | 2010/04/23 12:03:53 | 2010.04.23 AD at 12:03:53 IDT > INFO | jvm 1 | 2010/04/23 12:03:58 | 2010.04.23 AD at 12:03:58 IDT > INFO | jvm 1 | 2010/04/23 12:04:03 | 2010.04.23 AD at 12:04:03 IDT > INFO | jvm 1 | 2010/04/23 12:04:08 | 2010.04.23 AD at 12:04:08 IDT > INFO | jvm 1 | 2010/04/23 12:04:13 | 2010.04.23 AD at 12:04:13 IDT > INFO | jvm 1 | 2010/04/23 12:04:18 | 2010.04.23 AD at 12:04:18 IDT > INFO | jvm 1 | 2010/04/23 12:04:23 | 2010.04.23 AD at 12:04:23 IDT > INFO | jvm 1 | 2010/04/23 12:04:28 | 2010.04.23 AD at 12:04:28 IDT > INFO | jvm 1 | 2010/04/23 12:04:33 | 2010.04.23 AD at 12:04:33 IDT > INFO | jvm 1 | 2010/04/23 12:04:38 | 2010.04.23 AD at 12:04:38 IDT > INFO | jvm 1 | 2010/04/23 12:04:43 | 2010.04.23 AD at 12:04:43 IDT > INFO | jvm 1 | 2010/04/23 12:04:48 | 2010.04.23 AD at 12:04:48 IDT > INFO | jvm 1 | 2010/04/23 12:04:53 | 2010.04.23 AD at 12:04:53 IDT > INFO | jvm 1 | 2010/04/23 12:04:58 | 2010.04.23 AD at 12:04:58 IDT > INFO | jvm 1 | 2010/04/23 12:05:03 | 2010.04.23 AD at 12:05:03 IDT > INFO | jvm 1 | 2010/04/23 12:05:08 | 2010.04.23 AD at 12:05:08 IDT > INFO | jvm 1 | 2010/04/23 12:05:13 | 2010.04.23 AD at 12:05:13 IDT > INFO | jvm 1 | 2010/04/23 12:05:18 | 2010.04.23 AD at 12:05:18 IDT > INFO | jvm 1 | 2010/04/23 12:05:23 | 2010.04.23 AD at 12:05:23 IDT > INFO | jvm 1 | 2010/04/23 12:05:28 | 2010.04.23 AD at 12:05:28 IDT > INFO | jvm 1 | 2010/04/23 12:05:33 | 2010.04.23 AD at 12:05:33 IDT > INFO | jvm 1 | 2010/04/23 12:05:38 | 2010.04.23 AD at 12:05:38 IDT > INFO | jvm 1 | 2010/04/23 12:05:43 | 2010.04.23 AD at 12:05:43 IDT > INFO | jvm 1 | 2010/04/23 12:05:48 | 2010.04.23 AD at 12:05:48 IDT > INFO | jvm 1 | 2010/04/23 12:05:53 | 2010.04.23 AD at 12:05:53 IDT > INFO | jvm 1 | 2010/04/23 12:05:58 | 2010.04.23 AD at 12:05:58 IDT > INFO | jvm 1 | 2010/04/23 12:06:03 | 2010.04.23 AD at 12:06:03 IDT > INFO | jvm 1 | 2010/04/23 12:06:08 | 2010.04.23 AD at 12:06:08 IDT > INFO | jvm 1 | 2010/04/23 12:06:13 | 2010.04.23 AD at 12:06:13 IDT > INFO | jvm 1 | 2010/04/23 12:06:18 | 2010.04.23 AD at 12:06:18 IDT > INFO | jvm 1 | 2010/04/23 12:06:23 | 2010.04.23 AD at 12:06:23 IDT > INFO | jvm 1 | 2010/04/23 12:06:28 | 2010.04.23 AD at 12:06:28 IDT > INFO | jvm 1 | 2010/04/23 12:06:33 | 2010.04.23 AD at 12:06:33 IDT > INFO | jvm 1 | 2010/04/23 12:06:38 | 2010.04.23 AD at 12:06:38 IDT > INFO | jvm 1 | 2010/04/23 12:06:43 | 2010.04.23 AD at 12:06:43 IDT > INFO | jvm 1 | 2010/04/23 12:06:48 | 2010.04.23 AD at 12:06:48 IDT > INFO | jvm 1 | 2010/04/23 12:06:52 | [Loaded > java.net.SocketTimeoutException from > /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] > INFO | jvm 1 | 2010/04/23 12:06:52 | [Loaded > sun.net.ConnectionResetException from > /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] > INFO | jvm 1 | 2010/04/23 12:06:52 | WrapperManager Debug: Read Timed > out. (Last Ping was 298100 milliseconds ago) > INFO | jvm 1 | 2010/04/23 12:06:53 | 2010.04.23 AD at 12:06:53 IDT > INFO | jvm 1 | 2010/04/23 12:06:58 | 2010.04.23 AD at 12:06:58 IDT > INFO | jvm 1 | 2010/04/23 12:07:03 | 2010.04.23 AD at 12:07:03 IDT > INFO | jvm 1 | 2010/04/23 12:07:08 | 2010.04.23 AD at 12:07:08 IDT > INFO | jvm 1 | 2010/04/23 12:07:13 | 2010.04.23 AD at 12:07:13 IDT > INFO | jvm 1 | 2010/04/23 12:07:18 | 2010.04.23 AD at 12:07:18 IDT > INFO | jvm 1 | 2010/04/23 12:07:23 | 2010.04.23 AD at 12:07:23 IDT > INFO | jvm 1 | 2010/04/23 12:07:28 | 2010.04.23 AD at 12:07:28 IDT > INFO | jvm 1 | 2010/04/23 12:07:33 | 2010.04.23 AD at 12:07:33 IDT > INFO | jvm 1 | 2010/04/23 12:07:38 | 2010.04.23 AD at 12:07:38 IDT > INFO | jvm 1 | 2010/04/23 12:07:43 | 2010.04.23 AD at 12:07:43 IDT > INFO | jvm 1 | 2010/04/23 12:07:48 | 2010.04.23 AD at 12:07:48 IDT > INFO | jvm 1 | 2010/04/23 12:07:53 | 2010.04.23 AD at 12:07:53 IDT > INFO | jvm 1 | 2010/04/23 12:07:58 | 2010.04.23 AD at 12:07:58 IDT > INFO | jvm 1 | 2010/04/23 12:08:03 | 2010.04.23 AD at 12:08:03 IDT > INFO | jvm 1 | 2010/04/23 12:08:08 | 2010.04.23 AD at 12:08:08 IDT > INFO | jvm 1 | 2010/04/23 12:08:13 | 2010.04.23 AD at 12:08:13 IDT > INFO | jvm 1 | 2010/04/23 12:08:18 | 2010.04.23 AD at 12:08:18 IDT > INFO | jvm 1 | 2010/04/23 12:08:23 | 2010.04.23 AD at 12:08:23 IDT > INFO | jvm 1 | 2010/04/23 12:08:28 | 2010.04.23 AD at 12:08:28 IDT > INFO | jvm 1 | 2010/04/23 12:08:33 | 2010.04.23 AD at 12:08:33 IDT > INFO | jvm 1 | 2010/04/23 12:08:38 | 2010.04.23 AD at 12:08:38 IDT > INFO | jvm 1 | 2010/04/23 12:08:43 | 2010.04.23 AD at 12:08:43 IDT > INFO | jvm 1 | 2010/04/23 12:08:48 | 2010.04.23 AD at 12:08:48 IDT > INFO | jvm 1 | 2010/04/23 12:08:53 | 2010.04.23 AD at 12:08:53 IDT > INFO | jvm 1 | 2010/04/23 12:08:58 | 2010.04.23 AD at 12:08:58 IDT > INFO | jvm 1 | 2010/04/23 12:09:03 | 2010.04.23 AD at 12:09:03 IDT > INFO | jvm 1 | 2010/04/23 12:09:08 | 2010.04.23 AD at 12:09:08 IDT > INFO | jvm 1 | 2010/04/23 12:09:13 | 2010.04.23 AD at 12:09:13 IDT > INFO | jvm 1 | 2010/04/23 12:09:18 | 2010.04.23 AD at 12:09:18 IDT > INFO | jvm 1 | 2010/04/23 12:09:23 | 2010.04.23 AD at 12:09:23 IDT > INFO | jvm 1 | 2010/04/23 12:09:28 | 2010.04.23 AD at 12:09:28 IDT > INFO | jvm 1 | 2010/04/23 12:09:33 | 2010.04.23 AD at 12:09:33 IDT > INFO | jvm 1 | 2010/04/23 12:09:38 | 2010.04.23 AD at 12:09:38 IDT > INFO | jvm 1 | 2010/04/23 12:09:43 | 2010.04.23 AD at 12:09:43 IDT > INFO | jvm 1 | 2010/04/23 12:09:48 | 2010.04.23 AD at 12:09:48 IDT > INFO | jvm 1 | 2010/04/23 12:09:53 | 2010.04.23 AD at 12:09:53 IDT > INFO | jvm 1 | 2010/04/23 12:09:58 | 2010.04.23 AD at 12:09:58 IDT > INFO | jvm 1 | 2010/04/23 12:10:03 | 2010.04.23 AD at 12:10:03 IDT > INFO | jvm 1 | 2010/04/23 12:10:08 | 2010.04.23 AD at 12:10:08 IDT > INFO | jvm 1 | 2010/04/23 12:10:13 | 2010.04.23 AD at 12:10:13 IDT > INFO | jvm 1 | 2010/04/23 12:10:18 | 2010.04.23 AD at 12:10:18 IDT > INFO | jvm 1 | 2010/04/23 12:10:23 | 2010.04.23 AD at 12:10:23 IDT > INFO | jvm 1 | 2010/04/23 12:10:28 | 2010.04.23 AD at 12:10:28 IDT > INFO | jvm 1 | 2010/04/23 12:10:33 | 2010.04.23 AD at 12:10:33 IDT > INFO | jvm 1 | 2010/04/23 12:10:38 | 2010.04.23 AD at 12:10:38 IDT > INFO | jvm 1 | 2010/04/23 12:10:43 | 2010.04.23 AD at 12:10:43 IDT > INFO | jvm 1 | 2010/04/23 12:10:48 | 2010.04.23 AD at 12:10:48 IDT > INFO | jvm 1 | 2010/04/23 12:10:53 | 2010.04.23 AD at 12:10:53 IDT > INFO | jvm 1 | 2010/04/23 12:10:58 | 2010.04.23 AD at 12:10:58 IDT > INFO | jvm 1 | 2010/04/23 12:11:04 | 2010.04.23 AD at 12:11:03 IDT > INFO | jvm 1 | 2010/04/23 12:11:08 | 2010.04.23 AD at 12:11:08 IDT > INFO | jvm 1 | 2010/04/23 12:11:13 | 2010.04.23 AD at 12:11:13 IDT > INFO | jvm 1 | 2010/04/23 12:11:18 | 2010.04.23 AD at 12:11:18 IDT > INFO | jvm 1 | 2010/04/23 12:11:24 | 2010.04.23 AD at 12:11:23 IDT > INFO | jvm 1 | 2010/04/23 12:11:29 | 2010.04.23 AD at 12:11:28 IDT > INFO | jvm 1 | 2010/04/23 12:11:34 | 2010.04.23 AD at 12:11:33 IDT > INFO | jvm 1 | 2010/04/23 12:11:39 | 2010.04.23 AD at 12:11:38 IDT > INFO | jvm 1 | 2010/04/23 12:11:44 | 2010.04.23 AD at 12:11:43 IDT > INFO | jvm 1 | 2010/04/23 12:11:49 | 2010.04.23 AD at 12:11:48 IDT > INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Read Timed > out. (Last Ping was 596300 milliseconds ago) > INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager: JVM did not > exit. Give up. > INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded > java.util.IdentityHashMap$KeySet from > /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] > INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded > java.util.IdentityHashMap$IdentityHashMapIterator from > /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] > INFO | jvm 1 | 2010/04/23 12:11:52 | [Loaded > java.util.IdentityHashMap$KeyIterator from > /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] > INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: > ShutdownHook started > INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Send a > packet STOP : 0 > INFO | jvm 1 | 2010/04/23 12:11:52 | WrapperManager Debug: Stopped > checking for control events. > DEBUG | wrapperp | 2010/04/23 12:11:52 | read a packet STOP : 0 > DEBUG | wrapper | 2010/04/23 12:11:52 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2010/04/23 12:11:52 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2010/04/23 12:11:52 | Sending stop signal to JVM > DEBUG | wrapperp | 2010/04/23 12:11:52 | send a packet STOP : NULL > INFO | jvm 1 | 2010/04/23 12:11:53 | [Loaded > org.tanukisoftware.wrapper.WrapperManager$8 from > file:/opt/javatest/wrapper.jar] > INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Thread, > Wrapper-Shutdown-Hook, handling the shutdown process. > INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: calling > listener.stop() > INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: returned > from listener.stop() -> 0 > INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: wait for 0 > shutdown locs to be released. > INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Send a > packet STOPPED : 0 > DEBUG | wrapperp | 2010/04/23 12:11:53 | read a packet STOPPED : 0 > DEBUG | wrapper | 2010/04/23 12:11:53 | JVM signalled that it was > stopped. > INFO | jvm 1 | 2010/04/23 12:11:53 | WrapperManager Debug: Closing > socket. > DEBUG | wrapperp | 2010/04/23 12:11:53 | socket read no code (closed?). > INFO | jvm 1 | 2010/04/23 12:11:54 | 2010.04.23 AD at 12:11:53 IDT > INFO | jvm 1 | 2010/04/23 12:11:54 | WrapperManager Debug: > ShutdownHook complete > DEBUG | wrapper | 2010/04/23 12:11:55 | Signal trapped. Details: > DEBUG | wrapper | 2010/04/23 12:11:55 | signal number=18 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2010/04/23 12:11:55 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2010/04/23 12:11:55 | JVM process exited with a code of > 1, setting the wrapper exit code to 1. > DEBUG | wrapper | 2010/04/23 12:11:55 | JVM exited normally. > STATUS | wrapper | 2010/04/23 12:11:55 | <-- Wrapper Stopped > > i'm attaching the whole app again > > > > On Fri, Apr 23, 2010 at 9:49 AM, Leif Mortenson <le...@ta...>wrote: > >> Tomer, >> Thank you for the logs. I am looking through them. >> >> One thing that I do see is that your native library is not being >> loaded correctly: >> --- >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: WARNING - >> Unable to load the Wrapper's native library 'libwrapper.so'. >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> The file is located on the path at the following location but >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> could not be loaded: >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> /opt/javatest/./libwrapper.so >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> Please verify that the file is readable by the current user >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> and that the file has not been corrupted in any way. >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> One common cause of this problem is running a 32-bit version >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: of >> the Wrapper with a 64-bit version of Java, or vica versa. >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> This is a 32-bit JVM. >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> Reported cause: >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> /opt/javatest/libwrapper.so: ld.so.1: java: fatal: >> /opt/javatest/libwrapper.so: wrong ELF class: ELFCLASS64 (Possible >> cause: architecture word width misma$ >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: >> System signals will not be handled correctly. >> --- >> >> There are a few things in the logs which are confusing me as well: >> 1) In the first post that you sent, there were log entries like the >> following stating that the Wrapper had not pinged the JVM for almost 5 >> minutes and that the socket read times out. This actually made some >> sense: >> --- >> INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read >> Timed out. (Last Ping was 298400 milliseconds ago) >> --- >> In this latest log file however, this time has become 0 in all cases: >> --- >> INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read >> Timed out. (Last Ping was 0 milliseconds ago) >> --- >> Thar time is calculated using the internal timing mechanism of the the >> Wrapper and the only way that it could be 0 is if the WrapperManager's >> Event Monitor thread was not running. >> I can see that that thread started because of the following line: >> --- >> INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager Debug: >> Control event monitor thread started. >> --- >> There is no message that it was ever stopped however which doesn't make >> sense. >> >> 2) You have set your wrapper.ping.timeout=300. This means that >> regardless of what may go wrong in the JVM, the Wrapper should be >> killing the JVM if it fails to respond to a ping within 300 seconds. >> >From the following subset of your logs, you can see that the Wrapper >> is allowing the JVM to run for MUCH longer than the configured 300 >> seconds: >> --- >> DEBUG | wrapperp | 2010/04/22 18:26:19 | read a packet PING : ping >> INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read >> Timed out. (Last Ping was 0 milliseconds ago) >> INFO | jvm 1 | 2010/04/22 18:36:19 | WrapperManager Debug: Read >> Timed out. (Last Ping was 0 milliseconds ago) >> ... >> INFO | jvm 1 | 2010/04/22 19:21:19 | WrapperManager Debug: Read >> Timed out. (Last Ping was 0 milliseconds ago) >> INFO | jvm 1 | 2010/04/22 19:26:19 | WrapperManager Debug: Read >> Timed out. (Last Ping was 0 milliseconds ago) >> INFO | jvm 1 | 2010/04/22 19:31:19 | WrapperManager Debug: Read >> Timed out. (Last Ping was 0 milliseconds ago) >> --- >> Because the ping timeout is 300 seconds, the WrapperManager's socket >> read is correctly timing out every 300 seconds perfectly. >> I would question whether or not there was a problem in the Wrapper >> itself except for the fact that the thread that is checking for ping >> timeouts is the same thread that is processing the JVM's log output. >> The log output is making it to the log file so it is working >> correctly. >> >> We are still spending a lot of time trying to get to the bottom of >> this, but because this is the Community Edition, I need to ask if this >> is the binary that we released, or if this is a version that you have >> compiled from source yourself, possibly after some modifications? >> Knowing that it is an unmodified binary would be helpful in tracking >> down the cause of this issue. >> >> The code involved in the JVM has been unmodified since 2003 and there >> have been no other reports of problems when using the Tick Timer. The >> old System based timed was susceptible to high system load, but such >> loads slow down the rate of the ticks and avoid encountering any >> timeouts. (This doesn't mean that there isn't a problem, just that >> you are the first case I have seen.) >> >> We will run some tests using your test class on Solaris today as well. >> >> Thanks in advance, >> Cheers, >> Leif >> >> On Fri, Apr 23, 2010 at 1:52 AM, Tomer B <tom...@gm...> wrote: >> > Hi, >> > >> > I created a dummy java app that prints the time every 5 seconds and >> > allocates some memory. >> > I ran it for some time and although it did not halt I got the same >> behaviour >> > with manners of the jvm stopped receiving pings from wrapper after some >> > time! (which is what happens to my server). >> > I'm attaching the java app code + conf + logs >> > >> > Attaching a zip containing the whole thing. >> >> <snip> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > > |
|
From: Leif M. <le...@ta...> - 2010-04-23 06:50:06
|
Tomer, Thank you for the logs. I am looking through them. One thing that I do see is that your native library is not being loaded correctly: --- INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'libwrapper.so'. INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: The file is located on the path at the following location but INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: could not be loaded: INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: /opt/javatest/./libwrapper.so INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: Please verify that the file is readable by the current user INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: and that the file has not been corrupted in any way. INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: One common cause of this problem is running a 32-bit version INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa. INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: This is a 32-bit JVM. INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: Reported cause: INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: /opt/javatest/libwrapper.so: ld.so.1: java: fatal: /opt/javatest/libwrapper.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width misma$ INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager: System signals will not be handled correctly. --- There are a few things in the logs which are confusing me as well: 1) In the first post that you sent, there were log entries like the following stating that the Wrapper had not pinged the JVM for almost 5 minutes and that the socket read times out. This actually made some sense: --- INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read Timed out. (Last Ping was 298400 milliseconds ago) --- In this latest log file however, this time has become 0 in all cases: --- INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read Timed out. (Last Ping was 0 milliseconds ago) --- Thar time is calculated using the internal timing mechanism of the the Wrapper and the only way that it could be 0 is if the WrapperManager's Event Monitor thread was not running. I can see that that thread started because of the following line: --- INFO | jvm 1 | 2010/04/22 16:21:24 | WrapperManager Debug: Control event monitor thread started. --- There is no message that it was ever stopped however which doesn't make sense. 2) You have set your wrapper.ping.timeout=300. This means that regardless of what may go wrong in the JVM, the Wrapper should be killing the JVM if it fails to respond to a ping within 300 seconds. >From the following subset of your logs, you can see that the Wrapper is allowing the JVM to run for MUCH longer than the configured 300 seconds: --- DEBUG | wrapperp | 2010/04/22 18:26:19 | read a packet PING : ping INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read Timed out. (Last Ping was 0 milliseconds ago) INFO | jvm 1 | 2010/04/22 18:36:19 | WrapperManager Debug: Read Timed out. (Last Ping was 0 milliseconds ago) ... INFO | jvm 1 | 2010/04/22 19:21:19 | WrapperManager Debug: Read Timed out. (Last Ping was 0 milliseconds ago) INFO | jvm 1 | 2010/04/22 19:26:19 | WrapperManager Debug: Read Timed out. (Last Ping was 0 milliseconds ago) INFO | jvm 1 | 2010/04/22 19:31:19 | WrapperManager Debug: Read Timed out. (Last Ping was 0 milliseconds ago) --- Because the ping timeout is 300 seconds, the WrapperManager's socket read is correctly timing out every 300 seconds perfectly. I would question whether or not there was a problem in the Wrapper itself except for the fact that the thread that is checking for ping timeouts is the same thread that is processing the JVM's log output. The log output is making it to the log file so it is working correctly. We are still spending a lot of time trying to get to the bottom of this, but because this is the Community Edition, I need to ask if this is the binary that we released, or if this is a version that you have compiled from source yourself, possibly after some modifications? Knowing that it is an unmodified binary would be helpful in tracking down the cause of this issue. The code involved in the JVM has been unmodified since 2003 and there have been no other reports of problems when using the Tick Timer. The old System based timed was susceptible to high system load, but such loads slow down the rate of the ticks and avoid encountering any timeouts. (This doesn't mean that there isn't a problem, just that you are the first case I have seen.) We will run some tests using your test class on Solaris today as well. Thanks in advance, Cheers, Leif On Fri, Apr 23, 2010 at 1:52 AM, Tomer B <tom...@gm...> wrote: > Hi, > > I created a dummy java app that prints the time every 5 seconds and > allocates some memory. > I ran it for some time and although it did not halt I got the same behaviour > with manners of the jvm stopped receiving pings from wrapper after some > time! (which is what happens to my server). > I'm attaching the java app code + conf + logs > > Attaching a zip containing the whole thing. <snip> |
|
From: Tomer B <tom...@gm...> - 2010-04-22 21:37:40
|
This email contained a .zip file attachment. Raytheon does not allow email attachments that are considered likely to contain malicious code. For your protection this attachment has been removed. If this email is from an unknown source, please simply delete this email. If this email was expected, and it is from a known sender, you may follow the below suggested instructions to obtain these types of attachments. + Instruct the sender to enclose the file(s) in a ".zip" compressed file, and rename the ".zip" compressed file with a different extension, such as, ".rtnzip". Password protecting the renamed ".zip" compressed file adds an additional layer of protection. When you receive the file, please rename it with the extension ".zip". Additional instructions and options on how to receive these attachments can be found at: http://security.it.ray.com/antivirus/extensions.html http://security.it.ray.com/news/2007/zipfiles.html Should you have any questions or difficulty with these instructions, please contact the Help Desk at 877.844.4712 --- Hi, I created a dummy java app that prints the time every 5 seconds and allocates some memory. I ran it for some time and although it did not halt I got the same behaviour with manners of the jvm stopped receiving pings from wrapper after some time! (which is what happens to my server). I'm attaching the java app code + conf + logs Attaching a zip containing the whole thing. ################ JavaVMTester.java ################ package com.test.javavmtester; import java.text.SimpleDateFormat; import java.util.Date; import org.tanukisoftware.wrapper.WrapperListener; import org.tanukisoftware.wrapper.WrapperManager; public class JavaVMTester extends Thread implements WrapperListener{ private static byte[] myBytes = new byte[1024 * 1024 * 1200]; public static void main(String[] args) { WrapperManager.start( new JavaVMTester(), args ); } public void run() { while (true) { try { System.out.println(new SimpleDateFormat("yyyy.MM.dd G 'at' HH:mm:ss z").format(new Date())); Thread.sleep(5000); } catch (InterruptedException e) { // TODO Auto-generated catch block e.printStackTrace(); } } } @Override public void controlEvent(int event) { if (WrapperManager.isControlledByNativeWrapper()) { System.out.println("controlled by wrapper"); // The Wrapper will take care of this event } else { // We are not being controlled by the Wrapper, so // handle the event ourselves. if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) || (event == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) || (event == WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)){ System.out.println("controlled by us"); WrapperManager.stop(0); } } } @Override public Integer start(String[] arg0) { JavaVMTester jv = new JavaVMTester(); jv.start(); return null; } @Override public int stop(int arg0) { // TODO Auto-generated method stub return 0; } } ######### server.conf ######### #******************************************************************** # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=com.test.javavmtester.JavaVMTester wrapper.java.command=/bin/java #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Log file to use for wrapper output logging. wrapper.logfile=./server-wrapper.log wrapper.java.classpath.1=./wrapper.jar wrapper.java.classpath.2=. nitial Java Heap Size (in MB) wrapper.java.initmemory=1000 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=2000 # Java Additional Parameters wrapper.java.additional.1=-Xloggc:gc.txt wrapper.java.additional.2=-Dsun.rmi.dgc.client.gcInterval=0x7ffffffffffffffe wrapper.java.additional.3=-Dsun.rmi.dgc.server.gcInterval=0x7ffffffffffffffe wrapper.java.additional.4=-Dsun.net.inetaddr.ttl=0 wrapper.java.additional.5=-Dsun.net.client.defaultConnectTimeout=30000 wrapper.java.additional.6=-Dsun.net.client.defaultReadTimeout=120000 wrapper.java.additional.7=-Dummy wrapper.java.additional.8=-XX:+PrintGCDetails wrapper.java.additional.9=-XX:+PrintGCTimeStamps wrapper.java.additional.10=-XX:MaxPermSize=256M wrapper.java.additional.11=-DentityExpansionLimit=256000 wrapper.java.additional.12=-verbose wrapper.java.additional.13=-XX:-OmitStackTraceInFastThrow wrapper.java.additional.14=-XX:+UseParallelOldGC wrapper.java.additional.15=-Duser.timezone=Asia/Jerusalem wrapper.java.additional.17=-XX:-ReduceInitialCardMarks wrapper.java.additional.18=-Dummy wrapper.java.additional.19=-Dummy wrapper.java.additional.20=-Dummy wrapper.java.additional.21=-Dcom.sun.management.jmxremote.port=13034 wrapper.java.additional.22=-Dcom.sun.management.jmxremote.authenticate=false wrapper.java.additional.23=-Dcom.sun.management.jmxremote.ssl=false wrapper.java.additional.24=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=true wrapper.java.library.path.1=./ # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=DEBUG # Allow the service to interact with the desktop. wrapper.shutdown.timeout=300 wrapper.ping.timeout=300 ########### wrapper.conf ########### #******************************************************************** # Wrapper License Properties (Ignored by Community Edition) #******************************************************************** # Include file problems can be debugged by removing the first '#' # from the following line: ##include.debug #include ../conf/wrapper-license.conf #include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf #******************************************************************** # Wrapper Java Properties #******************************************************************** # Java Application wrapper.java.command=java # Tell the Wrapper to log the full generated Java command line. #wrapper.java.command.loglevel=DEBUG # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=org.tanukisoftware.wrapper.test.Main # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=./wrappertest.jar wrapper.java.classpath.2=./wrapper.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=./ # Java Bits. On applicable platforms, tells the JVM to run in 32 or 64-bit mode. wrapper.java.additional.auto_bits=TRUE # Java Additional Parameters #wrapper.java.additional.1= # Initial Java Heap Size (in MB) #wrapper.java.initmemory=3 # Maximum Java Heap Size (in MB) #wrapper.java.maxmemory=64 # Application parameters. Add parameters as needed starting from 1 #wrapper.app.parameter.1= #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Enables Debug output from the Wrapper. # wrapper.debug=TRUE # Format of output for the console. (See docs for formats) wrapper.console.format=PM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=DEBUG # Log file to use for wrapper output logging. wrapper.logfile=./wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=DEBUG # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m = 10 megabytes. wrapper.logfile.maxsize=0 # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=0 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=USER #******************************************************************** # Wrapper General Properties #******************************************************************** # Allow for the use of non-contiguous numbered properties wrapper.ignore_sequence_gaps=TRUE # Title to use when running as a console wrapper.console.title=Test Wrapper Sample Application #******************************************************************** # Wrapper Windows NT/2000/XP Service Properties #******************************************************************** # WARNING - Do not modify any of these properties when an application # using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The # service can then be reinstalled. # Name of the service wrapper.name=testwrapper # Display name of the service wrapper.displayname=Test Wrapper Sample Application # Description of the service wrapper.description=Test Wrapper Sample Application Description # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1= # Mode in which the service is installed. AUTO_START, DELAY_START or DEMAND_START wrapper.ntservice.starttype=AUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=false ############### server-wrapper.log ############### INFO | jvm 1 | 2010/04/22 18:25:58 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/22 18:25:58 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/22 18:25:58 | read a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:00 | 2010.04.22 AD at 18:26:00 IDT DEBUG | wrapperp | 2010/04/22 18:26:02 | send a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:02 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:02 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/22 18:26:02 | read a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:05 | 2010.04.22 AD at 18:26:05 IDT DEBUG | wrapperp | 2010/04/22 18:26:06 | send a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:07 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:07 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/22 18:26:07 | read a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:10 | 2010.04.22 AD at 18:26:10 IDT DEBUG | wrapperp | 2010/04/22 18:26:11 | send a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:11 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:11 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/22 18:26:11 | read a packet PING : ping DEBUG | wrapperp | 2010/04/22 18:26:15 | send a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:15 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:15 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/22 18:26:15 | read a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:15 | 2010.04.22 AD at 18:26:15 IDT DEBUG | wrapperp | 2010/04/22 18:26:19 | send a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:19 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:19 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/22 18:26:19 | read a packet PING : ping INFO | jvm 1 | 2010/04/22 18:26:20 | 2010.04.22 AD at 18:26:20 IDT INFO | jvm 1 | 2010/04/22 18:26:25 | 2010.04.22 AD at 18:26:25 IDT INFO | jvm 1 | 2010/04/22 18:26:30 | 2010.04.22 AD at 18:26:30 IDT INFO | jvm 1 | 2010/04/22 18:26:35 | 2010.04.22 AD at 18:26:35 IDT INFO | jvm 1 | 2010/04/22 18:26:40 | 2010.04.22 AD at 18:26:40 IDT INFO | jvm 1 | 2010/04/22 18:26:45 | 2010.04.22 AD at 18:26:45 IDT INFO | jvm 1 | 2010/04/22 18:26:50 | 2010.04.22 AD at 18:26:50 IDT INFO | jvm 1 | 2010/04/22 18:26:55 | 2010.04.22 AD at 18:26:55 IDT INFO | jvm 1 | 2010/04/22 18:27:00 | 2010.04.22 AD at 18:27:00 IDT INFO | jvm 1 | 2010/04/22 18:27:05 | 2010.04.22 AD at 18:27:05 IDT INFO | jvm 1 | 2010/04/22 18:27:10 | 2010.04.22 AD at 18:27:10 IDT INFO | jvm 1 | 2010/04/22 18:27:16 | 2010.04.22 AD at 18:27:15 IDT INFO | jvm 1 | 2010/04/22 18:27:21 | 2010.04.22 AD at 18:27:20 IDT INFO | jvm 1 | 2010/04/22 18:27:26 | 2010.04.22 AD at 18:27:25 IDT INFO | jvm 1 | 2010/04/22 18:27:30 | 2010.04.22 AD at 18:27:30 IDT INFO | jvm 1 | 2010/04/22 18:27:35 | 2010.04.22 AD at 18:27:35 IDT INFO | jvm 1 | 2010/04/22 18:27:41 | 2010.04.22 AD at 18:27:40 IDT INFO | jvm 1 | 2010/04/22 18:27:46 | 2010.04.22 AD at 18:27:45 IDT INFO | jvm 1 | 2010/04/22 18:27:51 | 2010.04.22 AD at 18:27:51 IDT INFO | jvm 1 | 2010/04/22 18:27:56 | 2010.04.22 AD at 18:27:56 IDT INFO | jvm 1 | 2010/04/22 18:28:01 | 2010.04.22 AD at 18:28:01 IDT INFO | jvm 1 | 2010/04/22 18:28:06 | 2010.04.22 AD at 18:28:06 IDT INFO | jvm 1 | 2010/04/22 18:28:11 | 2010.04.22 AD at 18:28:11 IDT INFO | jvm 1 | 2010/04/22 18:28:16 | 2010.04.22 AD at 18:28:16 IDT INFO | jvm 1 | 2010/04/22 18:28:21 | 2010.04.22 AD at 18:28:21 IDT INFO | jvm 1 | 2010/04/22 18:28:26 | 2010.04.22 AD at 18:28:26 IDT INFO | jvm 1 | 2010/04/22 18:28:31 | 2010.04.22 AD at 18:28:31 IDT INFO | jvm 1 | 2010/04/22 18:28:36 | 2010.04.22 AD at 18:28:36 IDT INFO | jvm 1 | 2010/04/22 18:28:41 | 2010.04.22 AD at 18:28:41 IDT INFO | jvm 1 | 2010/04/22 18:28:46 | 2010.04.22 AD at 18:28:46 IDT INFO | jvm 1 | 2010/04/22 18:28:51 | 2010.04.22 AD at 18:28:51 IDT INFO | jvm 1 | 2010/04/22 18:28:56 | 2010.04.22 AD at 18:28:56 IDT INFO | jvm 1 | 2010/04/22 18:29:01 | 2010.04.22 AD at 18:29:01 IDT INFO | jvm 1 | 2010/04/22 18:29:06 | 2010.04.22 AD at 18:29:06 IDT INFO | jvm 1 | 2010/04/22 18:29:11 | 2010.04.22 AD at 18:29:11 IDT INFO | jvm 1 | 2010/04/22 18:29:16 | 2010.04.22 AD at 18:29:16 IDT INFO | jvm 1 | 2010/04/22 18:29:21 | 2010.04.22 AD at 18:29:21 IDT INFO | jvm 1 | 2010/04/22 18:29:26 | 2010.04.22 AD at 18:29:26 IDT INFO | jvm 1 | 2010/04/22 18:29:31 | 2010.04.22 AD at 18:29:31 IDT INFO | jvm 1 | 2010/04/22 18:29:36 | 2010.04.22 AD at 18:29:36 IDT INFO | jvm 1 | 2010/04/22 18:29:41 | 2010.04.22 AD at 18:29:41 IDT INFO | jvm 1 | 2010/04/22 18:29:46 | 2010.04.22 AD at 18:29:46 IDT INFO | jvm 1 | 2010/04/22 18:29:51 | 2010.04.22 AD at 18:29:51 IDT INFO | jvm 1 | 2010/04/22 18:29:56 | 2010.04.22 AD at 18:29:56 IDT INFO | jvm 1 | 2010/04/22 18:30:01 | 2010.04.22 AD at 18:30:01 IDT INFO | jvm 1 | 2010/04/22 18:30:06 | 2010.04.22 AD at 18:30:06 IDT INFO | jvm 1 | 2010/04/22 18:30:11 | 2010.04.22 AD at 18:30:11 IDT INFO | jvm 1 | 2010/04/22 18:30:16 | 2010.04.22 AD at 18:30:16 IDT INFO | jvm 1 | 2010/04/22 18:30:21 | 2010.04.22 AD at 18:30:21 IDT INFO | jvm 1 | 2010/04/22 18:30:26 | 2010.04.22 AD at 18:30:26 IDT INFO | jvm 1 | 2010/04/22 18:30:31 | 2010.04.22 AD at 18:30:31 IDT INFO | jvm 1 | 2010/04/22 18:30:36 | 2010.04.22 AD at 18:30:36 IDT INFO | jvm 1 | 2010/04/22 18:30:41 | 2010.04.22 AD at 18:30:41 IDT INFO | jvm 1 | 2010/04/22 18:30:46 | 2010.04.22 AD at 18:30:46 IDT INFO | jvm 1 | 2010/04/22 18:30:51 | 2010.04.22 AD at 18:30:51 IDT INFO | jvm 1 | 2010/04/22 18:30:56 | 2010.04.22 AD at 18:30:56 IDT INFO | jvm 1 | 2010/04/22 18:31:01 | 2010.04.22 AD at 18:31:01 IDT INFO | jvm 1 | 2010/04/22 18:31:06 | 2010.04.22 AD at 18:31:06 IDT INFO | jvm 1 | 2010/04/22 18:31:11 | 2010.04.22 AD at 18:31:11 IDT INFO | jvm 1 | 2010/04/22 18:31:16 | 2010.04.22 AD at 18:31:16 IDT INFO | jvm 1 | 2010/04/22 18:31:19 | [Loaded java.net.SocketTimeoutException from /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] INFO | jvm 1 | 2010/04/22 18:31:19 | [Loaded sun.net.ConnectionResetException from /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar] INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read Timed out. (Last Ping was 0 milliseconds ago) INFO | jvm 1 | 2010/04/22 18:31:21 | 2010.04.22 AD at 18:31:21 IDT INFO | jvm 1 | 2010/04/22 18:31:26 | 2010.04.22 AD at 18:31:26 IDT INFO | jvm 1 | 2010/04/22 18:31:31 | 2010.04.22 AD at 18:31:31 IDT INFO | jvm 1 | 2010/04/22 18:31:36 | 2010.04.22 AD at 18:31:36 IDT INFO | jvm 1 | 2010/04/22 18:31:41 | 2010.04.22 AD at 18:31:41 IDT INFO | jvm 1 | 2010/04/22 18:31:46 | 2010.04.22 AD at 18:31:46 IDT INFO | jvm 1 | 2010/04/22 18:31:51 | 2010.04.22 AD at 18:31:51 IDT INFO | jvm 1 | 2010/04/22 18:31:56 | 2010.04.22 AD at 18:31:56 IDT INFO | jvm 1 | 2010/04/22 18:32:01 | 2010.04.22 AD at 18:32:01 IDT INFO | jvm 1 | 2010/04/22 18:32:06 | 2010.04.22 AD at 18:32:06 IDT INFO | jvm 1 | 2010/04/22 18:32:11 | 2010.04.22 AD at 18:32:11 IDT INFO | jvm 1 | 2010/04/22 18:32:16 | 2010.04.22 AD at 18:32:16 IDT INFO | jvm 1 | 2010/04/22 18:32:21 | 2010.04.22 AD at 18:32:21 IDT INFO | jvm 1 | 2010/04/22 18:32:26 | 2010.04.22 AD at 18:32:26 IDT INFO | jvm 1 | 2010/04/22 18:32:31 | 2010.04.22 AD at 18:32:31 IDT INFO | jvm 1 | 2010/04/22 18:32:36 | 2010.04.22 AD at 18:32:36 IDT INFO | jvm 1 | 2010/04/22 18:32:41 | 2010.04.22 AD at 18:32:41 IDT INFO | jvm 1 | 2010/04/22 18:32:46 | 2010.04.22 AD at 18:32:46 IDT INFO | jvm 1 | 2010/04/22 18:32:51 | 2010.04.22 AD at 18:32:51 IDT INFO | jvm 1 | 2010/04/22 18:32:56 | 2010.04.22 AD at 18:32:56 IDT INFO | jvm 1 | 2010/04/22 18:33:01 | 2010.04.22 AD at 18:33:01 IDT INFO | jvm 1 | 2010/04/22 18:33:06 | 2010.04.22 AD at 18:33:06 IDT INFO | jvm 1 | 2010/04/22 18:33:11 | 2010.04.22 AD at 18:33:11 IDT INFO | jvm 1 | 2010/04/22 18:33:16 | 2010.04.22 AD at 18:33:16 IDT INFO | jvm 1 | 2010/04/22 18:33:21 | 2010.04.22 AD at 18:33:21 IDT INFO | jvm 1 | 2010/04/22 18:33:26 | 2010.04.22 AD at 18:33:26 IDT INFO | jvm 1 | 2010/04/22 18:33:31 | 2010.04.22 AD at 18:33:31 IDT INFO | jvm 1 | 2010/04/22 18:33:36 | 2010.04.22 AD at 18:33:36 IDT INFO | jvm 1 | 2010/04/22 18:33:41 | 2010.04.22 AD at 18:33:41 IDT INFO | jvm 1 | 2010/04/22 18:33:46 | 2010.04.22 AD at 18:33:46 IDT INFO | jvm 1 | 2010/04/22 18:33:51 | 2010.04.22 AD at 18:33:51 IDT INFO | jvm 1 | 2010/04/22 18:33:57 | 2010.04.22 AD at 18:33:56 IDT INFO | jvm 1 | 2010/04/22 18:34:01 | 2010.04.22 AD at 18:34:01 IDT INFO | jvm 1 | 2010/04/22 18:34:06 | 2010.04.22 AD at 18:34:06 IDT INFO | jvm 1 | 2010/04/22 18:34:11 | 2010.04.22 AD at 18:34:11 IDT INFO | jvm 1 | 2010/04/22 18:34:16 | 2010.04.22 AD at 18:34:16 IDT INFO | jvm 1 | 2010/04/22 18:34:22 | 2010.04.22 AD at 18:34:21 IDT INFO | jvm 1 | 2010/04/22 18:34:27 | 2010.04.22 AD at 18:34:27 IDT INFO | jvm 1 | 2010/04/22 18:34:32 | 2010.04.22 AD at 18:34:32 IDT INFO | jvm 1 | 2010/04/22 18:34:37 | 2010.04.22 AD at 18:34:37 IDT INFO | jvm 1 | 2010/04/22 18:34:42 | 2010.04.22 AD at 18:34:42 IDT INFO | jvm 1 | 2010/04/22 18:34:47 | 2010.04.22 AD at 18:34:47 IDT INFO | jvm 1 | 2010/04/22 18:34:52 | 2010.04.22 AD at 18:34:52 IDT INFO | jvm 1 | 2010/04/22 18:34:57 | 2010.04.22 AD at 18:34:57 IDT INFO | jvm 1 | 2010/04/22 18:35:02 | 2010.04.22 AD at 18:35:02 IDT INFO | jvm 1 | 2010/04/22 18:35:07 | 2010.04.22 AD at 18:35:07 IDT INFO | jvm 1 | 2010/04/22 18:35:12 | 2010.04.22 AD at 18:35:12 IDT INFO | jvm 1 | 2010/04/22 18:35:17 | 2010.04.22 AD at 18:35:17 IDT INFO | jvm 1 | 2010/04/22 18:35:22 | 2010.04.22 AD at 18:35:22 IDT INFO | jvm 1 | 2010/04/22 18:35:27 | 2010.04.22 AD at 18:35:27 IDT INFO | jvm 1 | 2010/04/22 18:35:32 | 2010.04.22 AD at 18:35:32 IDT INFO | jvm 1 | 2010/04/22 18:35:37 | 2010.04.22 AD at 18:35:37 IDT INFO | jvm 1 | 2010/04/22 18:35:42 | 2010.04.22 AD at 18:35:42 IDT INFO | jvm 1 | 2010/04/22 18:35:47 | 2010.04.22 AD at 18:35:47 IDT INFO | jvm 1 | 2010/04/22 18:35:52 | 2010.04.22 AD at 18:35:52 IDT INFO | jvm 1 | 2010/04/22 18:35:57 | 2010.04.22 AD at 18:35:57 IDT INFO | jvm 1 | 2010/04/22 18:36:02 | 2010.04.22 AD at 18:36:02 IDT INFO | jvm 1 | 2010/04/22 18:36:07 | 2010.04.22 AD at 18:36:07 IDT INFO | jvm 1 | 2010/04/22 18:36:12 | 2010.04.22 AD at 18:36:12 IDT INFO | jvm 1 | 2010/04/22 18:36:17 | 2010.04.22 AD at 18:36:17 IDT INFO | jvm 1 | 2010/04/22 18:36:19 | WrapperManager Debug: Read Timed out. (Last Ping was 0 milliseconds ago) INFO | jvm 1 | 2010/04/22 18:36:22 | 2010.04.22 AD at 18:36:22 IDT INFO | jvm 1 | 2010/04/22 18:36:27 | 2010.04.22 AD at 18:36:27 IDT INFO | jvm 1 | 2010/04/22 18:36:32 | 2010.04.22 AD at 18:36:32 IDT INFO | jvm 1 | 2010/04/22 18:36:37 | 2010.04.22 AD at 18:36:37 IDT INFO | jvm 1 | 2010/04/22 18:36:42 | 2010.04.22 AD at 18:36:42 IDT INFO | jvm 1 | 2010/04/22 18:36:47 | 2010.04.22 AD at 18:36:47 IDT INFO | jvm 1 | 2010/04/22 18:36:52 | 2010.04.22 AD at 18:36:52 IDT INFO | jvm 1 | 2010/04/22 18:36:57 | 2010.04.22 AD at 18:36:57 IDT INFO | jvm 1 | 2010/04/22 18:37:02 | 2010.04.22 AD at 18:37:02 IDT INFO | jvm 1 | 2010/04/22 18:37:07 | 2010.04.22 AD at 18:37:07 IDT INFO | jvm 1 | 2010/04/22 18:37:12 | 2010.04.22 AD at 18:37:12 IDT INFO | jvm 1 | 2010/04/22 18:37:17 | 2010.04.22 AD at 18:37:17 IDT INFO | jvm 1 | 2010/04/22 18:37:22 | 2010.04.22 AD at 18:37:22 IDT INFO | jvm 1 | 2010/04/22 18:37:27 | 2010.04.22 AD at 18:37:27 IDT INFO | jvm 1 | 2010/04/22 18:37:32 | 2010.04.22 AD at 18:37:32 IDT INFO | jvm 1 | 2010/04/22 18:37:37 | 2010.04.22 AD at 18:37:37 IDT INFO | jvm 1 | 2010/04/22 18:37:42 | 2010.04.22 AD at 18:37:42 IDT INFO | jvm 1 | 2010/04/22 18:37:47 | 2010.04.22 AD at 18:37:47 IDT INFO | jvm 1 | 2010/04/22 18:37:52 | 2010.04.22 AD at 18:37:52 IDT INFO | jvm 1 | 2010/04/22 18:37:57 | 2010.04.22 AD at 18:37:57 IDT INFO | jvm 1 | 2010/04/22 18:38:02 | 2010.04.22 AD at 18:38:02 IDT INFO | jvm 1 | 2010/04/22 18:38:07 | 2010.04.22 AD at 18:38:07 IDT INFO | jvm 1 | 2010/04/22 18:38:12 | 2010.04.22 AD at 18:38:12 IDT INFO | jvm 1 | 2010/04/22 18:38:17 | 2010.04.22 AD at 18:38:17 IDT INFO | jvm 1 | 2010/04/22 18:38:22 | 2010.04.22 AD at 18:38:22 IDT INFO | jvm 1 | 2010/04/22 18:38:27 | 2010.04.22 AD at 18:38:27 IDT INFO | jvm 1 | 2010/04/22 18:38:32 | 2010.04.22 AD at 18:38:32 IDT INFO | jvm 1 | 2010/04/22 18:38:37 | 2010.04.22 AD at 18:38:37 IDT INFO | jvm 1 | 2010/04/22 18:38:42 | 2010.04.22 AD at 18:38:42 IDT INFO | jvm 1 | 2010/04/22 18:38:47 | 2010.04.22 AD at 18:38:47 IDT INFO | jvm 1 | 2010/04/22 18:38:52 | 2010.04.22 AD at 18:38:52 IDT INFO | jvm 1 | 2010/04/22 18:38:57 | 2010.04.22 AD at 18:38:57 IDT INFO | jvm 1 | 2010/04/22 18:39:02 | 2010.04.22 AD at 18:39:02 IDT INFO | jvm 1 | 2010/04/22 18:39:07 | 2010.04.22 AD at 18:39:07 IDT INFO | jvm 1 | 2010/04/22 18:39:12 | 2010.04.22 AD at 18:39:12 IDT INFO | jvm 1 | 2010/04/22 18:39:17 | 2010.04.22 AD at 18:39:17 IDT INFO | jvm 1 | 2010/04/22 18:39:22 | 2010.04.22 AD at 18:39:22 IDT INFO | jvm 1 | 2010/04/22 18:39:27 | 2010.04.22 AD at 18:39:27 IDT On Thu, Apr 22, 2010 at 11:22 AM, Leif Mortenson < lei...@ta...> wrote: > Tomer, > The Wrapper is designed to monitor the JVMs state to make sure that it > is running in a normal state. As one of its many checks, it sends a > ping every 5 seconds to the Java process. The Java process reads and > then responds to this ping, letting the Wrapper know that the JVM is > still alive. > The wrapper.ping.timeout is the maximum amount of time that the > Wrapper will allow without a ping reply before giving up and killing > the JVM. > > There is another issue that is especially important on Windows > machines, but also on UNIX. If the Wrapper process should ever crash, > then the Java process would be left running in the background as a > zombie without any way of terminating it. On Windows when running in > the service space, this means that the system would need to be > rebooted to kill the JVM. > To avoid this case, the Java side of the Wrapper keeps track of when > the last ping was received from the Wrapper. After the > wrapper.ping.timeout has expired, the JVM will request that the > Wrapper restart it. If that still fails for another 90 seconds then > the JVM will assume that the Wrapper is dead and exit. The Java side > of the Wrapper also checks to make sure that all of this only happens > if the Java-side tick timer has been progressing to make sure that it > is not a matter of the JVM being starved of CPU. > This is a feature that has been in the Wrapper without modification > for several years without modification. This is the first case I have > seen where it causes any problems. > > When the Java side of the Wrapper decides that the Wrapper is gone, it > calls System.exit to shut itself down. In your case however, the > Wrapper is still there. It sees that the JVM requested that it exit > and complies. This is why the JVM and then Wrapper are shutting down. > > I would really like to take a look at your unmodified wrapper.log as > well as the wrapper.conf file so I can make sense of exactly what is > happening on your system. > > As I wait, we are doing some more tests on our end to try and figure > out what combination of events would make this kind of failure > possible. > > I look forward to your response. > > Cheers, > Leif > > On Wed, Apr 21, 2010 at 10:02 PM, Tomer B <tom...@gm...> wrote: > > Hi, > > I'm checking about sending the logs. > > > > But what do you think of the following analysis (and question I raise). > > As I know that if I reservate some cpu processing to the vm that runs the > > wrapper+jvm then this issue does not happen - there is no shutdown, that > > means that maybe whats happening is that without cpu reservation the > vmware > > decides not to give cpu to the wrapper, therefore the wrapper does not > ping > > my jvm, and therefore the jvm asks the wrapper to restart itself (as seen > > from logs), in that case the wrapper manager is not confused because it > did > > not get any pings from the wrapper (in the logs I don't see that the > wrapper > > is sending pings at that time). However my question here is assuming > this > > is what is happening, how come when the wrapper shuts down the jvm and > not > > restarts it - the wrapper says: > > > >> DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: > >> DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), > >> source="unknown" > >> DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM > >> process status. > >> DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code > >> of > >> 1, setting the wrapper exit code to 1. > >> DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. > >> STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped > > > > Which looks like saying the wrapper is stopping the application, > shouldn't > > it just restart the jvm in case of ping timeouts? it looks like when my > jvm > > shuts down (as it requested the wrapper to shut itself down because it > did > > not recieve pings from wrapper) at that point when it finishes shut down > the > > wrapper receives SIGCHLD and decides to terminate the jvm and then also > > shuts down itself - what do you think of that? why is that happening? why > is > > there a SIGCHLD? isn't that normal? > > > > Thanks > > Tomer > > > > > > On Wed, Apr 21, 2010 at 9:52 AM, Leif Mortenson <le...@ta... > > > > wrote: > >> > >> Tomer, > >> Sorry for the trouble. Looking at subset of the log file, I am having > >> a hard time seeing exactly what is happening. Would it be possible > >> for you to send the full unedited wrapper.log file along with your > >> wrapper.conf to me directly off list? > >> > >> Something is causing read timeouts like the following. Are you aware > >> of any system time shifts taking place. The one below was about 5 > >> minutes. > >> INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read > >> Timed out. (Last Ping was 298400 milliseconds ago) > >> > >> The Wrapper's tick timer was designed to handle such time shifts > >> without problem. > >> > >> It looks like the WrapperManager is confused and thinks that the > >> Wrapper has not pinged it for 90 seconds more than the ping timeout. > >> This should only happen if the Wrapper process is dead, which is > >> obviously not true in your case. > >> > >> I will go back over the code and try to figure out exactly what is > >> going on, but the full log will be very helpful. > >> > >> As a note to that old thread. The problem they were having with the > >> EAR file needing to be reset can be easily handled with in the > >> Professional Edition with the ability to execute shell scripts or > >> other external commands prior to launching a new Java instance: > >> http://wrapper.tanukisoftware.org/doc/english/props-event.html#command > >> > >> Cheers, > >> Leif > >> > >> On Wed, Apr 21, 2010 at 6:05 AM, Tomer B <tom...@gm...> wrote: > >> > Hi, > >> > > >> > I am currently testing wrapper 3.4.0 on solaris 64 bit machine. > >> > Under regular "physical" machine its already working for days and is > >> > fine > >> > (tried that on a couple of machines). > >> > > >> > However if i run the wrapper under vm instances (of vmware) i get > >> > abnormal > >> > shutdowns always both to my server and to the wrapper (after about 2 > >> > hours > >> > both process are down). > >> > > >> > I'm attaching relevant logs: > >> > Note that I tested a configured vmware for reservation of cpu to one > of > >> > the > >> > vm instances then on that vm instance it seems that I don't have this > >> > shutdown, i have multiple vm virtual machines on the same physical > >> > machine > >> > and the shutdown happens on all of them (except for that instance with > >> > that > >> > cpu reservation). I would like vm configuration to be working as well > >> > because I'm thinking of having such a configuration possibly in future > >> > in > >> > production. > >> > I also saw this over the web: > >> > > >> > > http://old.nabble.com/JVM-appears-hung:-VMware,-verbose-garbage-collection-td13470076.html > >> > > >> > Here are relevant logs if you could provide me with information of why > >> > these > >> > abnormal shutdowns are happening: > >> > > >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: Java > VM > >> > Vendor : Sun Microsystems Inc. > >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > >> > Name : SunOS > >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > >> > Arch : amd64 > >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: > >> > INFO | jvm 1 | 2010/04/20 19:43:30 | [Loaded > >> > org.tanukisoftware.wrapper.WrapperManager$5 from xxxxxxxxxx (i made > >> > this.. > >> > xxxxxx)] > >> > > >> > > >> > DEBUG | wrapperp | 2010/04/20 22:16:09 | read a packet PING : ping > >> > DEBUG | wrapperp | 2010/04/20 22:16:13 | send a packet PING : ping > >> > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: > Received > >> > a > >> > packet PING : ping > >> > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Send a > >> > packet PING : ping > >> > DEBUG | wrapperp | 2010/04/20 22:16:13 | read a packet PING : ping > >> > > >> > . > >> > . > >> > . > >> > > >> > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read > >> > Timed > >> > out. (Last Ping was 298400 milliseconds ago) > >> > > >> > . > >> > . > >> > . > >> > > >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Read > >> > Timed > >> > out. (Last Ping was 596700 milliseconds ago) > >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager: JVM did not > >> > exit. > >> > Give up. > >> > > >> > . > >> > . > >> > . > >> > > >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > >> > ShutdownHook > >> > started > >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > >> > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Send a > >> > packet STOP : 0 > >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > Stopped > >> > checking for control events. > >> > DEBUG | wrapperp | 2010/04/20 22:26:13 | read a packet STOP : 0 > >> > DEBUG | wrapper | 2010/04/20 22:26:13 | JVM requested a shutdown. > (0) > >> > DEBUG | wrapper | 2010/04/20 22:26:13 | wrapperStopProcess(0) > called. > >> > DEBUG | wrapper | 2010/04/20 22:26:13 | Sending stop signal to JVM > >> > DEBUG | wrapperp | 2010/04/20 22:26:13 | send a packet STOP : NULL > >> > > >> > . > >> > . > >> > . > >> > > >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: > Thread, > >> > Wrapper-Shutdown-Hook, handling the shutdown process. > >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: > calling > >> > listener.stop() > >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Send a > >> > packet STOP_PENDING : 180000 > >> > > >> > . > >> > . > >> > . > >> > > >> > > >> > DEBUG | wrapperp | 2010/04/20 22:26:14 | read a packet STOP_PENDING : > >> > 180000 > >> > DEBUG | wrapper | 2010/04/20 22:26:14 | JVM signalled a stop pending > >> > with > >> > waitHint of 180000 millis. > >> > > >> > INFO | jvm 1 | 2010/04/20 22:26:14 | Start method stopped > >> > > >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: > returned > >> > from listener.stop() -> 0 > >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: > >> > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: wait > for > >> > 0 > >> > shutdown locs to be released. > >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Send a > >> > packet STOPPED : 0 > >> > > >> > DEBUG | wrapperp | 2010/04/20 22:26:22 | read a packet STOPPED : 0 > >> > DEBUG | wrapper | 2010/04/20 22:26:22 | JVM signalled that it was > >> > stopped. > >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: > Closing > >> > socket. > >> > DEBUG | wrapperp | 2010/04/20 22:26:22 | socket read no code > (closed?). > >> > > >> > INFO | jvm 1 | 2010/04/20 22:26:23 | WrapperManager Debug: > >> > ShutdownHook > >> > complete > >> > DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: > >> > DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 > (SIGCHLD), > >> > source="unknown" > >> > DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking > JVM > >> > process status. > >> > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a > code > >> > of > >> > 1, setting the wrapper exit code to 1. > >> > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. > >> > STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped > >> > > >> > > >> > Note that at this stage i have both wrapper & my server processes > down. > >> > > >> > Thanks for the help.. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Tomer B <tom...@gm...> - 2010-04-22 17:00:07
|
Hi
I just saw this in logs:
/opt/javatest/libwrapper.so: ld.so.1: java: fatal:
/opt/javatest/libwrapper.so: wrong ELF class: ELFCLASS64 (Possible cause:
architecture word width mismatch)
I'm going to fix this and rerun the test. I think it will happen also
because in my server I had it correct.
I'll send again the logs after this is fixed.
On Thu, Apr 22, 2010 at 7:52 PM, Tomer B <tom...@gm...> wrote:
> Hi,
>
> I created a dummy java app that prints the time every 5 seconds and
> allocates some memory.
> I ran it for some time and although it did not halt I got the same
> behaviour with manners of the jvm stopped receiving pings from wrapper after
> some time! (which is what happens to my server).
> I'm attaching the java app code + conf + logs
>
> Attaching a zip containing the whole thing.
>
> ################
> JavaVMTester.java
> ################
>
> package com.test.javavmtester;
>
> import java.text.SimpleDateFormat;
> import java.util.Date;
>
> import org.tanukisoftware.wrapper.WrapperListener;
> import org.tanukisoftware.wrapper.WrapperManager;
>
> public class JavaVMTester extends Thread implements WrapperListener{
> private static byte[] myBytes = new byte[1024 * 1024 * 1200];
>
> public static void main(String[] args) {
> WrapperManager.start( new JavaVMTester(), args );
> }
>
> public void run() {
>
> while (true) {
> try {
> System.out.println(new SimpleDateFormat("yyyy.MM.dd G 'at'
> HH:mm:ss z").format(new Date()));
> Thread.sleep(5000);
> } catch (InterruptedException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
> }
> }
>
>
> @Override
> public void controlEvent(int event) {
> if (WrapperManager.isControlledByNativeWrapper()) {
> System.out.println("controlled by wrapper");
> // The Wrapper will take care of this event
> } else {
> // We are not being controlled by the Wrapper, so
> // handle the event ourselves.
> if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) ||
> (event == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) ||
> (event == WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)){
> System.out.println("controlled by us");
> WrapperManager.stop(0);
> }
> }
> }
>
> @Override
> public Integer start(String[] arg0) {
> JavaVMTester jv = new JavaVMTester();
> jv.start();
> return null;
> }
>
> @Override
> public int stop(int arg0) {
> // TODO Auto-generated method stub
> return 0;
> }
> }
>
> #########
> server.conf
> #########
> #********************************************************************
>
> # Java Main class. This class must implement the WrapperListener interface
> # or guarantee that the WrapperManager class is initialized. Helper
> # classes are provided to do this for you. See the Integration section
> # of the documentation for details.
> wrapper.java.mainclass=com.test.javavmtester.JavaVMTester
> wrapper.java.command=/bin/java
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Log file to use for wrapper output logging.
> wrapper.logfile=./server-wrapper.log
>
> wrapper.java.classpath.1=./wrapper.jar
> wrapper.java.classpath.2=.
>
> nitial Java Heap Size (in MB)
> wrapper.java.initmemory=1000
>
> # Maximum Java Heap Size (in MB)
> wrapper.java.maxmemory=2000
>
> # Java Additional Parameters
> wrapper.java.additional.1=-Xloggc:gc.txt
>
> wrapper.java.additional.2=-Dsun.rmi.dgc.client.gcInterval=0x7ffffffffffffffe
>
> wrapper.java.additional.3=-Dsun.rmi.dgc.server.gcInterval=0x7ffffffffffffffe
> wrapper.java.additional.4=-Dsun.net.inetaddr.ttl=0
> wrapper.java.additional.5=-Dsun.net.client.defaultConnectTimeout=30000
> wrapper.java.additional.6=-Dsun.net.client.defaultReadTimeout=120000
> wrapper.java.additional.7=-Dummy
> wrapper.java.additional.8=-XX:+PrintGCDetails
> wrapper.java.additional.9=-XX:+PrintGCTimeStamps
> wrapper.java.additional.10=-XX:MaxPermSize=256M
> wrapper.java.additional.11=-DentityExpansionLimit=256000
> wrapper.java.additional.12=-verbose
> wrapper.java.additional.13=-XX:-OmitStackTraceInFastThrow
> wrapper.java.additional.14=-XX:+UseParallelOldGC
> wrapper.java.additional.15=-Duser.timezone=Asia/Jerusalem
> wrapper.java.additional.17=-XX:-ReduceInitialCardMarks
> wrapper.java.additional.18=-Dummy
> wrapper.java.additional.19=-Dummy
> wrapper.java.additional.20=-Dummy
>
> wrapper.java.additional.21=-Dcom.sun.management.jmxremote.port=13034
>
> wrapper.java.additional.22=-Dcom.sun.management.jmxremote.authenticate=false
> wrapper.java.additional.23=-Dcom.sun.management.jmxremote.ssl=false
>
> wrapper.java.additional.24=-Dorg.tanukisoftware.wrapper.WrapperManager.mbean=true
>
> wrapper.java.library.path.1=./
>
> # Format of output for the log file. (See docs for formats)
> wrapper.logfile.format=LPTM
>
> # Log Level for log file output. (See docs for log levels)
> wrapper.logfile.loglevel=DEBUG
>
> # Allow the service to interact with the desktop.
> wrapper.shutdown.timeout=300
> wrapper.ping.timeout=300
>
> ###########
> wrapper.conf
> ###########
>
> #********************************************************************
> # Wrapper License Properties (Ignored by Community Edition)
> #********************************************************************
> # Include file problems can be debugged by removing the first '#'
> # from the following line:
> ##include.debug
> #include ../conf/wrapper-license.conf
> #include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf
>
> #********************************************************************
> # Wrapper Java Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=java
>
> # Tell the Wrapper to log the full generated Java command line.
> #wrapper.java.command.loglevel=DEBUG
>
> # Java Main class. This class must implement the WrapperListener interface
> # or guarantee that the WrapperManager class is initialized. Helper
> # classes are provided to do this for you. See the Integration section
> # of the documentation for details.
> wrapper.java.mainclass=org.tanukisoftware.wrapper.test.Main
>
> # Java Classpath (include wrapper.jar) Add class path elements as
> # needed starting from 1
> wrapper.java.classpath.1=./wrappertest.jar
> wrapper.java.classpath.2=./wrapper.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=./
>
> # Java Bits. On applicable platforms, tells the JVM to run in 32 or 64-bit
> mode.
> wrapper.java.additional.auto_bits=TRUE
>
> # Java Additional Parameters
> #wrapper.java.additional.1=
>
> # Initial Java Heap Size (in MB)
> #wrapper.java.initmemory=3
>
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>
> # Application parameters. Add parameters as needed starting from 1
> #wrapper.app.parameter.1=
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Enables Debug output from the Wrapper.
> # wrapper.debug=TRUE
>
> # Format of output for the console. (See docs for formats)
> wrapper.console.format=PM
>
> # Log Level for console output. (See docs for log levels)
> wrapper.console.loglevel=DEBUG
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=./wrapper.log
>
> # Format of output for the log file. (See docs for formats)
> wrapper.logfile.format=LPTM
>
> # Log Level for log file output. (See docs for log levels)
> wrapper.logfile.loglevel=DEBUG
>
> # Maximum size that the log file will be allowed to grow to before
> # the log is rolled. Size is specified in bytes. The default value
> # of 0, disables log rolling. May abbreviate with the 'k' (kb) or
> # 'm' (mb) suffix. For example: 10m = 10 megabytes.
> wrapper.logfile.maxsize=0
>
> # Maximum number of rolled log files which will be allowed before old
> # files are deleted. The default value of 0 implies no limit.
> wrapper.logfile.maxfiles=0
>
> # Log Level for sys/event log output. (See docs for log levels)
> wrapper.syslog.loglevel=USER
> #********************************************************************
> # Wrapper General Properties
> #********************************************************************
> # Allow for the use of non-contiguous numbered properties
> wrapper.ignore_sequence_gaps=TRUE
>
> # Title to use when running as a console
> wrapper.console.title=Test Wrapper Sample Application
>
> #********************************************************************
> # Wrapper Windows NT/2000/XP Service Properties
> #********************************************************************
> # WARNING - Do not modify any of these properties when an application
> # using this configuration file has been installed as a service.
> # Please uninstall the service before modifying this section. The
> # service can then be reinstalled.
>
> # Name of the service
> wrapper.name=testwrapper
>
> # Display name of the service
> wrapper.displayname=Test Wrapper Sample Application
>
> # Description of the service
> wrapper.description=Test Wrapper Sample Application Description
>
> # Service dependencies. Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed. AUTO_START, DELAY_START or
> DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
>
> ###############
> server-wrapper.log
> ###############
>
> INFO | jvm 1 | 2010/04/22 18:25:58 | WrapperManager Debug: Received a
> packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:25:58 | WrapperManager Debug: Send a
> packet PING : ping
> DEBUG | wrapperp | 2010/04/22 18:25:58 | read a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:00 | 2010.04.22 AD at 18:26:00 IDT
> DEBUG | wrapperp | 2010/04/22 18:26:02 | send a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:02 | WrapperManager Debug: Received a
> packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:02 | WrapperManager Debug: Send a
> packet PING : ping
> DEBUG | wrapperp | 2010/04/22 18:26:02 | read a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:05 | 2010.04.22 AD at 18:26:05 IDT
> DEBUG | wrapperp | 2010/04/22 18:26:06 | send a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:07 | WrapperManager Debug: Received a
> packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:07 | WrapperManager Debug: Send a
> packet PING : ping
> DEBUG | wrapperp | 2010/04/22 18:26:07 | read a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:10 | 2010.04.22 AD at 18:26:10 IDT
> DEBUG | wrapperp | 2010/04/22 18:26:11 | send a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:11 | WrapperManager Debug: Received a
> packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:11 | WrapperManager Debug: Send a
> packet PING : ping
> DEBUG | wrapperp | 2010/04/22 18:26:11 | read a packet PING : ping
> DEBUG | wrapperp | 2010/04/22 18:26:15 | send a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:15 | WrapperManager Debug: Received a
> packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:15 | WrapperManager Debug: Send a
> packet PING : ping
> DEBUG | wrapperp | 2010/04/22 18:26:15 | read a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:15 | 2010.04.22 AD at 18:26:15 IDT
> DEBUG | wrapperp | 2010/04/22 18:26:19 | send a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:19 | WrapperManager Debug: Received a
> packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:19 | WrapperManager Debug: Send a
> packet PING : ping
> DEBUG | wrapperp | 2010/04/22 18:26:19 | read a packet PING : ping
> INFO | jvm 1 | 2010/04/22 18:26:20 | 2010.04.22 AD at 18:26:20 IDT
> INFO | jvm 1 | 2010/04/22 18:26:25 | 2010.04.22 AD at 18:26:25 IDT
> INFO | jvm 1 | 2010/04/22 18:26:30 | 2010.04.22 AD at 18:26:30 IDT
> INFO | jvm 1 | 2010/04/22 18:26:35 | 2010.04.22 AD at 18:26:35 IDT
> INFO | jvm 1 | 2010/04/22 18:26:40 | 2010.04.22 AD at 18:26:40 IDT
> INFO | jvm 1 | 2010/04/22 18:26:45 | 2010.04.22 AD at 18:26:45 IDT
> INFO | jvm 1 | 2010/04/22 18:26:50 | 2010.04.22 AD at 18:26:50 IDT
> INFO | jvm 1 | 2010/04/22 18:26:55 | 2010.04.22 AD at 18:26:55 IDT
> INFO | jvm 1 | 2010/04/22 18:27:00 | 2010.04.22 AD at 18:27:00 IDT
> INFO | jvm 1 | 2010/04/22 18:27:05 | 2010.04.22 AD at 18:27:05 IDT
> INFO | jvm 1 | 2010/04/22 18:27:10 | 2010.04.22 AD at 18:27:10 IDT
> INFO | jvm 1 | 2010/04/22 18:27:16 | 2010.04.22 AD at 18:27:15 IDT
> INFO | jvm 1 | 2010/04/22 18:27:21 | 2010.04.22 AD at 18:27:20 IDT
> INFO | jvm 1 | 2010/04/22 18:27:26 | 2010.04.22 AD at 18:27:25 IDT
> INFO | jvm 1 | 2010/04/22 18:27:30 | 2010.04.22 AD at 18:27:30 IDT
> INFO | jvm 1 | 2010/04/22 18:27:35 | 2010.04.22 AD at 18:27:35 IDT
> INFO | jvm 1 | 2010/04/22 18:27:41 | 2010.04.22 AD at 18:27:40 IDT
> INFO | jvm 1 | 2010/04/22 18:27:46 | 2010.04.22 AD at 18:27:45 IDT
> INFO | jvm 1 | 2010/04/22 18:27:51 | 2010.04.22 AD at 18:27:51 IDT
> INFO | jvm 1 | 2010/04/22 18:27:56 | 2010.04.22 AD at 18:27:56 IDT
> INFO | jvm 1 | 2010/04/22 18:28:01 | 2010.04.22 AD at 18:28:01 IDT
> INFO | jvm 1 | 2010/04/22 18:28:06 | 2010.04.22 AD at 18:28:06 IDT
> INFO | jvm 1 | 2010/04/22 18:28:11 | 2010.04.22 AD at 18:28:11 IDT
> INFO | jvm 1 | 2010/04/22 18:28:16 | 2010.04.22 AD at 18:28:16 IDT
> INFO | jvm 1 | 2010/04/22 18:28:21 | 2010.04.22 AD at 18:28:21 IDT
> INFO | jvm 1 | 2010/04/22 18:28:26 | 2010.04.22 AD at 18:28:26 IDT
> INFO | jvm 1 | 2010/04/22 18:28:31 | 2010.04.22 AD at 18:28:31 IDT
> INFO | jvm 1 | 2010/04/22 18:28:36 | 2010.04.22 AD at 18:28:36 IDT
> INFO | jvm 1 | 2010/04/22 18:28:41 | 2010.04.22 AD at 18:28:41 IDT
> INFO | jvm 1 | 2010/04/22 18:28:46 | 2010.04.22 AD at 18:28:46 IDT
> INFO | jvm 1 | 2010/04/22 18:28:51 | 2010.04.22 AD at 18:28:51 IDT
> INFO | jvm 1 | 2010/04/22 18:28:56 | 2010.04.22 AD at 18:28:56 IDT
> INFO | jvm 1 | 2010/04/22 18:29:01 | 2010.04.22 AD at 18:29:01 IDT
> INFO | jvm 1 | 2010/04/22 18:29:06 | 2010.04.22 AD at 18:29:06 IDT
> INFO | jvm 1 | 2010/04/22 18:29:11 | 2010.04.22 AD at 18:29:11 IDT
> INFO | jvm 1 | 2010/04/22 18:29:16 | 2010.04.22 AD at 18:29:16 IDT
> INFO | jvm 1 | 2010/04/22 18:29:21 | 2010.04.22 AD at 18:29:21 IDT
> INFO | jvm 1 | 2010/04/22 18:29:26 | 2010.04.22 AD at 18:29:26 IDT
> INFO | jvm 1 | 2010/04/22 18:29:31 | 2010.04.22 AD at 18:29:31 IDT
> INFO | jvm 1 | 2010/04/22 18:29:36 | 2010.04.22 AD at 18:29:36 IDT
> INFO | jvm 1 | 2010/04/22 18:29:41 | 2010.04.22 AD at 18:29:41 IDT
> INFO | jvm 1 | 2010/04/22 18:29:46 | 2010.04.22 AD at 18:29:46 IDT
> INFO | jvm 1 | 2010/04/22 18:29:51 | 2010.04.22 AD at 18:29:51 IDT
> INFO | jvm 1 | 2010/04/22 18:29:56 | 2010.04.22 AD at 18:29:56 IDT
> INFO | jvm 1 | 2010/04/22 18:30:01 | 2010.04.22 AD at 18:30:01 IDT
> INFO | jvm 1 | 2010/04/22 18:30:06 | 2010.04.22 AD at 18:30:06 IDT
> INFO | jvm 1 | 2010/04/22 18:30:11 | 2010.04.22 AD at 18:30:11 IDT
> INFO | jvm 1 | 2010/04/22 18:30:16 | 2010.04.22 AD at 18:30:16 IDT
> INFO | jvm 1 | 2010/04/22 18:30:21 | 2010.04.22 AD at 18:30:21 IDT
> INFO | jvm 1 | 2010/04/22 18:30:26 | 2010.04.22 AD at 18:30:26 IDT
> INFO | jvm 1 | 2010/04/22 18:30:31 | 2010.04.22 AD at 18:30:31 IDT
> INFO | jvm 1 | 2010/04/22 18:30:36 | 2010.04.22 AD at 18:30:36 IDT
> INFO | jvm 1 | 2010/04/22 18:30:41 | 2010.04.22 AD at 18:30:41 IDT
> INFO | jvm 1 | 2010/04/22 18:30:46 | 2010.04.22 AD at 18:30:46 IDT
> INFO | jvm 1 | 2010/04/22 18:30:51 | 2010.04.22 AD at 18:30:51 IDT
> INFO | jvm 1 | 2010/04/22 18:30:56 | 2010.04.22 AD at 18:30:56 IDT
> INFO | jvm 1 | 2010/04/22 18:31:01 | 2010.04.22 AD at 18:31:01 IDT
> INFO | jvm 1 | 2010/04/22 18:31:06 | 2010.04.22 AD at 18:31:06 IDT
> INFO | jvm 1 | 2010/04/22 18:31:11 | 2010.04.22 AD at 18:31:11 IDT
> INFO | jvm 1 | 2010/04/22 18:31:16 | 2010.04.22 AD at 18:31:16 IDT
> INFO | jvm 1 | 2010/04/22 18:31:19 | [Loaded
> java.net.SocketTimeoutException from
> /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar]
> INFO | jvm 1 | 2010/04/22 18:31:19 | [Loaded
> sun.net.ConnectionResetException from
> /usr/jdk/instances/jdk1.6.0/jre/lib/rt.jar]
> INFO | jvm 1 | 2010/04/22 18:31:19 | WrapperManager Debug: Read Timed
> out. (Last Ping was 0 milliseconds ago)
> INFO | jvm 1 | 2010/04/22 18:31:21 | 2010.04.22 AD at 18:31:21 IDT
> INFO | jvm 1 | 2010/04/22 18:31:26 | 2010.04.22 AD at 18:31:26 IDT
> INFO | jvm 1 | 2010/04/22 18:31:31 | 2010.04.22 AD at 18:31:31 IDT
> INFO | jvm 1 | 2010/04/22 18:31:36 | 2010.04.22 AD at 18:31:36 IDT
> INFO | jvm 1 | 2010/04/22 18:31:41 | 2010.04.22 AD at 18:31:41 IDT
> INFO | jvm 1 | 2010/04/22 18:31:46 | 2010.04.22 AD at 18:31:46 IDT
> INFO | jvm 1 | 2010/04/22 18:31:51 | 2010.04.22 AD at 18:31:51 IDT
> INFO | jvm 1 | 2010/04/22 18:31:56 | 2010.04.22 AD at 18:31:56 IDT
> INFO | jvm 1 | 2010/04/22 18:32:01 | 2010.04.22 AD at 18:32:01 IDT
> INFO | jvm 1 | 2010/04/22 18:32:06 | 2010.04.22 AD at 18:32:06 IDT
> INFO | jvm 1 | 2010/04/22 18:32:11 | 2010.04.22 AD at 18:32:11 IDT
> INFO | jvm 1 | 2010/04/22 18:32:16 | 2010.04.22 AD at 18:32:16 IDT
> INFO | jvm 1 | 2010/04/22 18:32:21 | 2010.04.22 AD at 18:32:21 IDT
> INFO | jvm 1 | 2010/04/22 18:32:26 | 2010.04.22 AD at 18:32:26 IDT
> INFO | jvm 1 | 2010/04/22 18:32:31 | 2010.04.22 AD at 18:32:31 IDT
> INFO | jvm 1 | 2010/04/22 18:32:36 | 2010.04.22 AD at 18:32:36 IDT
> INFO | jvm 1 | 2010/04/22 18:32:41 | 2010.04.22 AD at 18:32:41 IDT
> INFO | jvm 1 | 2010/04/22 18:32:46 | 2010.04.22 AD at 18:32:46 IDT
> INFO | jvm 1 | 2010/04/22 18:32:51 | 2010.04.22 AD at 18:32:51 IDT
> INFO | jvm 1 | 2010/04/22 18:32:56 | 2010.04.22 AD at 18:32:56 IDT
> INFO | jvm 1 | 2010/04/22 18:33:01 | 2010.04.22 AD at 18:33:01 IDT
> INFO | jvm 1 | 2010/04/22 18:33:06 | 2010.04.22 AD at 18:33:06 IDT
> INFO | jvm 1 | 2010/04/22 18:33:11 | 2010.04.22 AD at 18:33:11 IDT
> INFO | jvm 1 | 2010/04/22 18:33:16 | 2010.04.22 AD at 18:33:16 IDT
> INFO | jvm 1 | 2010/04/22 18:33:21 | 2010.04.22 AD at 18:33:21 IDT
> INFO | jvm 1 | 2010/04/22 18:33:26 | 2010.04.22 AD at 18:33:26 IDT
> INFO | jvm 1 | 2010/04/22 18:33:31 | 2010.04.22 AD at 18:33:31 IDT
> INFO | jvm 1 | 2010/04/22 18:33:36 | 2010.04.22 AD at 18:33:36 IDT
> INFO | jvm 1 | 2010/04/22 18:33:41 | 2010.04.22 AD at 18:33:41 IDT
> INFO | jvm 1 | 2010/04/22 18:33:46 | 2010.04.22 AD at 18:33:46 IDT
> INFO | jvm 1 | 2010/04/22 18:33:51 | 2010.04.22 AD at 18:33:51 IDT
> INFO | jvm 1 | 2010/04/22 18:33:57 | 2010.04.22 AD at 18:33:56 IDT
> INFO | jvm 1 | 2010/04/22 18:34:01 | 2010.04.22 AD at 18:34:01 IDT
> INFO | jvm 1 | 2010/04/22 18:34:06 | 2010.04.22 AD at 18:34:06 IDT
> INFO | jvm 1 | 2010/04/22 18:34:11 | 2010.04.22 AD at 18:34:11 IDT
> INFO | jvm 1 | 2010/04/22 18:34:16 | 2010.04.22 AD at 18:34:16 IDT
> INFO | jvm 1 | 2010/04/22 18:34:22 | 2010.04.22 AD at 18:34:21 IDT
> INFO | jvm 1 | 2010/04/22 18:34:27 | 2010.04.22 AD at 18:34:27 IDT
> INFO | jvm 1 | 2010/04/22 18:34:32 | 2010.04.22 AD at 18:34:32 IDT
> INFO | jvm 1 | 2010/04/22 18:34:37 | 2010.04.22 AD at 18:34:37 IDT
> INFO | jvm 1 | 2010/04/22 18:34:42 | 2010.04.22 AD at 18:34:42 IDT
> INFO | jvm 1 | 2010/04/22 18:34:47 | 2010.04.22 AD at 18:34:47 IDT
> INFO | jvm 1 | 2010/04/22 18:34:52 | 2010.04.22 AD at 18:34:52 IDT
> INFO | jvm 1 | 2010/04/22 18:34:57 | 2010.04.22 AD at 18:34:57 IDT
> INFO | jvm 1 | 2010/04/22 18:35:02 | 2010.04.22 AD at 18:35:02 IDT
> INFO | jvm 1 | 2010/04/22 18:35:07 | 2010.04.22 AD at 18:35:07 IDT
> INFO | jvm 1 | 2010/04/22 18:35:12 | 2010.04.22 AD at 18:35:12 IDT
> INFO | jvm 1 | 2010/04/22 18:35:17 | 2010.04.22 AD at 18:35:17 IDT
> INFO | jvm 1 | 2010/04/22 18:35:22 | 2010.04.22 AD at 18:35:22 IDT
> INFO | jvm 1 | 2010/04/22 18:35:27 | 2010.04.22 AD at 18:35:27 IDT
> INFO | jvm 1 | 2010/04/22 18:35:32 | 2010.04.22 AD at 18:35:32 IDT
> INFO | jvm 1 | 2010/04/22 18:35:37 | 2010.04.22 AD at 18:35:37 IDT
> INFO | jvm 1 | 2010/04/22 18:35:42 | 2010.04.22 AD at 18:35:42 IDT
> INFO | jvm 1 | 2010/04/22 18:35:47 | 2010.04.22 AD at 18:35:47 IDT
> INFO | jvm 1 | 2010/04/22 18:35:52 | 2010.04.22 AD at 18:35:52 IDT
> INFO | jvm 1 | 2010/04/22 18:35:57 | 2010.04.22 AD at 18:35:57 IDT
> INFO | jvm 1 | 2010/04/22 18:36:02 | 2010.04.22 AD at 18:36:02 IDT
> INFO | jvm 1 | 2010/04/22 18:36:07 | 2010.04.22 AD at 18:36:07 IDT
> INFO | jvm 1 | 2010/04/22 18:36:12 | 2010.04.22 AD at 18:36:12 IDT
> INFO | jvm 1 | 2010/04/22 18:36:17 | 2010.04.22 AD at 18:36:17 IDT
> INFO | jvm 1 | 2010/04/22 18:36:19 | WrapperManager Debug: Read Timed
> out. (Last Ping was 0 milliseconds ago)
> INFO | jvm 1 | 2010/04/22 18:36:22 | 2010.04.22 AD at 18:36:22 IDT
> INFO | jvm 1 | 2010/04/22 18:36:27 | 2010.04.22 AD at 18:36:27 IDT
> INFO | jvm 1 | 2010/04/22 18:36:32 | 2010.04.22 AD at 18:36:32 IDT
> INFO | jvm 1 | 2010/04/22 18:36:37 | 2010.04.22 AD at 18:36:37 IDT
> INFO | jvm 1 | 2010/04/22 18:36:42 | 2010.04.22 AD at 18:36:42 IDT
> INFO | jvm 1 | 2010/04/22 18:36:47 | 2010.04.22 AD at 18:36:47 IDT
> INFO | jvm 1 | 2010/04/22 18:36:52 | 2010.04.22 AD at 18:36:52 IDT
> INFO | jvm 1 | 2010/04/22 18:36:57 | 2010.04.22 AD at 18:36:57 IDT
> INFO | jvm 1 | 2010/04/22 18:37:02 | 2010.04.22 AD at 18:37:02 IDT
> INFO | jvm 1 | 2010/04/22 18:37:07 | 2010.04.22 AD at 18:37:07 IDT
> INFO | jvm 1 | 2010/04/22 18:37:12 | 2010.04.22 AD at 18:37:12 IDT
> INFO | jvm 1 | 2010/04/22 18:37:17 | 2010.04.22 AD at 18:37:17 IDT
> INFO | jvm 1 | 2010/04/22 18:37:22 | 2010.04.22 AD at 18:37:22 IDT
> INFO | jvm 1 | 2010/04/22 18:37:27 | 2010.04.22 AD at 18:37:27 IDT
> INFO | jvm 1 | 2010/04/22 18:37:32 | 2010.04.22 AD at 18:37:32 IDT
> INFO | jvm 1 | 2010/04/22 18:37:37 | 2010.04.22 AD at 18:37:37 IDT
> INFO | jvm 1 | 2010/04/22 18:37:42 | 2010.04.22 AD at 18:37:42 IDT
> INFO | jvm 1 | 2010/04/22 18:37:47 | 2010.04.22 AD at 18:37:47 IDT
> INFO | jvm 1 | 2010/04/22 18:37:52 | 2010.04.22 AD at 18:37:52 IDT
> INFO | jvm 1 | 2010/04/22 18:37:57 | 2010.04.22 AD at 18:37:57 IDT
> INFO | jvm 1 | 2010/04/22 18:38:02 | 2010.04.22 AD at 18:38:02 IDT
> INFO | jvm 1 | 2010/04/22 18:38:07 | 2010.04.22 AD at 18:38:07 IDT
> INFO | jvm 1 | 2010/04/22 18:38:12 | 2010.04.22 AD at 18:38:12 IDT
> INFO | jvm 1 | 2010/04/22 18:38:17 | 2010.04.22 AD at 18:38:17 IDT
> INFO | jvm 1 | 2010/04/22 18:38:22 | 2010.04.22 AD at 18:38:22 IDT
> INFO | jvm 1 | 2010/04/22 18:38:27 | 2010.04.22 AD at 18:38:27 IDT
> INFO | jvm 1 | 2010/04/22 18:38:32 | 2010.04.22 AD at 18:38:32 IDT
> INFO | jvm 1 | 2010/04/22 18:38:37 | 2010.04.22 AD at 18:38:37 IDT
> INFO | jvm 1 | 2010/04/22 18:38:42 | 2010.04.22 AD at 18:38:42 IDT
> INFO | jvm 1 | 2010/04/22 18:38:47 | 2010.04.22 AD at 18:38:47 IDT
> INFO | jvm 1 | 2010/04/22 18:38:52 | 2010.04.22 AD at 18:38:52 IDT
> INFO | jvm 1 | 2010/04/22 18:38:57 | 2010.04.22 AD at 18:38:57 IDT
> INFO | jvm 1 | 2010/04/22 18:39:02 | 2010.04.22 AD at 18:39:02 IDT
> INFO | jvm 1 | 2010/04/22 18:39:07 | 2010.04.22 AD at 18:39:07 IDT
> INFO | jvm 1 | 2010/04/22 18:39:12 | 2010.04.22 AD at 18:39:12 IDT
> INFO | jvm 1 | 2010/04/22 18:39:17 | 2010.04.22 AD at 18:39:17 IDT
> INFO | jvm 1 | 2010/04/22 18:39:22 | 2010.04.22 AD at 18:39:22 IDT
> INFO | jvm 1 | 2010/04/22 18:39:27 | 2010.04.22 AD at 18:39:27 IDT
>
>
>
>
> On Thu, Apr 22, 2010 at 11:22 AM, Leif Mortenson <
> lei...@ta...> wrote:
>
>> Tomer,
>> The Wrapper is designed to monitor the JVMs state to make sure that it
>> is running in a normal state. As one of its many checks, it sends a
>> ping every 5 seconds to the Java process. The Java process reads and
>> then responds to this ping, letting the Wrapper know that the JVM is
>> still alive.
>> The wrapper.ping.timeout is the maximum amount of time that the
>> Wrapper will allow without a ping reply before giving up and killing
>> the JVM.
>>
>> There is another issue that is especially important on Windows
>> machines, but also on UNIX. If the Wrapper process should ever crash,
>> then the Java process would be left running in the background as a
>> zombie without any way of terminating it. On Windows when running in
>> the service space, this means that the system would need to be
>> rebooted to kill the JVM.
>> To avoid this case, the Java side of the Wrapper keeps track of when
>> the last ping was received from the Wrapper. After the
>> wrapper.ping.timeout has expired, the JVM will request that the
>> Wrapper restart it. If that still fails for another 90 seconds then
>> the JVM will assume that the Wrapper is dead and exit. The Java side
>> of the Wrapper also checks to make sure that all of this only happens
>> if the Java-side tick timer has been progressing to make sure that it
>> is not a matter of the JVM being starved of CPU.
>> This is a feature that has been in the Wrapper without modification
>> for several years without modification. This is the first case I have
>> seen where it causes any problems.
>>
>> When the Java side of the Wrapper decides that the Wrapper is gone, it
>> calls System.exit to shut itself down. In your case however, the
>> Wrapper is still there. It sees that the JVM requested that it exit
>> and complies. This is why the JVM and then Wrapper are shutting down.
>>
>> I would really like to take a look at your unmodified wrapper.log as
>> well as the wrapper.conf file so I can make sense of exactly what is
>> happening on your system.
>>
>> As I wait, we are doing some more tests on our end to try and figure
>> out what combination of events would make this kind of failure
>> possible.
>>
>> I look forward to your response.
>>
>> Cheers,
>> Leif
>>
>> On Wed, Apr 21, 2010 at 10:02 PM, Tomer B <tom...@gm...> wrote:
>> > Hi,
>> > I'm checking about sending the logs.
>> >
>> > But what do you think of the following analysis (and question I raise).
>> > As I know that if I reservate some cpu processing to the vm that runs
>> the
>> > wrapper+jvm then this issue does not happen - there is no shutdown, that
>> > means that maybe whats happening is that without cpu reservation the
>> vmware
>> > decides not to give cpu to the wrapper, therefore the wrapper does not
>> ping
>> > my jvm, and therefore the jvm asks the wrapper to restart itself (as
>> seen
>> > from logs), in that case the wrapper manager is not confused because it
>> did
>> > not get any pings from the wrapper (in the logs I don't see that the
>> wrapper
>> > is sending pings at that time). However my question here is assuming
>> this
>> > is what is happening, how come when the wrapper shuts down the jvm and
>> not
>> > restarts it - the wrapper says:
>> >
>> >> DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details:
>> >> DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD),
>> >> source="unknown"
>> >> DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking
>> JVM
>> >> process status.
>> >> DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a
>> code
>> >> of
>> >> 1, setting the wrapper exit code to 1.
>> >> DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally.
>> >> STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped
>> >
>> > Which looks like saying the wrapper is stopping the application,
>> shouldn't
>> > it just restart the jvm in case of ping timeouts? it looks like when my
>> jvm
>> > shuts down (as it requested the wrapper to shut itself down because it
>> did
>> > not recieve pings from wrapper) at that point when it finishes shut down
>> the
>> > wrapper receives SIGCHLD and decides to terminate the jvm and then also
>> > shuts down itself - what do you think of that? why is that happening?
>> why is
>> > there a SIGCHLD? isn't that normal?
>> >
>> > Thanks
>> > Tomer
>> >
>> >
>> > On Wed, Apr 21, 2010 at 9:52 AM, Leif Mortenson <
>> le...@ta...>
>> > wrote:
>> >>
>> >> Tomer,
>> >> Sorry for the trouble. Looking at subset of the log file, I am having
>> >> a hard time seeing exactly what is happening. Would it be possible
>> >> for you to send the full unedited wrapper.log file along with your
>> >> wrapper.conf to me directly off list?
>> >>
>> >> Something is causing read timeouts like the following. Are you aware
>> >> of any system time shifts taking place. The one below was about 5
>> >> minutes.
>> >> INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read
>> >> Timed out. (Last Ping was 298400 milliseconds ago)
>> >>
>> >> The Wrapper's tick timer was designed to handle such time shifts
>> >> without problem.
>> >>
>> >> It looks like the WrapperManager is confused and thinks that the
>> >> Wrapper has not pinged it for 90 seconds more than the ping timeout.
>> >> This should only happen if the Wrapper process is dead, which is
>> >> obviously not true in your case.
>> >>
>> >> I will go back over the code and try to figure out exactly what is
>> >> going on, but the full log will be very helpful.
>> >>
>> >> As a note to that old thread. The problem they were having with the
>> >> EAR file needing to be reset can be easily handled with in the
>> >> Professional Edition with the ability to execute shell scripts or
>> >> other external commands prior to launching a new Java instance:
>> >> http://wrapper.tanukisoftware.org/doc/english/props-event.html#command
>> >>
>> >> Cheers,
>> >> Leif
>> >>
>> >> On Wed, Apr 21, 2010 at 6:05 AM, Tomer B <tom...@gm...> wrote:
>> >> > Hi,
>> >> >
>> >> > I am currently testing wrapper 3.4.0 on solaris 64 bit machine.
>> >> > Under regular "physical" machine its already working for days and is
>> >> > fine
>> >> > (tried that on a couple of machines).
>> >> >
>> >> > However if i run the wrapper under vm instances (of vmware) i get
>> >> > abnormal
>> >> > shutdowns always both to my server and to the wrapper (after about 2
>> >> > hours
>> >> > both process are down).
>> >> >
>> >> > I'm attaching relevant logs:
>> >> > Note that I tested a configured vmware for reservation of cpu to one
>> of
>> >> > the
>> >> > vm instances then on that vm instance it seems that I don't have this
>> >> > shutdown, i have multiple vm virtual machines on the same physical
>> >> > machine
>> >> > and the shutdown happens on all of them (except for that instance
>> with
>> >> > that
>> >> > cpu reservation). I would like vm configuration to be working as
>> well
>> >> > because I'm thinking of having such a configuration possibly in
>> future
>> >> > in
>> >> > production.
>> >> > I also saw this over the web:
>> >> >
>> >> >
>> http://old.nabble.com/JVM-appears-hung:-VMware,-verbose-garbage-collection-td13470076.html
>> >> >
>> >> > Here are relevant logs if you could provide me with information of
>> why
>> >> > these
>> >> > abnormal shutdowns are happening:
>> >> >
>> >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: Java
>> VM
>> >> > Vendor : Sun Microsystems Inc.
>> >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS
>> >> > Name : SunOS
>> >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS
>> >> > Arch : amd64
>> >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug:
>> >> > INFO | jvm 1 | 2010/04/20 19:43:30 | [Loaded
>> >> > org.tanukisoftware.wrapper.WrapperManager$5 from xxxxxxxxxx (i made
>> >> > this..
>> >> > xxxxxx)]
>> >> >
>> >> >
>> >> > DEBUG | wrapperp | 2010/04/20 22:16:09 | read a packet PING : ping
>> >> > DEBUG | wrapperp | 2010/04/20 22:16:13 | send a packet PING : ping
>> >> > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug:
>> Received
>> >> > a
>> >> > packet PING : ping
>> >> > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Send
>> a
>> >> > packet PING : ping
>> >> > DEBUG | wrapperp | 2010/04/20 22:16:13 | read a packet PING : ping
>> >> >
>> >> > .
>> >> > .
>> >> > .
>> >> >
>> >> > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read
>> >> > Timed
>> >> > out. (Last Ping was 298400 milliseconds ago)
>> >> >
>> >> > .
>> >> > .
>> >> > .
>> >> >
>> >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Read
>> >> > Timed
>> >> > out. (Last Ping was 596700 milliseconds ago)
>> >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager: JVM did not
>> >> > exit.
>> >> > Give up.
>> >> >
>> >> > .
>> >> > .
>> >> > .
>> >> >
>> >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug:
>> >> > ShutdownHook
>> >> > started
>> >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug:
>> >> > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
>> >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Send
>> a
>> >> > packet STOP : 0
>> >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug:
>> Stopped
>> >> > checking for control events.
>> >> > DEBUG | wrapperp | 2010/04/20 22:26:13 | read a packet STOP : 0
>> >> > DEBUG | wrapper | 2010/04/20 22:26:13 | JVM requested a shutdown.
>> (0)
>> >> > DEBUG | wrapper | 2010/04/20 22:26:13 | wrapperStopProcess(0)
>> called.
>> >> > DEBUG | wrapper | 2010/04/20 22:26:13 | Sending stop signal to JVM
>> >> > DEBUG | wrapperp | 2010/04/20 22:26:13 | send a packet STOP : NULL
>> >> >
>> >> > .
>> >> > .
>> >> > .
>> >> >
>> >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug:
>> Thread,
>> >> > Wrapper-Shutdown-Hook, handling the shutdown process.
>> >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug:
>> calling
>> >> > listener.stop()
>> >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Send
>> a
>> >> > packet STOP_PENDING : 180000
>> >> >
>> >> > .
>> >> > .
>> >> > .
>> >> >
>> >> >
>> >> > DEBUG | wrapperp | 2010/04/20 22:26:14 | read a packet STOP_PENDING
>> :
>> >> > 180000
>> >> > DEBUG | wrapper | 2010/04/20 22:26:14 | JVM signalled a stop
>> pending
>> >> > with
>> >> > waitHint of 180000 millis.
>> >> >
>> >> > INFO | jvm 1 | 2010/04/20 22:26:14 | Start method stopped
>> >> >
>> >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug:
>> returned
>> >> > from listener.stop() -> 0
>> >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug:
>> >> > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook
>> >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: wait
>> for
>> >> > 0
>> >> > shutdown locs to be released.
>> >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Send
>> a
>> >> > packet STOPPED : 0
>> >> >
>> >> > DEBUG | wrapperp | 2010/04/20 22:26:22 | read a packet STOPPED : 0
>> >> > DEBUG | wrapper | 2010/04/20 22:26:22 | JVM signalled that it was
>> >> > stopped.
>> >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug:
>> Closing
>> >> > socket.
>> >> > DEBUG | wrapperp | 2010/04/20 22:26:22 | socket read no code
>> (closed?).
>> >> >
>> >> > INFO | jvm 1 | 2010/04/20 22:26:23 | WrapperManager Debug:
>> >> > ShutdownHook
>> >> > complete
>> >> > DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details:
>> >> > DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18
>> (SIGCHLD),
>> >> > source="unknown"
>> >> > DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking
>> JVM
>> >> > process status.
>> >> > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a
>> code
>> >> > of
>> >> > 1, setting the wrapper exit code to 1.
>> >> > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally.
>> >> > STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped
>> >> >
>> >> >
>> >> > Note that at this stage i have both wrapper & my server processes
>> down.
>> >> >
>> >> > Thanks for the help..
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>
>
|
|
From: Leif M. <lei...@ta...> - 2010-04-22 08:23:00
|
Tomer, The Wrapper is designed to monitor the JVMs state to make sure that it is running in a normal state. As one of its many checks, it sends a ping every 5 seconds to the Java process. The Java process reads and then responds to this ping, letting the Wrapper know that the JVM is still alive. The wrapper.ping.timeout is the maximum amount of time that the Wrapper will allow without a ping reply before giving up and killing the JVM. There is another issue that is especially important on Windows machines, but also on UNIX. If the Wrapper process should ever crash, then the Java process would be left running in the background as a zombie without any way of terminating it. On Windows when running in the service space, this means that the system would need to be rebooted to kill the JVM. To avoid this case, the Java side of the Wrapper keeps track of when the last ping was received from the Wrapper. After the wrapper.ping.timeout has expired, the JVM will request that the Wrapper restart it. If that still fails for another 90 seconds then the JVM will assume that the Wrapper is dead and exit. The Java side of the Wrapper also checks to make sure that all of this only happens if the Java-side tick timer has been progressing to make sure that it is not a matter of the JVM being starved of CPU. This is a feature that has been in the Wrapper without modification for several years without modification. This is the first case I have seen where it causes any problems. When the Java side of the Wrapper decides that the Wrapper is gone, it calls System.exit to shut itself down. In your case however, the Wrapper is still there. It sees that the JVM requested that it exit and complies. This is why the JVM and then Wrapper are shutting down. I would really like to take a look at your unmodified wrapper.log as well as the wrapper.conf file so I can make sense of exactly what is happening on your system. As I wait, we are doing some more tests on our end to try and figure out what combination of events would make this kind of failure possible. I look forward to your response. Cheers, Leif On Wed, Apr 21, 2010 at 10:02 PM, Tomer B <tom...@gm...> wrote: > Hi, > I'm checking about sending the logs. > > But what do you think of the following analysis (and question I raise). > As I know that if I reservate some cpu processing to the vm that runs the > wrapper+jvm then this issue does not happen - there is no shutdown, that > means that maybe whats happening is that without cpu reservation the vmware > decides not to give cpu to the wrapper, therefore the wrapper does not ping > my jvm, and therefore the jvm asks the wrapper to restart itself (as seen > from logs), in that case the wrapper manager is not confused because it did > not get any pings from the wrapper (in the logs I don't see that the wrapper > is sending pings at that time). However my question here is assuming this > is what is happening, how come when the wrapper shuts down the jvm and not > restarts it - the wrapper says: > >> DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: >> DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), >> source="unknown" >> DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM >> process status. >> DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code >> of >> 1, setting the wrapper exit code to 1. >> DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. >> STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped > > Which looks like saying the wrapper is stopping the application, shouldn't > it just restart the jvm in case of ping timeouts? it looks like when my jvm > shuts down (as it requested the wrapper to shut itself down because it did > not recieve pings from wrapper) at that point when it finishes shut down the > wrapper receives SIGCHLD and decides to terminate the jvm and then also > shuts down itself - what do you think of that? why is that happening? why is > there a SIGCHLD? isn't that normal? > > Thanks > Tomer > > > On Wed, Apr 21, 2010 at 9:52 AM, Leif Mortenson <le...@ta...> > wrote: >> >> Tomer, >> Sorry for the trouble. Looking at subset of the log file, I am having >> a hard time seeing exactly what is happening. Would it be possible >> for you to send the full unedited wrapper.log file along with your >> wrapper.conf to me directly off list? >> >> Something is causing read timeouts like the following. Are you aware >> of any system time shifts taking place. The one below was about 5 >> minutes. >> INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read >> Timed out. (Last Ping was 298400 milliseconds ago) >> >> The Wrapper's tick timer was designed to handle such time shifts >> without problem. >> >> It looks like the WrapperManager is confused and thinks that the >> Wrapper has not pinged it for 90 seconds more than the ping timeout. >> This should only happen if the Wrapper process is dead, which is >> obviously not true in your case. >> >> I will go back over the code and try to figure out exactly what is >> going on, but the full log will be very helpful. >> >> As a note to that old thread. The problem they were having with the >> EAR file needing to be reset can be easily handled with in the >> Professional Edition with the ability to execute shell scripts or >> other external commands prior to launching a new Java instance: >> http://wrapper.tanukisoftware.org/doc/english/props-event.html#command >> >> Cheers, >> Leif >> >> On Wed, Apr 21, 2010 at 6:05 AM, Tomer B <tom...@gm...> wrote: >> > Hi, >> > >> > I am currently testing wrapper 3.4.0 on solaris 64 bit machine. >> > Under regular "physical" machine its already working for days and is >> > fine >> > (tried that on a couple of machines). >> > >> > However if i run the wrapper under vm instances (of vmware) i get >> > abnormal >> > shutdowns always both to my server and to the wrapper (after about 2 >> > hours >> > both process are down). >> > >> > I'm attaching relevant logs: >> > Note that I tested a configured vmware for reservation of cpu to one of >> > the >> > vm instances then on that vm instance it seems that I don't have this >> > shutdown, i have multiple vm virtual machines on the same physical >> > machine >> > and the shutdown happens on all of them (except for that instance with >> > that >> > cpu reservation). I would like vm configuration to be working as well >> > because I'm thinking of having such a configuration possibly in future >> > in >> > production. >> > I also saw this over the web: >> > >> > http://old.nabble.com/JVM-appears-hung:-VMware,-verbose-garbage-collection-td13470076.html >> > >> > Here are relevant logs if you could provide me with information of why >> > these >> > abnormal shutdowns are happening: >> > >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: Java VM >> > Vendor : Sun Microsystems Inc. >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS >> > Name : SunOS >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS >> > Arch : amd64 >> > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: >> > INFO | jvm 1 | 2010/04/20 19:43:30 | [Loaded >> > org.tanukisoftware.wrapper.WrapperManager$5 from xxxxxxxxxx (i made >> > this.. >> > xxxxxx)] >> > >> > >> > DEBUG | wrapperp | 2010/04/20 22:16:09 | read a packet PING : ping >> > DEBUG | wrapperp | 2010/04/20 22:16:13 | send a packet PING : ping >> > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Received >> > a >> > packet PING : ping >> > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Send a >> > packet PING : ping >> > DEBUG | wrapperp | 2010/04/20 22:16:13 | read a packet PING : ping >> > >> > . >> > . >> > . >> > >> > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read >> > Timed >> > out. (Last Ping was 298400 milliseconds ago) >> > >> > . >> > . >> > . >> > >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Read >> > Timed >> > out. (Last Ping was 596700 milliseconds ago) >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager: JVM did not >> > exit. >> > Give up. >> > >> > . >> > . >> > . >> > >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: >> > ShutdownHook >> > started >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: >> > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Send a >> > packet STOP : 0 >> > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Stopped >> > checking for control events. >> > DEBUG | wrapperp | 2010/04/20 22:26:13 | read a packet STOP : 0 >> > DEBUG | wrapper | 2010/04/20 22:26:13 | JVM requested a shutdown. (0) >> > DEBUG | wrapper | 2010/04/20 22:26:13 | wrapperStopProcess(0) called. >> > DEBUG | wrapper | 2010/04/20 22:26:13 | Sending stop signal to JVM >> > DEBUG | wrapperp | 2010/04/20 22:26:13 | send a packet STOP : NULL >> > >> > . >> > . >> > . >> > >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Thread, >> > Wrapper-Shutdown-Hook, handling the shutdown process. >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: calling >> > listener.stop() >> > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Send a >> > packet STOP_PENDING : 180000 >> > >> > . >> > . >> > . >> > >> > >> > DEBUG | wrapperp | 2010/04/20 22:26:14 | read a packet STOP_PENDING : >> > 180000 >> > DEBUG | wrapper | 2010/04/20 22:26:14 | JVM signalled a stop pending >> > with >> > waitHint of 180000 millis. >> > >> > INFO | jvm 1 | 2010/04/20 22:26:14 | Start method stopped >> > >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: returned >> > from listener.stop() -> 0 >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: >> > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: wait for >> > 0 >> > shutdown locs to be released. >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Send a >> > packet STOPPED : 0 >> > >> > DEBUG | wrapperp | 2010/04/20 22:26:22 | read a packet STOPPED : 0 >> > DEBUG | wrapper | 2010/04/20 22:26:22 | JVM signalled that it was >> > stopped. >> > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Closing >> > socket. >> > DEBUG | wrapperp | 2010/04/20 22:26:22 | socket read no code (closed?). >> > >> > INFO | jvm 1 | 2010/04/20 22:26:23 | WrapperManager Debug: >> > ShutdownHook >> > complete >> > DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: >> > DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), >> > source="unknown" >> > DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM >> > process status. >> > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code >> > of >> > 1, setting the wrapper exit code to 1. >> > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. >> > STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped >> > >> > >> > Note that at this stage i have both wrapper & my server processes down. >> > >> > Thanks for the help.. |
|
From: Christian <chr...@ta...> - 2010-04-22 06:12:49
|
Hi, Usually the jvm inherits the whole environment from the wrapper. so when you started the wrapper preloading libumem both, the wrapper as well as the JVM, will use libumem. I assume you want to preload your JVM exclusively libumem. That would be possible using the environment definition routines of the wrapper; please have a look at this site: http://wrapper.tanukisoftware.org/doc/english/props-envvars.html#definition adding the following line should cause your JVM being generated using libumem rather than the standard library for memory allocation: set.LD_PRELOAD=/usr/lib/libumem.so additionally you can also set the value for LD_PRELOAD_64 at the same place to preload the 64bit libumem. pldd 623 623: /export/home/chris/340/wrapper_prerelease_3.4.0-pro/bin/./wrapper /exp /usr/lib/libsocket.so.1 /usr/lib/libpthread.so.1 /usr/lib/libnsl.so.1 /usr/lib/libm.so.1 /usr/lib/librt.so.1 /usr/lib/libc.so.1 /usr/lib/libdl.so.1 /usr/lib/libmp.so.2 /usr/lib/libaio.so.1 /usr/lib/libmd5.so.1 /usr/lib/libthread.so.1 pldd 624 624: /usr/jdk/jdk1.6.0_14/bin/java -Djava.library.path=../lib -classpath .. /usr/lib/libumem.so.1 /usr/lib/libthread.so.1 /usr/jdk/jdk1.6.0_14/jre/lib/i386/jli/libjli.so /usr/lib/libdl.so.1 /usr/lib/libc.so.1 /usr/jdk/jdk1.6.0_14/jre/lib/i386/client/libjvm.so /usr/lib/libsocket.so.1 /usr/lib/libsched.so.1 /usr/lib/libm.so.1 /usr/lib/libCrun.so.1 /usr/lib/libdoor.so.1 /usr/lib/libnsl.so.1 /usr/lib/libmp.so.2 /usr/jdk/jdk1.6.0_14/jre/lib/i386/libverify.so /usr/jdk/jdk1.6.0_14/jre/lib/i386/libjava.so /usr/jdk/jdk1.6.0_14/jre/lib/i386/native_threads/libhpi.so /usr/jdk/jdk1.6.0_14/jre/lib/i386/libzip.so /usr/jdk/jdk1.6.0_14/jre/lib/i386/libmanagement.so /export/home/wrapper/lib/libwrapper.so /usr/lib/librt.so.1 /usr/lib/libaio.so.1 /usr/lib/libmd5.so.1 /usr/jdk/jdk1.6.0_14/jre/lib/i386/libnet.so /usr/jdk/jdk1.6.0_14/jre/lib/i386/libawt.so /usr/jdk/jdk1.6.0_14/jre/lib/i386/headless/libmawt.so Hope this is the answer to your question. Best Regards, Christian On Wed, 2010-04-21 at 23:55 +0300, Tomer B wrote: > We’re in process to migrate our app to Solaris x86. Due to some memory > allocation enhancements we would like to use libumem Solaris memory. > To make it work JVM should have system environment LD_PRELOAD or > LD_PRELOAD_64. The problem that if we use preload before wrapper > launch it does not transfer the config further to jvm. And it is not > clear how to configure wrapper to make it work. > > > Could you help please? > > Thanks > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Tomer B <tom...@gm...> - 2010-04-21 20:56:00
|
We’re in process to migrate our app to Solaris x86. Due to some memory allocation enhancements we would like to use libumem Solaris memory. To make it work JVM should have system environment LD_PRELOAD or LD_PRELOAD_64. The problem that if we use preload before wrapper launch it does not transfer the config further to jvm. And it is not clear how to configure wrapper to make it work. Could you help please? Thanks |
|
From: Tomer B <tom...@gm...> - 2010-04-21 13:02:51
|
Hi, I'm checking about sending the logs. But what do you think of the following analysis (and question I raise). As I know that if I reservate some cpu processing to the vm that runs the wrapper+jvm then this issue does not happen - there is no shutdown, that means that maybe whats happening is that without cpu reservation the vmware decides not to give cpu to the wrapper, therefore the wrapper does not ping my jvm, and therefore the jvm asks the wrapper to restart itself (as seen from logs), in that case the wrapper manager is not confused because it did not get any pings from the wrapper (in the logs I don't see that the wrapper is sending pings at that time). However my question here is assuming this is what is happening, how come when the wrapper shuts down the jvm and not restarts it - the wrapper says: > DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: > DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code of > 1, setting the wrapper exit code to 1. > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. > STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped Which looks like saying the wrapper is stopping the application, shouldn't it just restart the jvm in case of ping timeouts? it looks like when my jvm shuts down (as it requested the wrapper to shut itself down because it did not recieve pings from wrapper) at that point when it finishes shut down the wrapper receives SIGCHLD and decides to terminate the jvm and then also shuts down itself - what do you think of that? why is that happening? why is there a SIGCHLD? isn't that normal? Thanks Tomer On Wed, Apr 21, 2010 at 9:52 AM, Leif Mortenson <le...@ta...>wrote: > Tomer, > Sorry for the trouble. Looking at subset of the log file, I am having > a hard time seeing exactly what is happening. Would it be possible > for you to send the full unedited wrapper.log file along with your > wrapper.conf to me directly off list? > > Something is causing read timeouts like the following. Are you aware > of any system time shifts taking place. The one below was about 5 > minutes. > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read > Timed out. (Last Ping was 298400 milliseconds ago) > > The Wrapper's tick timer was designed to handle such time shifts > without problem. > > It looks like the WrapperManager is confused and thinks that the > Wrapper has not pinged it for 90 seconds more than the ping timeout. > This should only happen if the Wrapper process is dead, which is > obviously not true in your case. > > I will go back over the code and try to figure out exactly what is > going on, but the full log will be very helpful. > > As a note to that old thread. The problem they were having with the > EAR file needing to be reset can be easily handled with in the > Professional Edition with the ability to execute shell scripts or > other external commands prior to launching a new Java instance: > http://wrapper.tanukisoftware.org/doc/english/props-event.html#command > > Cheers, > Leif > > On Wed, Apr 21, 2010 at 6:05 AM, Tomer B <tom...@gm...> wrote: > > Hi, > > > > I am currently testing wrapper 3.4.0 on solaris 64 bit machine. > > Under regular "physical" machine its already working for days and is fine > > (tried that on a couple of machines). > > > > However if i run the wrapper under vm instances (of vmware) i get > abnormal > > shutdowns always both to my server and to the wrapper (after about 2 > hours > > both process are down). > > > > I'm attaching relevant logs: > > Note that I tested a configured vmware for reservation of cpu to one of > the > > vm instances then on that vm instance it seems that I don't have this > > shutdown, i have multiple vm virtual machines on the same physical > machine > > and the shutdown happens on all of them (except for that instance with > that > > cpu reservation). I would like vm configuration to be working as well > > because I'm thinking of having such a configuration possibly in future in > > production. > > I also saw this over the web: > > > http://old.nabble.com/JVM-appears-hung:-VMware,-verbose-garbage-collection-td13470076.html > > > > Here are relevant logs if you could provide me with information of why > these > > abnormal shutdowns are happening: > > > > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: Java VM > > Vendor : Sun Microsystems Inc. > > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > > Name : SunOS > > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > > Arch : amd64 > > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: > > INFO | jvm 1 | 2010/04/20 19:43:30 | [Loaded > > org.tanukisoftware.wrapper.WrapperManager$5 from xxxxxxxxxx (i made > this.. > > xxxxxx)] > > > > > > DEBUG | wrapperp | 2010/04/20 22:16:09 | read a packet PING : ping > > DEBUG | wrapperp | 2010/04/20 22:16:13 | send a packet PING : ping > > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Received > a > > packet PING : ping > > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Send a > > packet PING : ping > > DEBUG | wrapperp | 2010/04/20 22:16:13 | read a packet PING : ping > > > > . > > . > > . > > > > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read > Timed > > out. (Last Ping was 298400 milliseconds ago) > > > > . > > . > > . > > > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Read > Timed > > out. (Last Ping was 596700 milliseconds ago) > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager: JVM did not > exit. > > Give up. > > > > . > > . > > . > > > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > ShutdownHook > > started > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Send a > > packet STOP : 0 > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Stopped > > checking for control events. > > DEBUG | wrapperp | 2010/04/20 22:26:13 | read a packet STOP : 0 > > DEBUG | wrapper | 2010/04/20 22:26:13 | JVM requested a shutdown. (0) > > DEBUG | wrapper | 2010/04/20 22:26:13 | wrapperStopProcess(0) called. > > DEBUG | wrapper | 2010/04/20 22:26:13 | Sending stop signal to JVM > > DEBUG | wrapperp | 2010/04/20 22:26:13 | send a packet STOP : NULL > > > > . > > . > > . > > > > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Thread, > > Wrapper-Shutdown-Hook, handling the shutdown process. > > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: calling > > listener.stop() > > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Send a > > packet STOP_PENDING : 180000 > > > > . > > . > > . > > > > > > DEBUG | wrapperp | 2010/04/20 22:26:14 | read a packet STOP_PENDING : > > 180000 > > DEBUG | wrapper | 2010/04/20 22:26:14 | JVM signalled a stop pending > with > > waitHint of 180000 millis. > > > > INFO | jvm 1 | 2010/04/20 22:26:14 | Start method stopped > > > > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: returned > > from listener.stop() -> 0 > > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: > > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: wait for > 0 > > shutdown locs to be released. > > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Send a > > packet STOPPED : 0 > > > > DEBUG | wrapperp | 2010/04/20 22:26:22 | read a packet STOPPED : 0 > > DEBUG | wrapper | 2010/04/20 22:26:22 | JVM signalled that it was > stopped. > > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Closing > > socket. > > DEBUG | wrapperp | 2010/04/20 22:26:22 | socket read no code (closed?). > > > > INFO | jvm 1 | 2010/04/20 22:26:23 | WrapperManager Debug: > ShutdownHook > > complete > > DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: > > DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), > > source="unknown" > > DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM > > process status. > > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code > of > > 1, setting the wrapper exit code to 1. > > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. > > STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped > > > > > > Note that at this stage i have both wrapper & my server processes down. > > > > Thanks for the help.. > > -- > Leif Mortenson > Tanuki Software, Ltd. > 6-16-7-1001 Nishi-Kasai, Edogawa-ku > Tokyo 134-0088 Japan > Tel/Fax: +81-3-3878-3211 > http://www.tanukisoftware.com > lei...@ta... > > > ------------------------------------------------------------------------------ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <le...@ta...> - 2010-04-21 07:18:29
|
Tomer, Sorry for the trouble. Looking at subset of the log file, I am having a hard time seeing exactly what is happening. Would it be possible for you to send the full unedited wrapper.log file along with your wrapper.conf to me directly off list? Something is causing read timeouts like the following. Are you aware of any system time shifts taking place. The one below was about 5 minutes. INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read Timed out. (Last Ping was 298400 milliseconds ago) The Wrapper's tick timer was designed to handle such time shifts without problem. It looks like the WrapperManager is confused and thinks that the Wrapper has not pinged it for 90 seconds more than the ping timeout. This should only happen if the Wrapper process is dead, which is obviously not true in your case. I will go back over the code and try to figure out exactly what is going on, but the full log will be very helpful. As a note to that old thread. The problem they were having with the EAR file needing to be reset can be easily handled with in the Professional Edition with the ability to execute shell scripts or other external commands prior to launching a new Java instance: http://wrapper.tanukisoftware.org/doc/english/props-event.html#command Cheers, Leif On Wed, Apr 21, 2010 at 6:05 AM, Tomer B <tom...@gm...> wrote: > Hi, > > I am currently testing wrapper 3.4.0 on solaris 64 bit machine. > Under regular "physical" machine its already working for days and is fine > (tried that on a couple of machines). > > However if i run the wrapper under vm instances (of vmware) i get abnormal > shutdowns always both to my server and to the wrapper (after about 2 hours > both process are down). > > I'm attaching relevant logs: > Note that I tested a configured vmware for reservation of cpu to one of the > vm instances then on that vm instance it seems that I don't have this > shutdown, i have multiple vm virtual machines on the same physical machine > and the shutdown happens on all of them (except for that instance with that > cpu reservation). I would like vm configuration to be working as well > because I'm thinking of having such a configuration possibly in future in > production. > I also saw this over the web: > http://old.nabble.com/JVM-appears-hung:-VMware,-verbose-garbage-collection-td13470076.html > > Here are relevant logs if you could provide me with information of why these > abnormal shutdowns are happening: > > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: Java VM > Vendor : Sun Microsystems Inc. > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > Name : SunOS > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > Arch : amd64 > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: > INFO | jvm 1 | 2010/04/20 19:43:30 | [Loaded > org.tanukisoftware.wrapper.WrapperManager$5 from xxxxxxxxxx (i made this.. > xxxxxx)] > > > DEBUG | wrapperp | 2010/04/20 22:16:09 | read a packet PING : ping > DEBUG | wrapperp | 2010/04/20 22:16:13 | send a packet PING : ping > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/20 22:16:13 | read a packet PING : ping > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read Timed > out. (Last Ping was 298400 milliseconds ago) > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Read Timed > out. (Last Ping was 596700 milliseconds ago) > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager: JVM did not exit. > Give up. > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: ShutdownHook > started > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Send a > packet STOP : 0 > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Stopped > checking for control events. > DEBUG | wrapperp | 2010/04/20 22:26:13 | read a packet STOP : 0 > DEBUG | wrapper | 2010/04/20 22:26:13 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2010/04/20 22:26:13 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2010/04/20 22:26:13 | Sending stop signal to JVM > DEBUG | wrapperp | 2010/04/20 22:26:13 | send a packet STOP : NULL > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Thread, > Wrapper-Shutdown-Hook, handling the shutdown process. > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: calling > listener.stop() > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Send a > packet STOP_PENDING : 180000 > > . > . > . > > > DEBUG | wrapperp | 2010/04/20 22:26:14 | read a packet STOP_PENDING : > 180000 > DEBUG | wrapper | 2010/04/20 22:26:14 | JVM signalled a stop pending with > waitHint of 180000 millis. > > INFO | jvm 1 | 2010/04/20 22:26:14 | Start method stopped > > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: returned > from listener.stop() -> 0 > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: wait for 0 > shutdown locs to be released. > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Send a > packet STOPPED : 0 > > DEBUG | wrapperp | 2010/04/20 22:26:22 | read a packet STOPPED : 0 > DEBUG | wrapper | 2010/04/20 22:26:22 | JVM signalled that it was stopped. > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Closing > socket. > DEBUG | wrapperp | 2010/04/20 22:26:22 | socket read no code (closed?). > > INFO | jvm 1 | 2010/04/20 22:26:23 | WrapperManager Debug: ShutdownHook > complete > DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: > DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code of > 1, setting the wrapper exit code to 1. > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. > STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped > > > Note that at this stage i have both wrapper & my server processes down. > > Thanks for the help.. -- Leif Mortenson Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com lei...@ta... |
|
From: Tomer B <tom...@gm...> - 2010-04-20 21:18:39
|
Hi, I forgot to mention also that If I run my java app (server) without the wrapper on same vms where its being abruptly shut down with the wrapper, then in this case the java app runs with no shutdown - runs fine, for days... Thanks, Tomer On Wed, Apr 21, 2010 at 12:05 AM, Tomer B <tom...@gm...> wrote: > Hi, > > I am currently testing wrapper 3.4.0 on solaris 64 bit machine. > Under regular "physical" machine its already working for days and is fine > (tried that on a couple of machines). > > However if i run the wrapper under vm instances (of vmware) i get abnormal > shutdowns always both to my server and to the wrapper (after about 2 hours > both process are down). > > I'm attaching relevant logs: > Note that I tested a configured vmware for reservation of cpu to one of the > vm instances then on that vm instance it seems that I don't have this > shutdown, i have multiple vm virtual machines on the same physical machine > and the shutdown happens on all of them (except for that instance with that > cpu reservation). I would like vm configuration to be working as well > because I'm thinking of having such a configuration possibly in future in > production. > I also saw this over the web: > http://old.nabble.com/JVM-appears-hung:-VMware,-verbose-garbage-collection-td13470076.html > > Here are relevant logs if you could provide me with information of why > these abnormal shutdowns are happening: > > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: Java VM > Vendor : Sun Microsystems Inc. > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > Name : SunOS > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS > Arch : amd64 > INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: > INFO | jvm 1 | 2010/04/20 19:43:30 | [Loaded > org.tanukisoftware.wrapper.WrapperManager$5 from xxxxxxxxxx (i made this.. > xxxxxx)] > > > DEBUG | wrapperp | 2010/04/20 22:16:09 | read a packet PING : ping > DEBUG | wrapperp | 2010/04/20 22:16:13 | send a packet PING : ping > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Received a > packet PING : ping > INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Send a > packet PING : ping > DEBUG | wrapperp | 2010/04/20 22:16:13 | read a packet PING : ping > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read Timed > out. (Last Ping was 298400 milliseconds ago) > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Read Timed > out. (Last Ping was 596700 milliseconds ago) > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager: JVM did not > exit. Give up. > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > ShutdownHook started > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: > WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Send a > packet STOP : 0 > INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Stopped > checking for control events. > DEBUG | wrapperp | 2010/04/20 22:26:13 | read a packet STOP : 0 > DEBUG | wrapper | 2010/04/20 22:26:13 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2010/04/20 22:26:13 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2010/04/20 22:26:13 | Sending stop signal to JVM > DEBUG | wrapperp | 2010/04/20 22:26:13 | send a packet STOP : NULL > > . > . > . > > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Thread, > Wrapper-Shutdown-Hook, handling the shutdown process. > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: calling > listener.stop() > INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Send a > packet STOP_PENDING : 180000 > > . > . > . > > > DEBUG | wrapperp | 2010/04/20 22:26:14 | read a packet STOP_PENDING : > 180000 > DEBUG | wrapper | 2010/04/20 22:26:14 | JVM signalled a stop pending with > waitHint of 180000 millis. > > INFO | jvm 1 | 2010/04/20 22:26:14 | Start method stopped > > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: returned > from listener.stop() -> 0 > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: > shutdownJVM(0) Thread:Wrapper-Shutdown-Hook > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: wait for 0 > shutdown locs to be released. > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Send a > packet STOPPED : 0 > > DEBUG | wrapperp | 2010/04/20 22:26:22 | read a packet STOPPED : 0 > DEBUG | wrapper | 2010/04/20 22:26:22 | JVM signalled that it was > stopped. > INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Closing > socket. > DEBUG | wrapperp | 2010/04/20 22:26:22 | socket read no code (closed?). > > INFO | jvm 1 | 2010/04/20 22:26:23 | WrapperManager Debug: > ShutdownHook complete > DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: > DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), > source="unknown" > DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM > process status. > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code of > 1, setting the wrapper exit code to 1. > DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. > STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped > > > Note that at this stage i have both wrapper & my server processes down. > > Thanks for the help.. > |
|
From: Tomer B <tom...@gm...> - 2010-04-20 21:05:30
|
Hi, I am currently testing wrapper 3.4.0 on solaris 64 bit machine. Under regular "physical" machine its already working for days and is fine (tried that on a couple of machines). However if i run the wrapper under vm instances (of vmware) i get abnormal shutdowns always both to my server and to the wrapper (after about 2 hours both process are down). I'm attaching relevant logs: Note that I tested a configured vmware for reservation of cpu to one of the vm instances then on that vm instance it seems that I don't have this shutdown, i have multiple vm virtual machines on the same physical machine and the shutdown happens on all of them (except for that instance with that cpu reservation). I would like vm configuration to be working as well because I'm thinking of having such a configuration possibly in future in production. I also saw this over the web: http://old.nabble.com/JVM-appears-hung:-VMware,-verbose-garbage-collection-td13470076.html Here are relevant logs if you could provide me with information of why these abnormal shutdowns are happening: INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: Java VM Vendor : Sun Microsystems Inc. INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS Name : SunOS INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: OS Arch : amd64 INFO | jvm 1 | 2010/04/20 19:43:30 | WrapperManager Debug: INFO | jvm 1 | 2010/04/20 19:43:30 | [Loaded org.tanukisoftware.wrapper.WrapperManager$5 from xxxxxxxxxx (i made this.. xxxxxx)] DEBUG | wrapperp | 2010/04/20 22:16:09 | read a packet PING : ping DEBUG | wrapperp | 2010/04/20 22:16:13 | send a packet PING : ping INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Received a packet PING : ping INFO | jvm 1 | 2010/04/20 22:16:13 | WrapperManager Debug: Send a packet PING : ping DEBUG | wrapperp | 2010/04/20 22:16:13 | read a packet PING : ping . . . INFO | jvm 1 | 2010/04/20 22:21:13 | WrapperManager Debug: Read Timed out. (Last Ping was 298400 milliseconds ago) . . . INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Read Timed out. (Last Ping was 596700 milliseconds ago) INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager: JVM did not exit. Give up. . . . INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: ShutdownHook started INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Send a packet STOP : 0 INFO | jvm 1 | 2010/04/20 22:26:13 | WrapperManager Debug: Stopped checking for control events. DEBUG | wrapperp | 2010/04/20 22:26:13 | read a packet STOP : 0 DEBUG | wrapper | 2010/04/20 22:26:13 | JVM requested a shutdown. (0) DEBUG | wrapper | 2010/04/20 22:26:13 | wrapperStopProcess(0) called. DEBUG | wrapper | 2010/04/20 22:26:13 | Sending stop signal to JVM DEBUG | wrapperp | 2010/04/20 22:26:13 | send a packet STOP : NULL . . . INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Thread, Wrapper-Shutdown-Hook, handling the shutdown process. INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: calling listener.stop() INFO | jvm 1 | 2010/04/20 22:26:14 | WrapperManager Debug: Send a packet STOP_PENDING : 180000 . . . DEBUG | wrapperp | 2010/04/20 22:26:14 | read a packet STOP_PENDING : 180000 DEBUG | wrapper | 2010/04/20 22:26:14 | JVM signalled a stop pending with waitHint of 180000 millis. INFO | jvm 1 | 2010/04/20 22:26:14 | Start method stopped INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: returned from listener.stop() -> 0 INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: shutdownJVM(0) Thread:Wrapper-Shutdown-Hook INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: wait for 0 shutdown locs to be released. INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Send a packet STOPPED : 0 DEBUG | wrapperp | 2010/04/20 22:26:22 | read a packet STOPPED : 0 DEBUG | wrapper | 2010/04/20 22:26:22 | JVM signalled that it was stopped. INFO | jvm 1 | 2010/04/20 22:26:22 | WrapperManager Debug: Closing socket. DEBUG | wrapperp | 2010/04/20 22:26:22 | socket read no code (closed?). INFO | jvm 1 | 2010/04/20 22:26:23 | WrapperManager Debug: ShutdownHook complete DEBUG | wrapper | 2010/04/20 22:26:24 | Signal trapped. Details: DEBUG | wrapper | 2010/04/20 22:26:24 | signal number=18 (SIGCHLD), source="unknown" DEBUG | wrapper | 2010/04/20 22:26:24 | Received SIGCHLD, checking JVM process status. DEBUG | wrapper | 2010/04/20 22:26:24 | JVM process exited with a code of 1, setting the wrapper exit code to 1. DEBUG | wrapper | 2010/04/20 22:26:24 | JVM exited normally. STATUS | wrapper | 2010/04/20 22:26:24 | <-- Wrapper Stopped Note that at this stage i have both wrapper & my server processes down. Thanks for the help.. |
|
From: Leif M. <le...@ta...> - 2010-04-19 17:51:18
|
Sumanth, These features have been under development and we were able to get them completed today. They still need more testing but will be released in our 3.5.0 release in the middle of May. 1) It is now possible to specify a list of Actions for filters on the JVM output. The following example will fire a user event, perform a thread dump, and then restart the JVM: wrapper.filter.trigger.1=java.lang.OutOfMemoryError wrapper.filter.action.1=USER_1, DUMP, RESTART 2) It is now possible to define multiple customer user events which are triggered by the above actions. These events work like any other Wrapper event and can be used to send emails or execute external system commands. http://wrapper.tanukisoftware.org/doc/english/props-event.html For example: wrapper.event.user_1.email=TRUE The ability to chain events is available in all Wrapper Editions, including the Community Edition, but the customer user events are a Professional Edition feature. Cheers, Leif On Mon, Apr 19, 2010 at 1:06 PM, Christian <chr...@ta...> wrote: > Sumanth, > > Thank you for your suggestion. > > We actually have this already put into our ToDo List. > > I have upped your request and will try to implement this in the 3.5.0 > release of the wrapper. > Another feature will be that you will be able to chain more actions if a > certain event occurred. > > > Best Regards, > Christian > > On Fri, 2010-04-16 at 14:01 -0400, Sridhar, Sumanth wrote: >> Since there is already a facility for the wrapper to send out emails, >> it would be nice if the wrapper can be configured to look for >> particular keywords in the application log file, and send email alerts >> for the occurrence of these keywords. >> >> I know it would get much more complex than this, but a simple feature >> should be good to start with. >> >> Regards, >> >> Sumanth Sridhar |
|
From: Christian <chr...@ta...> - 2010-04-19 04:06:50
|
Sumanth, Thank you for your suggestion. We actually have this already put into our ToDo List. I have upped your request and will try to implement this in the 3.5.0 release of the wrapper. Another feature will be that you will be able to chain more actions if a certain event occurred. Best Regards, Christian On Fri, 2010-04-16 at 14:01 -0400, Sridhar, Sumanth wrote: > Since there is already a facility for the wrapper to send out emails, > it would be nice if the wrapper can be configured to look for > particular keywords in the application log file, and send email alerts > for the occurrence of these keywords. > > I know it would get much more complex than this, but a simple feature > should be good to start with. > > > > > > > > Regards, > > Sumanth Sridhar > > Distributed Application Services - NY > Phone: 212-214-4926 > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <le...@ta...> - 2010-04-17 15:53:35
|
jcc, Could you please send me the wrapper.log file that was created when you rebooted your machine? That should provide information about what is happening. Cheers, Leif On Sat, Apr 17, 2010 at 9:06 AM, john <jc...@gm...> wrote: > I was able to quickly code up a java-based windows service and install it. > Successfully started it via the windows control panel/admin tools/services > dialogue. > > However, at boot time the service does not auto-start, even though > auto-start is enabled. Additionally, the event log message states that the > service connection manager was not notified by the service and has > timed-out. > > Is this possibly a wrapper.conf issue ? > > /jcc |
|
From: john <jc...@gm...> - 2010-04-17 00:06:29
|
I was able to quickly code up a java-based windows service and install it. Successfully started it via the windows control panel/admin tools/services dialogue. However, at boot time the service does not auto-start, even though auto-start is enabled. Additionally, the event log message states that the service connection manager was not notified by the service and has timed-out. Is this possibly a wrapper.conf issue ? /jcc |
|
From: Sridhar, S. <sum...@wa...> - 2010-04-16 18:27:02
|
Since there is already a facility for the wrapper to send out emails, it would be nice if the wrapper can be configured to look for particular keywords in the application log file, and send email alerts for the occurrence of these keywords. I know it would get much more complex than this, but a simple feature should be good to start with. Regards, Sumanth Sridhar Distributed Application Services - NY Phone: 212-214-4926 |
|
From: Leif M. <lei...@ta...> - 2010-04-15 16:31:00
|
Tomer, It is most likely possible to get the 64-bit Solaris x86 version to build on older versions if you backport the make files. The first version that we released however was 3.3.0. The 64-bit Solaris Sparc version had been released when we did several of the earlier releases. Cheers, Leif On Thu, Apr 15, 2010 at 6:26 PM, Tomer B <tom...@gm...> wrote: > We supported 64-bit Sparc going back farther, but the first 64-bit x86 > release we did was version 3.3.0. > > How did 64-bit Spac was supported farther if the first release was released > on 3.3.0? by manually compiling the sources of previous releases on > solaris-64 bit? > > Thanks > > On Thu, Apr 15, 2010 at 10:19 AM, Leif Mortenson > <lei...@ta...> wrote: >> >> Tomer, >> Historical Java Service Wrapper releases can be downloaded from the >> following directory. >> http://wrapper.tanukisoftware.org/downloads >> >> We supported 64-bit Sparc going back farther, but the first 64-bit x86 >> release we did was version 3.3.0. >> http://wrapper.tanukisoftware.org/downloads/3.3.0/ >> >> In order for all of the Wrapper's functionally to be operational, it >> is necessary that the "bits" of the Wrapper match the "bits" of the >> JVM. The Wrapper process itself does not matter so much, but the JVM >> needs to load in a native JNI library, libwrapper.so. If the "bits" >> do not match that of the JVM process, then the JVM will not be able to >> load it. >> >> All of the signal handling and several other features require that the >> native library be present. The Wrapper will work without the native >> library, but the JVM process will not be protected as well. The >> Wrapper's pinging will work fine as that is handled in the >> wrapper.jar, within Java code. >> >> There have been a lot of other changes, fixes, and improvements going >> into the Wrapper over the years since 3.1.2 was released. In general, >> we always suggest making use of the latest version. 3.4.0 has proved >> to be very stable to date. >> >> Hope this helps. >> >> Cheers, >> Leif >> >> On Wed, Apr 14, 2010 at 9:41 PM, Tomer B <tom...@gm...> wrote: >> > Does release 3.1.2 supports solaris 64 x86 if not which version started >> > its >> > support? >> > Can I start the java service wrapper in solaris 32 x86 bit and let it >> > run my >> > jvm which will be in solaris x86 64 bit? will it work (including >> > communication - pings from wrapper to my jvm, hooks from wrapper to my >> > app >> > etc). >> > >> > I saw this in release notes: >> > >> > 3.3.1 >> > >> > Fix a problem where the 64-bit Solaris x86 version was unable to load >> > its >> > JNI library. Bug #1992039. >> > >> > 3.3.0 >> > >> > Fix an occasional crash with 64-bit UNIX caused by a native >> > synchronization >> > problem when system signals are trapped. Bug #1614010. >> > is this also related to solaris 64-bit? >> > >> > 3.2.0 >> > >> > Add support for Linux 64-bit PPC and Solaris 32-bit x86 versions. >> > >> > Thanks |
|
From: Tomer B <tom...@gm...> - 2010-04-15 09:27:25
|
We supported 64-bit Sparc going back farther, but the first 64-bit x86 release we did was version 3.3.0. How did 64-bit Spac was supported farther if the first release was released on 3.3.0? by manually compiling the sources of previous releases on solaris-64 bit? Thanks On Thu, Apr 15, 2010 at 10:19 AM, Leif Mortenson < lei...@ta...> wrote: > Tomer, > Historical Java Service Wrapper releases can be downloaded from the > following directory. > http://wrapper.tanukisoftware.org/downloads > > We supported 64-bit Sparc going back farther, but the first 64-bit x86 > release we did was version 3.3.0. > http://wrapper.tanukisoftware.org/downloads/3.3.0/ > > In order for all of the Wrapper's functionally to be operational, it > is necessary that the "bits" of the Wrapper match the "bits" of the > JVM. The Wrapper process itself does not matter so much, but the JVM > needs to load in a native JNI library, libwrapper.so. If the "bits" > do not match that of the JVM process, then the JVM will not be able to > load it. > > All of the signal handling and several other features require that the > native library be present. The Wrapper will work without the native > library, but the JVM process will not be protected as well. The > Wrapper's pinging will work fine as that is handled in the > wrapper.jar, within Java code. > > There have been a lot of other changes, fixes, and improvements going > into the Wrapper over the years since 3.1.2 was released. In general, > we always suggest making use of the latest version. 3.4.0 has proved > to be very stable to date. > > Hope this helps. > > Cheers, > Leif > > On Wed, Apr 14, 2010 at 9:41 PM, Tomer B <tom...@gm...> wrote: > > Does release 3.1.2 supports solaris 64 x86 if not which version started > its > > support? > > Can I start the java service wrapper in solaris 32 x86 bit and let it run > my > > jvm which will be in solaris x86 64 bit? will it work (including > > communication - pings from wrapper to my jvm, hooks from wrapper to my > app > > etc). > > > > I saw this in release notes: > > > > 3.3.1 > > > > Fix a problem where the 64-bit Solaris x86 version was unable to load its > > JNI library. Bug #1992039. > > > > 3.3.0 > > > > Fix an occasional crash with 64-bit UNIX caused by a native > synchronization > > problem when system signals are trapped. Bug #1614010. > > is this also related to solaris 64-bit? > > > > 3.2.0 > > > > Add support for Linux 64-bit PPC and Solaris 32-bit x86 versions. > > > > Thanks > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Leif M. <lei...@ta...> - 2010-04-15 07:19:13
|
Tomer, Historical Java Service Wrapper releases can be downloaded from the following directory. http://wrapper.tanukisoftware.org/downloads We supported 64-bit Sparc going back farther, but the first 64-bit x86 release we did was version 3.3.0. http://wrapper.tanukisoftware.org/downloads/3.3.0/ In order for all of the Wrapper's functionally to be operational, it is necessary that the "bits" of the Wrapper match the "bits" of the JVM. The Wrapper process itself does not matter so much, but the JVM needs to load in a native JNI library, libwrapper.so. If the "bits" do not match that of the JVM process, then the JVM will not be able to load it. All of the signal handling and several other features require that the native library be present. The Wrapper will work without the native library, but the JVM process will not be protected as well. The Wrapper's pinging will work fine as that is handled in the wrapper.jar, within Java code. There have been a lot of other changes, fixes, and improvements going into the Wrapper over the years since 3.1.2 was released. In general, we always suggest making use of the latest version. 3.4.0 has proved to be very stable to date. Hope this helps. Cheers, Leif On Wed, Apr 14, 2010 at 9:41 PM, Tomer B <tom...@gm...> wrote: > Does release 3.1.2 supports solaris 64 x86 if not which version started its > support? > Can I start the java service wrapper in solaris 32 x86 bit and let it run my > jvm which will be in solaris x86 64 bit? will it work (including > communication - pings from wrapper to my jvm, hooks from wrapper to my app > etc). > > I saw this in release notes: > > 3.3.1 > > Fix a problem where the 64-bit Solaris x86 version was unable to load its > JNI library. Bug #1992039. > > 3.3.0 > > Fix an occasional crash with 64-bit UNIX caused by a native synchronization > problem when system signals are trapped. Bug #1614010. > is this also related to solaris 64-bit? > > 3.2.0 > > Add support for Linux 64-bit PPC and Solaris 32-bit x86 versions. > > Thanks |
165 messages has been excluded from this view by a project administrator.
