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: Leif M. <le...@ta...> - 2008-03-10 08:30:35
|
This is possible in the Professional Edition of the upcoming 3.3.0 release. (I know I've said it before. But later this week) Cheers, Leif Suad AlShamsi wrote: > Dear users, > > Is there any way to configure the wrapper to send an email in case > of ERROR log level?! As of now I can only see the the wrapper is > configured with the console and log file appenders. > > Regards > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: Suad A. <sua...@gm...> - 2008-03-09 09:50:17
|
Dear users,
Is there any way to configure the wrapper to send an email in case
of ERROR log level?! As of now I can only see the the wrapper is
configured with the console and log file appenders.
Regards
|
|
From: Leif M. <le...@ta...> - 2008-03-01 04:02:26
|
Mike, The following messages will show up in the Wrapper if you remove the service while it is running: STATUS | wrapper | 2007/10/22 08:42:33 | Service is running. Stopping it... STATUS | wrapper | 2007/10/22 08:42:36 | Fileretr stopped. STATUS | wrapper | 2007/10/22 08:42:36 | Fileretr removed. Something must be running: bin\wrapper -r ..\conf\wrapper.conf Can you think of anything that might be doing so? The next message: ERROR | wrapper | 2007/10/22 08:42:57 | The Fileretr service is not installed - The specified service does not exist as an installed service. (0x424) is caused by someone running: bin\wrapper -t ..\conf\wrapper.conf to start the service. Cheers, Leif Mike Greco wrote: > INFO | jvm 1 | 2007/10/22 08:40:50 | [Requester] - requesting... > INFO | jvm 1 | 2007/10/22 08:41:00 | [Processor] - checking for > request... > INFO | jvm 1 | 2007/10/22 08:41:00 | [Processor] - runtime > exception... > INFO | jvm 1 | 2007/10/22 08:41:00 | [Requester] - polling for > any results... > INFO | jvm 1 | 2007/10/22 08:41:00 | [Requester] - runtime > exception... > INFO | jvm 1 | 2007/10/22 08:42:00 | [Processor] - checking for > request... > INFO | jvm 1 | 2007/10/22 08:42:00 | [Processor] - runtime > exception... > INFO | jvm 1 | 2007/10/22 08:42:00 | [Requester] - requesting... > INFO | jvm 1 | 2007/10/22 08:42:10 | [Requester] - polling for > any results... > INFO | jvm 1 | 2007/10/22 08:42:10 | [Requester] - runtime > exception... > STATUS | wrapper | 2007/10/22 08:42:33 | Service is running. > Stopping it... > STATUS | wrapper | 2007/10/22 08:42:34 | <-- Wrapper Stopped > STATUS | wrapper | 2007/10/22 08:42:36 | Fileretr stopped. > STATUS | wrapper | 2007/10/22 08:42:36 | Fileretr removed. > ERROR | wrapper | 2007/10/22 08:42:57 | The Fileretr service is not > installed - The specified service does not exist as an installed > service. (0x424) > > Any ideas on why the service would be removed? In a thread, my java > code captures RuntimeException and then sleeps 20 seconds, then loops > again doing the same thing. It encountered several runtimes in a row > (for hours most likely) and then suddenly this series of wrapper > status messages. > > Should I put the following property in my wrapper.conf? > # restart on exit regardless of exit code > wrapper.on_exit.default=RESTART > > I'm not sure this is appropriate. Is service removal the default > behavior if the JVM exists? Here's my entire wrapper.conf if this > helps any: > > # Java Application > wrapper.java.command=java > > # Java Main class. This class must implement the WrapperListener > interface > # or guarantee that the WrapperManager class is initialized. Helper > # classes are provided to do this for you. See the Integration section > # of the documentation for details. > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > > # Java Classpath (include wrapper.jar) Add class path elements as > # needed starting from 1 > wrapper.java.classpath.1=../lib > wrapper.java.classpath.2=../lib/wrapper.jar > wrapper.java.classpath.3=../lib/junit-3.8.1.jar > wrapper.java.classpath.4=../lib/spring-core-1.2.5.jar > wrapper.java.classpath.5=../lib/spring-mock-1.2.5.jar > wrapper.java.classpath.6=../lib/spring-beans-1.2.5.jar > wrapper.java.classpath.7=../lib/spring-context-1.2.5.jar > wrapper.java.classpath.8=../lib/commons-logging-1.0.4.jar > wrapper.java.classpath.9=../lib/spring-remoting-1.2.5.jar > wrapper.java.classpath.10=../lib/spring-aop-1.2.5.jar > wrapper.java.classpath.11=../lib/spring-web-1.2.5.jar > wrapper.java.classpath.12=../lib/spring-webmvc-1.2.5.jar > wrapper.java.classpath.13=../lib/servlet-api.jar > wrapper.java.classpath.14=../lib/commons-httpclient-3.0.jar > wrapper.java.classpath.15=../lib/commons-codec-1.2.jar > wrapper.java.classpath.16=../lib/jai-codec-1.1.3.jar > wrapper.java.classpath.17=../lib/jai-core-1.1.3.jar > wrapper.java.classpath.18=../lib/jai-imageio-1.1.jar > wrapper.java.classpath.19=../lib/spring-jdbc-1.2.5.jar > wrapper.java.classpath.20=../lib/spring-dao-1.2.5.jar > wrapper.java.classpath.21=../lib/opencsv-1.6.jar > wrapper.java.classpath.22=../lib/fileretr-1.0.jar > wrapper.java.classpath.23=../lib/fileretrClient-1.0.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=../lib > > # Java Additional Parameters > wrapper.java.additional.1=-Dcom.sun.media.jai.disableMediaLib=true > > # Initial Java Heap Size (in MB) > wrapper.java.initmemory=128 > > # Maximum Java Heap Size (in MB) > wrapper.java.maxmemory=128 > > # Application parameters. Add parameters as needed starting from 1 > wrapper.app.parameter.1=com.greco.fileretr.client.http.FileRequestByExtClientService > > #******************************************************************** > # Wrapper Logging Properties > #******************************************************************** > # Format of output for the console. (See docs for formats) > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > wrapper.console.loglevel=INFO > > # Log file to use for wrapper output logging. > wrapper.logfile=../logs/wrapper.log > > # Format of output for the log file. (See docs for formats) > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > wrapper.logfile.loglevel=INFO > > # 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=1m > > # 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=4 > > # Log Level for sys/event log output. (See docs for log levels) > wrapper.syslog.loglevel=NONE > > #******************************************************************** > # Wrapper Windows Properties > #******************************************************************** > # Title to use when running as a console > wrapper.console.title=Fileretr > > #******************************************************************** > # 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.ntservice.name=Fileretr > > # Display name of the service > wrapper.ntservice.displayname=Fileretr > > # Description of the service > wrapper.ntservice.description=Fileretr > > # Service dependencies. Add dependencies as needed starting from 1 > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > wrapper.ntservice.starttype=AUTO_START > > # Allow the service to interact with the desktop. > wrapper.ntservice.interactive=false > > # restart on exit regardless of exit code > wrapper.on_exit.default=RESTART > > > Thanks in advance. > - Mike |
|
From: Nicolas V. <ni...@va...> - 2008-02-29 14:23:22
|
Gabriel TESSIER a écrit : > FATAL | wrapper | 2008/02/29 10:30:12 | Unable to execute Java > command. Le fichier spécifié est introuvable. (0x2) > FATAL | wrapper | 2008/02/29 10:30:12 | "%JAVA_HOME%\bin\java" > -Djava.library.path="../lib" -classpath > "../lib/wrapper.jar;%JAVA_HOME%/lib/tools.jar;MySoftware.jar" > -Dwrapper.key="QzZXI7r6LXg3smLK" -Dwrapper.port=32000 > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > -Dwrapper.pid=1112 -Dwrapper.version="3.2.3" > -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 > org.tanukisoftware.wrapper.WrapperSimpleApp com.mycompany.core.Main 1 > FATAL | wrapper | 2008/02/29 10:30:12 | Critical error: wait for JVM > process failed > > My %JAVA_HOME% = C:\Program Files\Java\jdk1.6.0_03 > > What's wrong? The wrapper does not find %JAVA_HOME% Does the %JAVA_HOME% variable belong to the system or user ?? It's look like the %JAVA_HOME% is a user variable, so windows services don't have access to this variable. Nicolas |
|
From: Gabriel T. <gab...@lo...> - 2008-02-29 13:42:19
|
Hi, I setup the JSWrapper on PC1 with windows XP ==== OK Copy the Same on PC2 with windows Vista ===== OK Copy the Same on PC3 with windows Vista ===== OK Copy the Same on PC4 with windows XP ===== NOOOOOOOOO Here the wrapper log of PC4 : --> Wrapper Started as Service STATUS | wrapper | 2008/02/29 10:30:12 | Launching a JVM... FATAL | wrapper | 2008/02/29 10:30:12 | Unable to execute Java command. Le fichier spécifié est introuvable. (0x2) FATAL | wrapper | 2008/02/29 10:30:12 | "%JAVA_HOME%\bin\java" -Djava.library.path="../lib" -classpath "../lib/wrapper.jar;%JAVA_HOME%/lib/tools.jar;MySoftware.jar" -Dwrapper.key="QzZXI7r6LXg3smLK" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=1112 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp com.mycompany.core.Main 1 FATAL | wrapper | 2008/02/29 10:30:12 | Critical error: wait for JVM process failed My %JAVA_HOME% = C:\Program Files\Java\jdk1.6.0_03 What's wrong??? -- Cordialement. Gabriel TESSIER LOGOSAPIENCE 3, Rue Pierre et Marie CURIE 49070 ST JEAN DE LINIERES +33 (0)2.41.36.81.41 |
|
From: Mike G. <mg...@ch...> - 2008-02-29 07:06:53
|
INFO | jvm 1 | 2007/10/22 08:40:50 | [Requester] - requesting... INFO | jvm 1 | 2007/10/22 08:41:00 | [Processor] - checking for request... INFO | jvm 1 | 2007/10/22 08:41:00 | [Processor] - runtime exception... INFO | jvm 1 | 2007/10/22 08:41:00 | [Requester] - polling for any results... INFO | jvm 1 | 2007/10/22 08:41:00 | [Requester] - runtime exception... INFO | jvm 1 | 2007/10/22 08:42:00 | [Processor] - checking for request... INFO | jvm 1 | 2007/10/22 08:42:00 | [Processor] - runtime exception... INFO | jvm 1 | 2007/10/22 08:42:00 | [Requester] - requesting... INFO | jvm 1 | 2007/10/22 08:42:10 | [Requester] - polling for any results... INFO | jvm 1 | 2007/10/22 08:42:10 | [Requester] - runtime exception... STATUS | wrapper | 2007/10/22 08:42:33 | Service is running. Stopping it... STATUS | wrapper | 2007/10/22 08:42:34 | <-- Wrapper Stopped STATUS | wrapper | 2007/10/22 08:42:36 | Fileretr stopped. STATUS | wrapper | 2007/10/22 08:42:36 | Fileretr removed. ERROR | wrapper | 2007/10/22 08:42:57 | The Fileretr service is not installed - The specified service does not exist as an installed service. (0x424) Any ideas on why the service would be removed? In a thread, my java code captures RuntimeException and then sleeps 20 seconds, then loops again doing the same thing. It encountered several runtimes in a row (for hours most likely) and then suddenly this series of wrapper status messages. Should I put the following property in my wrapper.conf? # restart on exit regardless of exit code wrapper.on_exit.default=RESTART I'm not sure this is appropriate. Is service removal the default behavior if the JVM exists? Here's my entire wrapper.conf if this helps any: # Java Application wrapper.java.command=java # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=../lib wrapper.java.classpath.2=../lib/wrapper.jar wrapper.java.classpath.3=../lib/junit-3.8.1.jar wrapper.java.classpath.4=../lib/spring-core-1.2.5.jar wrapper.java.classpath.5=../lib/spring-mock-1.2.5.jar wrapper.java.classpath.6=../lib/spring-beans-1.2.5.jar wrapper.java.classpath.7=../lib/spring-context-1.2.5.jar wrapper.java.classpath.8=../lib/commons-logging-1.0.4.jar wrapper.java.classpath.9=../lib/spring-remoting-1.2.5.jar wrapper.java.classpath.10=../lib/spring-aop-1.2.5.jar wrapper.java.classpath.11=../lib/spring-web-1.2.5.jar wrapper.java.classpath.12=../lib/spring-webmvc-1.2.5.jar wrapper.java.classpath.13=../lib/servlet-api.jar wrapper.java.classpath.14=../lib/commons-httpclient-3.0.jar wrapper.java.classpath.15=../lib/commons-codec-1.2.jar wrapper.java.classpath.16=../lib/jai-codec-1.1.3.jar wrapper.java.classpath.17=../lib/jai-core-1.1.3.jar wrapper.java.classpath.18=../lib/jai-imageio-1.1.jar wrapper.java.classpath.19=../lib/spring-jdbc-1.2.5.jar wrapper.java.classpath.20=../lib/spring-dao-1.2.5.jar wrapper.java.classpath.21=../lib/opencsv-1.6.jar wrapper.java.classpath.22=../lib/fileretr-1.0.jar wrapper.java.classpath.23=../lib/fileretrClient-1.0.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=../lib # Java Additional Parameters wrapper.java.additional.1=-Dcom.sun.media.jai.disableMediaLib=true # Initial Java Heap Size (in MB) wrapper.java.initmemory=128 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=128 # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=com.greco.fileretr.client.http.FileRequestByExtClientService #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=PM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=INFO # Log file to use for wrapper output logging. wrapper.logfile=../logs/wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=INFO # 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=1m # 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=4 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=NONE #******************************************************************** # Wrapper Windows Properties #******************************************************************** # Title to use when running as a console wrapper.console.title=Fileretr #******************************************************************** # 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.ntservice.name=Fileretr # Display name of the service wrapper.ntservice.displayname=Fileretr # Description of the service wrapper.ntservice.description=Fileretr # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1= # Mode in which the service is installed. AUTO_START or DEMAND_START wrapper.ntservice.starttype=AUTO_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=false # restart on exit regardless of exit code wrapper.on_exit.default=RESTART Thanks in advance. - Mike |
|
From: Sergio W. <ser...@ev...> - 2008-02-28 14:39:45
|
Thank you very much for your kind offer to help, but I kind of "fixed" the problem. I totally forgot that you can do a hotdeploy on Tomcat so I don't need to stop und restart it with cruisecontrol and therefore I don't need to wrap it (sometimes I tend to think much more complicated than necessary :-)). Greets, Sergio Leif Mortenson schrieb: > Sergio, > No, any exceptions thrown by the wrapped application will look normal. > They do not pass through the Wrapper.dll (native component) in any > way. > > The message you are seeing is that the wrapper is not able to locate > its native library. This is a library path problem and is unrelated to > the wrapped application. > > If you could post your wrapper.conf and explain the relative locations > of the wrapper.exe and wrapper.dll files I could probably tell you right > away what the problem is. > > Cheers, > Leif > > Sergio Weigel wrote: > >> Thanx for your rapid reply, Leif. >> You're right, there seems to be a problem with the Tomcat configuration. >> I guess, the mentioned error message from the wrapper.dll occurs, if >> the wrapped application throws exceptions. >> Am I right on that? >> >> Greets, Sergio >> >> Leif Mortenson schrieb: >> >>> Sergio, >>> Try setting the wrapper.java.command.loglevel=INFO property. >>> It will show the full generated Java command line. The problem >>> might be more apparent looking at that. >>> >>> The java library path will be the problem. That is all loaded before >>> any tomcat code is executed, so it can't be anything to do with >>> Tomcat itself. >>> >>> Cheers, >>> Leif >>> >>> serdsch wrote: >>> >>> >>>> Hello, >>>> >>>> I try to wrap Tomcat 6.0 to be able to control it with automated builds >>>> using cruisecontrol's antpublisher. Tomcat should publish the build results >>>> and I have to run it as a Windows service because otherwise cruisecontrol >>>> wont continue when the server is started as it keeps waiting for the Ant >>>> task to complete. >>>> Wrapping worked perfectly fine with JBoss, but with Tomcat I have the >>>> following problems. >>>> >>>> I read the manual for wrapping Tomcat 4.x on Tanuki's website: >>>> http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html >>>> >>>> I did everything the same with Tomcat 6.0 but when I execute the Tomcat.bat >>>> it can't load the wrapper.dll: >>>> >>>> Unable to load the wrapper's native library 'wrapper.dll'. >>>> The file is located on the path at the following location but could not be >>>> loaded. >>>> >>>> The logged in user has the rights to read the file and I use a 32-bit >>>> Windows with a 32-bit Java version and a 32-bit wrapper. >>>> >>>> Any idea? >>>> Or is there maybe another way to control Tomcat with cruisecontrol? >>>> >>>> Thx, Sergio >>>> >>>> >>>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Wrapper-user mailing list >>> Wra...@li... >>> https://lists.sourceforge.net/lists/listinfo/wrapper-user >>> >>> >> -- >> Sergio Weigel >> IT-Consultant >> >> *** evodion IT - weil Standard nur Mittelmaß ist *** >> >> evodion Information Technologies GmbH >> Högerdamm 41 >> 20097 Hamburg >> Geschäftsführer: Wolfgang Wulf, Frank Hunold >> Handelsregister: Amtsgericht Hamburg >> HRB 86622 >> www.evodion.de >> >> Tel : +49 (40)2714340-35 >> Fax : +49 (40)2714340-37 >> Ser...@ev... >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > -- Sergio Weigel IT-Consultant *** evodion IT - weil Standard nur Mittelmaß ist *** evodion Information Technologies GmbH Högerdamm 41 20097 Hamburg Geschäftsführer: Wolfgang Wulf, Frank Hunold Handelsregister: Amtsgericht Hamburg HRB 86622 www.evodion.de Tel : +49 (40)2714340-35 Fax : +49 (40)2714340-37 Ser...@ev... |
|
From: Leif M. <le...@ta...> - 2008-02-28 14:22:23
|
Sergio, No, any exceptions thrown by the wrapped application will look normal. They do not pass through the Wrapper.dll (native component) in any way. The message you are seeing is that the wrapper is not able to locate its native library. This is a library path problem and is unrelated to the wrapped application. If you could post your wrapper.conf and explain the relative locations of the wrapper.exe and wrapper.dll files I could probably tell you right away what the problem is. Cheers, Leif Sergio Weigel wrote: > Thanx for your rapid reply, Leif. > You're right, there seems to be a problem with the Tomcat configuration. > I guess, the mentioned error message from the wrapper.dll occurs, if > the wrapped application throws exceptions. > Am I right on that? > > Greets, Sergio > > Leif Mortenson schrieb: >> Sergio, >> Try setting the wrapper.java.command.loglevel=INFO property. >> It will show the full generated Java command line. The problem >> might be more apparent looking at that. >> >> The java library path will be the problem. That is all loaded before >> any tomcat code is executed, so it can't be anything to do with >> Tomcat itself. >> >> Cheers, >> Leif >> >> serdsch wrote: >> >>> Hello, >>> >>> I try to wrap Tomcat 6.0 to be able to control it with automated builds >>> using cruisecontrol's antpublisher. Tomcat should publish the build results >>> and I have to run it as a Windows service because otherwise cruisecontrol >>> wont continue when the server is started as it keeps waiting for the Ant >>> task to complete. >>> Wrapping worked perfectly fine with JBoss, but with Tomcat I have the >>> following problems. >>> >>> I read the manual for wrapping Tomcat 4.x on Tanuki's website: >>> http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html >>> >>> I did everything the same with Tomcat 6.0 but when I execute the Tomcat.bat >>> it can't load the wrapper.dll: >>> >>> Unable to load the wrapper's native library 'wrapper.dll'. >>> The file is located on the path at the following location but could not be >>> loaded. >>> >>> The logged in user has the rights to read the file and I use a 32-bit >>> Windows with a 32-bit Java version and a 32-bit wrapper. >>> >>> Any idea? >>> Or is there maybe another way to control Tomcat with cruisecontrol? >>> >>> Thx, Sergio >>> >>> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> > > > -- > Sergio Weigel > IT-Consultant > > *** evodion IT - weil Standard nur Mittelmaß ist *** > > evodion Information Technologies GmbH > Högerdamm 41 > 20097 Hamburg > Geschäftsführer: Wolfgang Wulf, Frank Hunold > Handelsregister: Amtsgericht Hamburg > HRB 86622 > www.evodion.de > > Tel : +49 (40)2714340-35 > Fax : +49 (40)2714340-37 > Ser...@ev... > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Sergio W. <ser...@ev...> - 2008-02-28 12:42:19
|
Thanx for your rapid reply, Leif. You're right, there seems to be a problem with the Tomcat configuration. I guess, the mentioned error message from the wrapper.dll occurs, if the wrapped application throws exceptions. Am I right on that? Greets, Sergio Leif Mortenson schrieb: > Sergio, > Try setting the wrapper.java.command.loglevel=INFO property. > It will show the full generated Java command line. The problem > might be more apparent looking at that. > > The java library path will be the problem. That is all loaded before > any tomcat code is executed, so it can't be anything to do with > Tomcat itself. > > Cheers, > Leif > > serdsch wrote: > >> Hello, >> >> I try to wrap Tomcat 6.0 to be able to control it with automated builds >> using cruisecontrol's antpublisher. Tomcat should publish the build results >> and I have to run it as a Windows service because otherwise cruisecontrol >> wont continue when the server is started as it keeps waiting for the Ant >> task to complete. >> Wrapping worked perfectly fine with JBoss, but with Tomcat I have the >> following problems. >> >> I read the manual for wrapping Tomcat 4.x on Tanuki's website: >> http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html >> >> I did everything the same with Tomcat 6.0 but when I execute the Tomcat.bat >> it can't load the wrapper.dll: >> >> Unable to load the wrapper's native library 'wrapper.dll'. >> The file is located on the path at the following location but could not be >> loaded. >> >> The logged in user has the rights to read the file and I use a 32-bit >> Windows with a 32-bit Java version and a 32-bit wrapper. >> >> Any idea? >> Or is there maybe another way to control Tomcat with cruisecontrol? >> >> Thx, Sergio >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > -- Sergio Weigel IT-Consultant *** evodion IT - weil Standard nur Mittelmaß ist *** evodion Information Technologies GmbH Högerdamm 41 20097 Hamburg Geschäftsführer: Wolfgang Wulf, Frank Hunold Handelsregister: Amtsgericht Hamburg HRB 86622 www.evodion.de Tel : +49 (40)2714340-35 Fax : +49 (40)2714340-37 Ser...@ev... |
|
From: Steven A Moussa/M. <Ste...@ma...> - 2008-02-28 12:03:29
|
I will be out of the office starting 02/25/2008 and will not return until 03/03/2008. I will respond to your message when I return. Please contact Ian Zaleski for any urgent issues. |
|
From: Leif M. <le...@ta...> - 2008-02-28 11:15:37
|
Sergio, Try setting the wrapper.java.command.loglevel=INFO property. It will show the full generated Java command line. The problem might be more apparent looking at that. The java library path will be the problem. That is all loaded before any tomcat code is executed, so it can't be anything to do with Tomcat itself. Cheers, Leif serdsch wrote: > Hello, > > I try to wrap Tomcat 6.0 to be able to control it with automated builds > using cruisecontrol's antpublisher. Tomcat should publish the build results > and I have to run it as a Windows service because otherwise cruisecontrol > wont continue when the server is started as it keeps waiting for the Ant > task to complete. > Wrapping worked perfectly fine with JBoss, but with Tomcat I have the > following problems. > > I read the manual for wrapping Tomcat 4.x on Tanuki's website: > http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html > > I did everything the same with Tomcat 6.0 but when I execute the Tomcat.bat > it can't load the wrapper.dll: > > Unable to load the wrapper's native library 'wrapper.dll'. > The file is located on the path at the following location but could not be > loaded. > > The logged in user has the rights to read the file and I use a 32-bit > Windows with a 32-bit Java version and a 32-bit wrapper. > > Any idea? > Or is there maybe another way to control Tomcat with cruisecontrol? > > Thx, Sergio > |
|
From: serdsch <ser...@ev...> - 2008-02-28 10:35:17
|
Hello, I try to wrap Tomcat 6.0 to be able to control it with automated builds using cruisecontrol's antpublisher. Tomcat should publish the build results and I have to run it as a Windows service because otherwise cruisecontrol wont continue when the server is started as it keeps waiting for the Ant task to complete. Wrapping worked perfectly fine with JBoss, but with Tomcat I have the following problems. I read the manual for wrapping Tomcat 4.x on Tanuki's website: http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html I did everything the same with Tomcat 6.0 but when I execute the Tomcat.bat it can't load the wrapper.dll: Unable to load the wrapper's native library 'wrapper.dll'. The file is located on the path at the following location but could not be loaded. The logged in user has the rights to read the file and I use a 32-bit Windows with a 32-bit Java version and a 32-bit wrapper. Any idea? Or is there maybe another way to control Tomcat with cruisecontrol? Thx, Sergio -- View this message in context: http://www.nabble.com/Problems-wrapping-Tomcat-6.0-tp15733655p15733655.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Ben L. <Ben...@As...> - 2008-02-21 23:29:39
|
Hi Leif, Thank you very much for your prompt reply. It turned out that, indeed, the java application rather than the wrapper was mal-configured. Setting wrapper.java.command.loglevel=INFO was very useful while tracking this down. I really appreciate your help - thank you! Cheers, Ben -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of wra...@li... Sent: Tuesday, February 19, 2008 10:52 PM To: wra...@li... Subject: Wrapper-user Digest, Vol 21, Issue 9 Send Wrapper-user mailing list submissions to wra...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/wrapper-user or, via email, send a message with subject or body 'help' to wra...@li... You can reach the person managing the list at wra...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Wrapper-user digest..." Today's Topics: 1. Re: Wrapper Monopolizes CPU (Leif Mortenson) 2. Re: Issue with wrapper (Leif Mortenson) 3. Re: Issue with wrapper (Ramakrishna Bv Sanku) ---------------------------------------------------------------------- Message: 1 Date: Wed, 20 Feb 2008 14:20:53 +0900 From: Leif Mortenson <le...@ta...> Subject: Re: [Wrapper-user] Wrapper Monopolizes CPU To: wra...@li... Message-ID: <47B...@ta...> Content-Type: text/plain; charset=windows-1252; format=flowed Ben, I have never seen or heard of any examples of the Wrapper or its Java component consuming lots of CPU due to the Wrapper. To confirm, it is the java process and not the wrapper process that is using up all the CPU. You might want to try doing some profiling of your JVM to narrow down the cause. From you classpath, and configManager.VPNManagement.RegistrarDaemon class, it is likely that more is going on in your application than the loop below. I have seen cases where the java application is not being configured as expected when running under the wrapper. An incorrect path for example. Something like that could cause some thrashing of an outer loop depending on how the error handling code was written. You can review the full command used to launch the JVM by adding the following to your wrapper.conf wrapper.java.command.loglevel=INFO Cheers, Leif Ben Leibert wrote: > > I?m using version 3.2.3 of the wrapper on SuSe Linux 10.1 alongside > version 1.5 of Java. The ?top? command shows the wrapper to > consistently monopolize the CPU, which I?d ~really~ appreciate help > resolving. The code I?m testing with looks as follows: > > while(true) > > { > > System.out.println("This just ran"); > > Thread.currentThread().sleep(3000); > > } > > Only when run via the wrapper does this dominate the processor. > Neither changing the wrapper.ping.interval nor the priority (nice) > properties has had any noticeable affect. My configuration files are > included below. Thanks in advance for any help! > > Cheers, > > Ben > (snip) ------------------------------ Message: 2 Date: Wed, 20 Feb 2008 15:23:56 +0900 From: Leif Mortenson <le...@ta...> Subject: Re: [Wrapper-user] Issue with wrapper To: wra...@li... Message-ID: <47B...@ta...> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Ram, I am a bit of a loss as to what is happening here assuming that you sent me the full logs. DEBUG | wrapperp | 2008/02/08 01:39:48 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:49 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:49 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:53 | send a packet PING : ping DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053) DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet not sent SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE The Wrapper should be attempting to send a PING packet once every 5 seconds as happens at 01:39:48 and 01:39:53. But then there is nothing. The JVM does say that it received the ping and there are no more attempts to send by the Wrapper. The next bessage is 49 seconds later at 01:40:42 when the Service Manager sends an interrogate control code. Both of your logs show the same thing. The wrapper sends a ping which is never acknowledged by the Java side of the Wrapper then about 50 seconds later an interrogate control code shows up which fails to be sent to the JVM. In addition to the wrapper.debug=TRUE property, can you also try setting wrapper.state_output=TRUE This will produce a LOT of output, but it might also shed more light on what is happening to you. Cheers, Leif Ramakrishna Bv Sanku wrote: > Hi Leif Mortenson, > > Thank you for quick response. Please check my answers in Blue for the > questions. > > Please find the attachment for the log. > > > I have checked the logs on other days as well , this issue is occuring > but for the recovery time is less, please check the log below: > > INFO | jvm 9 | 2008/02/10 01:28:46 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/10 01:28:46 | read a packet PING : ok > DEBUG | wrapper | 2008/02/10 01:28:46 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/10 01:28:50 | send a packet PING : ping > INFO | jvm 9 | 2008/02/10 01:28:50 | Received a packet PING : ping > INFO | jvm 9 | 2008/02/10 01:28:50 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/10 01:28:50 | read a packet PING : ok > DEBUG | wrapper | 2008/02/10 01:28:50 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/10 01:28:54 | send a packet PING : ping > DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/10 01:29:25 | send a packet > SERVICE_CONTROL_CODE : 4 DEBUG | wrapperp | 2008/02/10 01:29:25 | > socket send failed. (10053) > DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 9 | 2008/02/10 01:29:25 | Read Timed out. (Last Ping > was 30300 milliseconds ago) > INFO | jvm 9 | 2008/02/10 01:29:25 | Wrapper Manager: The Wrapper > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > resynch. > INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet RESTART : restart > INFO | jvm 9 | 2008/02/10 01:29:25 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 9 | 2008/02/10 01:29:25 | calling listener.stop() > INFO | jvm 9 | 2008/02/10 01:29:25 | Waiting for > WrapperListener.stop runner thread to complete. > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner > thread started. > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperSimpleApp: stop(1) > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner > thread stopped. > INFO | jvm 9 | 2008/02/10 01:29:25 | returned from > listener.stop() -> 1 > INFO | jvm 9 | 2008/02/10 01:29:25 | shutdownJVM(1) > Thread:Wrapper-Connection > INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet STOPPED : 1 > INFO | jvm 9 | 2008/02/10 01:29:25 | Closing socket. > INFO | jvm 9 | 2008/02/10 01:29:25 | calling System.exit(1) > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,188|INFO|SequencerTool|shutting down > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,266|INFO|SequencerTool|ok. > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,266|INFO|SequencerTool|stopped. > DEBUG | wrapperp | 2008/02/10 01:29:25 | server listening on port 32002. > INFO | wrapper | 2008/02/10 01:29:25 | Wrapper Process has not > received any CPU time for 30 seconds. Extending timeouts. > DEBUG | wrapper | 2008/02/10 01:29:25 | JVM process exited with a > code of 1, setting the wrapper exit code to 1. > ERROR | wrapper | 2008/02/10 01:29:25 | JVM exited unexpectedly. > DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/10 01:29:25 | socket not open, so packet > not sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE > DEBUG | wrapper | 2008/02/10 01:29:25 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2008/02/10 01:29:29 | Classpath element, > wrapper.java.classpath.10, does not exist: ../classes STATUS | wrapper > | 2008/02/10 01:29:29 | Launching a JVM... > ______________________________________________________________________ > ___________________________ > > INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet > SERVICE_CONTROL_CODE : 4 > INFO | jvm 7 | 2008/02/06 02:31:49 | ServiceControlCode from > Wrapper with code 4 > DEBUG | wrapperp | 2008/02/06 02:31:49 | send a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:49 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/06 02:31:50 | read a packet PING : ok > DEBUG | wrapper | 2008/02/06 02:31:50 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/06 02:31:54 | send a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:54 | Received a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:54 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/06 02:31:54 | read a packet PING : ok > DEBUG | wrapper | 2008/02/06 02:31:54 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/06 02:31:58 | send a packet PING : ping > DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/06 02:32:50 | send a packet > SERVICE_CONTROL_CODE : 4 DEBUG | wrapperp | 2008/02/06 02:32:50 | > socket send failed. (10053) > DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE > DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/06 02:32:50 | socket not open, so packet > not sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 7 | 2008/02/06 02:32:50 | Read Timed out. (Last Ping > was 30400 milliseconds ago) > INFO | jvm 7 | 2008/02/06 02:32:50 | Wrapper Manager: The Wrapper > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > resynch. > INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet RESTART : restart > INFO | jvm 7 | 2008/02/06 02:32:50 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 7 | 2008/02/06 02:32:50 | calling listener.stop() > INFO | jvm 7 | 2008/02/06 02:32:50 | Waiting for > WrapperListener.stop runner thread to complete. > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner > thread started. > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperSimpleApp: stop(1) > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner > thread stopped. > INFO | jvm 7 | 2008/02/06 02:32:50 | returned from > listener.stop() -> 1 > INFO | jvm 7 | 2008/02/06 02:32:50 | shutdownJVM(1) > Thread:Wrapper-Connection > INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet STOPPED : 1 > INFO | jvm 7 | 2008/02/06 02:32:50 | Closing socket. > INFO | jvm 7 | 2008/02/06 02:32:50 | calling System.exit(1) > INFO | jvm 7 | 2008/02/06 02:32:50 | 2008-02-06 > 02:32:26,750|INFO|SequencerTool|shutting down DEBUG | wrapperp | > 2008/02/06 02:32:50 | server listening on port 32002. > INFO | wrapper | 2008/02/06 02:32:50 | Wrapper Process has not > received any CPU time for 51 seconds. Extending timeouts. > DEBUG | wrapper | 2008/02/06 02:32:50 | JVM process exited with a > code of 1, setting the wrapper exit code to 1. > ERROR | wrapper | 2008/02/06 02:32:50 | JVM exited unexpectedly. > DEBUG | wrapper | 2008/02/06 02:32:50 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2008/02/06 02:32:54 | Classpath element, > wrapper.java.classpath.10, does not exist: ../classes STATUS | wrapper > | 2008/02/06 02:32:54 | Launching a JVM... > > Best Regards, > Ram > IBM Global Services India Pvt. Ltd. > Mindspace, Survey No 64, APIIC Software Layout, Hi-tech City, > Hyderabad -500 081 INDIA > Phone: +91-40-66956756 > > > *Leif Mortenson <le...@ta...>* Sent by: > wra...@li... > > 02/08/2008 01:17 PM > Please respond to > wra...@li... > > > > To > wra...@li... > cc > > Subject > Re: [Wrapper-user] Issue with wrapper > > > > > > > > > > Ramakrishna, > According to the log, the backend socket between the Wrapper and > Java process was somehow closed. The Wrapper is failing saying > that it can no longer communicate with the JVM. It keeps going though > because the JVM process is still running. > > The JVM then gives up after around 30 seconds because it has not > received any communications from the Wrapper for that long. This is a > safety feature to shut the JVM process down just in case the Wrapper > process should ever crash. > > Once the Wrapper detects that the JVM is shutdown, it is correctly > restarting the JVM. > > > The question is why is the backend socket being closed? This is not a > problem I have ever seen or heard of in the past. Is anything else in > the log file earlier than what you sent? > > How easy is this to reproduce? > *A: We cannot reproduce.* > > Does it always happen at the same time? > *A: No,it does not happen at the sametime.* > > Is it possible that some other application on your system is closing > the socket? > *A:Can't say whether someother application on the system might be > trying to close the socket.Another two applications are running on the > same machine with wrapper having same configuration.* > > Is your system under load at the time of this reset? > *A: Yes, it was under load.* > > Does your Java application respond during the 30 seconds between the > socket being closed and the JVM shutting itself down? > *A: Can't answer* > > Cheers, > Leif > > Ramakrishna Bv Sanku wrote: > > > > Hi All, > > > > I came across a issue with wrapper, the Wrapper is getting degraded > > for sometime and getting into normal state after some time. Please > > check the wrapper log below. > > > > Can anyone help me and provide a solution, how can this be rectified. > > > > *Information from the wrapper log* > > WrapperManager class initialized by thread: main Using classloader: > > sun.misc.Launcher$AppClassLoader@27e3570f > > ............... > > Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org > > ............... > > > > Extract from wrapper log > > > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet > > SERVICE_CONTROL_CODE : 4 DEBUG | wrapperp | 2008/02/08 01:40:42 | > > socket send failed. (10053) > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet > > not sent SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > INFO | jvm 8 | 2008/02/08 01:40:42 | Read Timed out. (Last Ping > > was 30600 milliseconds ago) > > INFO | jvm 8 | 2008/02/08 01:40:42 | Wrapper Manager: The Wrapper > > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > > resynch. > > INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet RESTART : > restart > > INFO | jvm 8 | 2008/02/08 01:40:42 | Thread, Wrapper-Connection, > > handling the shutdown process. > > INFO | jvm 8 | 2008/02/08 01:40:42 | calling listener.stop() > > INFO | jvm 8 | 2008/02/08 01:40:42 | Waiting for > > WrapperListener.stop runner thread to complete. > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner > > thread started. > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperSimpleApp: stop(1) > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner > > thread stopped. > > INFO | jvm 8 | 2008/02/08 01:40:42 | returned from > > listener.stop() -> 1 > > INFO | jvm 8 | 2008/02/08 01:40:42 | shutdownJVM(1) > > Thread:Wrapper-Connection > > INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet STOPPED : 1 > > INFO | jvm 8 | 2008/02/08 01:40:42 | Closing socket. > > INFO | jvm 8 | 2008/02/08 01:40:42 | calling System.exit(1) > > INFO | jvm 8 | 2008/02/08 01:40:42 | 2008-02-08 > > 01:40:22,031|INFO|SequencerTool|shutting down DEBUG | wrapperp | > > 2008/02/08 01:40:42 | server listening on port > 32002. > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet > > not sent SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > INFO | wrapper | 2008/02/08 01:40:42 | Wrapper Process has not > > received any CPU time for 48 seconds. Extending timeouts. > > DEBUG | wrapper | 2008/02/08 01:40:42 | JVM process exited with a > > code of 1, setting the wrapper exit code to 1. > > ERROR | wrapper | 2008/02/08 01:40:42 | JVM exited unexpectedly. > > DEBUG | wrapper | 2008/02/08 01:40:42 | Waiting 5 seconds before > > launching another JVM. > > DEBUG | wrapper | 2008/02/08 01:40:46 | Classpath element, > > wrapper.java.classpath.10, does not exist: ../classes STATUS | > > wrapper | 2008/02/08 01:40:46 | Launching a JVM... > > NONE | wrapper | 2008/02/08 01:40:46 | command: > > "D:\IBM\WBIServer\jre\bin\java.exe" > > -Dsequencer.context=AU04QWS130DCA32 > > -Dsequencer.logs=d:\wppaup\runtime\var\sequencer\logs > > -Drepository.directory=D:\IBM\Sequencer -Djava.library.path="./lib" > > -classpath > > > "./lib/wrapper.jar;./lib/commons-collections-3.1.jar;./lib/commons-lang- 2.1.jar;./lib/commons-logging-1.0.4.jar;./lib/commons-net-1.4.1.jar;./li b/jakarta-oro.jar;./lib/log4j-1.2.7.jar;./lib/spring.jar;./lib/velocity- 1.4.jar;../classes;./lib/sequencer.jar" > > > -Dwrapper.key="2ZXzPWYAZ6Ry7obW" -Dwrapper.port=32002 > > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > > -Dwrapper.debug="TRUE" -Dwrapper.pid=2508 -Dwrapper.version="3.2.3" > > -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > > -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=9 > > org.tanukisoftware.wrapper.WrapperSimpleApp SequencerTool LOOP DEBUG > > | wrapper | 2008/02/08 01:40:46 | JVM started (PID=9500) > > > ---------------------------------------------------------------------- > --- This SF.net email is sponsored by: Microsoft Defy all challenges. > Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > ---------------------------------------------------------------------- > -- > > ---------------------------------------------------------------------- > --- This SF.net email is sponsored by: Microsoft Defy all challenges. > Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ---------------------------------------------------------------------- > -- > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user ------------------------------ Message: 3 Date: Wed, 20 Feb 2008 12:21:47 +0530 From: Ramakrishna Bv Sanku <ram...@in...> Subject: Re: [Wrapper-user] Issue with wrapper To: Leif Mortenson <le...@ta...> Cc: wra...@li... Message-ID: <OF5...@in...> Content-Type: text/plain; charset="us-ascii" Hi Leif Mortenson, Thank you i will set the property and check what is happening. Best Regards, Ram IBM Global Services India Pvt. Ltd. Mindspace, Survey No 64, APIIC Software Layout, Hi-tech City, Hyderabad -500 081 Phone: +91-40-66956756 INDIA Leif Mortenson <le...@ta...> 20/02/2008 11:53 To wra...@li... cc Ramakrishna Bv Sanku/India/IBM@IBMIN Subject Re: [Wrapper-user] Issue with wrapper Ram, I am a bit of a loss as to what is happening here assuming that you sent me the full logs. DEBUG | wrapperp | 2008/02/08 01:39:48 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:49 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:49 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:53 | send a packet PING : ping DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053) DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet not sent SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE The Wrapper should be attempting to send a PING packet once every 5 seconds as happens at 01:39:48 and 01:39:53. But then there is nothing. The JVM does say that it received the ping and there are no more attempts to send by the Wrapper. The next bessage is 49 seconds later at 01:40:42 when the Service Manager sends an interrogate control code. Both of your logs show the same thing. The wrapper sends a ping which is never acknowledged by the Java side of the Wrapper then about 50 seconds later an interrogate control code shows up which fails to be sent to the JVM. In addition to the wrapper.debug=TRUE property, can you also try setting wrapper.state_output=TRUE This will produce a LOT of output, but it might also shed more light on what is happening to you. Cheers, Leif Ramakrishna Bv Sanku wrote: > Hi Leif Mortenson, > > Thank you for quick response. Please check my answers in Blue for the > questions. > > Please find the attachment for the log. > > > I have checked the logs on other days as well , this issue is occuring > but for the recovery time is less, please check the log below: > > INFO | jvm 9 | 2008/02/10 01:28:46 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/10 01:28:46 | read a packet PING : ok > DEBUG | wrapper | 2008/02/10 01:28:46 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/10 01:28:50 | send a packet PING : ping > INFO | jvm 9 | 2008/02/10 01:28:50 | Received a packet PING : ping > INFO | jvm 9 | 2008/02/10 01:28:50 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/10 01:28:50 | read a packet PING : ok > DEBUG | wrapper | 2008/02/10 01:28:50 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/10 01:28:54 | send a packet PING : ping > DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/10 01:29:25 | send a packet > SERVICE_CONTROL_CODE : 4 > DEBUG | wrapperp | 2008/02/10 01:29:25 | socket send failed. (10053) > DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 9 | 2008/02/10 01:29:25 | Read Timed out. (Last Ping > was 30300 milliseconds ago) > INFO | jvm 9 | 2008/02/10 01:29:25 | Wrapper Manager: The Wrapper > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > resynch. > INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet RESTART : restart > INFO | jvm 9 | 2008/02/10 01:29:25 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 9 | 2008/02/10 01:29:25 | calling listener.stop() > INFO | jvm 9 | 2008/02/10 01:29:25 | Waiting for > WrapperListener.stop runner thread to complete. > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner > thread started. > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperSimpleApp: stop(1) > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner > thread stopped. > INFO | jvm 9 | 2008/02/10 01:29:25 | returned from > listener.stop() -> 1 > INFO | jvm 9 | 2008/02/10 01:29:25 | shutdownJVM(1) > Thread:Wrapper-Connection > INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet STOPPED : 1 > INFO | jvm 9 | 2008/02/10 01:29:25 | Closing socket. > INFO | jvm 9 | 2008/02/10 01:29:25 | calling System.exit(1) > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,188|INFO|SequencerTool|shutting down > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,266|INFO|SequencerTool|ok. > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,266|INFO|SequencerTool|stopped. > DEBUG | wrapperp | 2008/02/10 01:29:25 | server listening on port 32002. > INFO | wrapper | 2008/02/10 01:29:25 | Wrapper Process has not > received any CPU time for 30 seconds. Extending timeouts. > DEBUG | wrapper | 2008/02/10 01:29:25 | JVM process exited with a > code of 1, setting the wrapper exit code to 1. > ERROR | wrapper | 2008/02/10 01:29:25 | JVM exited unexpectedly. > DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/10 01:29:25 | socket not open, so packet > not sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE > DEBUG | wrapper | 2008/02/10 01:29:25 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2008/02/10 01:29:29 | Classpath element, > wrapper.java.classpath.10, does not exist: ../classes > STATUS | wrapper | 2008/02/10 01:29:29 | Launching a JVM... > ________________________________________________________________________ _________________________ > > INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet > SERVICE_CONTROL_CODE : 4 > INFO | jvm 7 | 2008/02/06 02:31:49 | ServiceControlCode from > Wrapper with code 4 > DEBUG | wrapperp | 2008/02/06 02:31:49 | send a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:49 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/06 02:31:50 | read a packet PING : ok > DEBUG | wrapper | 2008/02/06 02:31:50 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/06 02:31:54 | send a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:54 | Received a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:54 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/06 02:31:54 | read a packet PING : ok > DEBUG | wrapper | 2008/02/06 02:31:54 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/06 02:31:58 | send a packet PING : ping > DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/06 02:32:50 | send a packet > SERVICE_CONTROL_CODE : 4 > DEBUG | wrapperp | 2008/02/06 02:32:50 | socket send failed. (10053) > DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE > DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/06 02:32:50 | socket not open, so packet > not sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 7 | 2008/02/06 02:32:50 | Read Timed out. (Last Ping > was 30400 milliseconds ago) > INFO | jvm 7 | 2008/02/06 02:32:50 | Wrapper Manager: The Wrapper > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > resynch. > INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet RESTART : restart > INFO | jvm 7 | 2008/02/06 02:32:50 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 7 | 2008/02/06 02:32:50 | calling listener.stop() > INFO | jvm 7 | 2008/02/06 02:32:50 | Waiting for > WrapperListener.stop runner thread to complete. > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner > thread started. > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperSimpleApp: stop(1) > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner > thread stopped. > INFO | jvm 7 | 2008/02/06 02:32:50 | returned from > listener.stop() -> 1 > INFO | jvm 7 | 2008/02/06 02:32:50 | shutdownJVM(1) > Thread:Wrapper-Connection > INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet STOPPED : 1 > INFO | jvm 7 | 2008/02/06 02:32:50 | Closing socket. > INFO | jvm 7 | 2008/02/06 02:32:50 | calling System.exit(1) > INFO | jvm 7 | 2008/02/06 02:32:50 | 2008-02-06 > 02:32:26,750|INFO|SequencerTool|shutting down > DEBUG | wrapperp | 2008/02/06 02:32:50 | server listening on port 32002. > INFO | wrapper | 2008/02/06 02:32:50 | Wrapper Process has not > received any CPU time for 51 seconds. Extending timeouts. > DEBUG | wrapper | 2008/02/06 02:32:50 | JVM process exited with a > code of 1, setting the wrapper exit code to 1. > ERROR | wrapper | 2008/02/06 02:32:50 | JVM exited unexpectedly. > DEBUG | wrapper | 2008/02/06 02:32:50 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2008/02/06 02:32:54 | Classpath element, > wrapper.java.classpath.10, does not exist: ../classes > STATUS | wrapper | 2008/02/06 02:32:54 | Launching a JVM... > > Best Regards, > Ram > IBM Global Services India Pvt. Ltd. > Mindspace, Survey No 64, APIIC Software Layout, > Hi-tech City, Hyderabad -500 081 > INDIA > Phone: +91-40-66956756 > > > *Leif Mortenson <le...@ta...>* > Sent by: wra...@li... > > 02/08/2008 01:17 PM > Please respond to > wra...@li... > > > > To > wra...@li... > cc > > Subject > Re: [Wrapper-user] Issue with wrapper > > > > > > > > > > Ramakrishna, > According to the log, the backend socket between the Wrapper and > Java process was somehow closed. The Wrapper is failing saying > that it can no longer communicate with the JVM. It keeps going > though because the JVM process is still running. > > The JVM then gives up after around 30 seconds because it has not > received any communications from the Wrapper for that long. This > is a safety feature to shut the JVM process down just in case the > Wrapper process should ever crash. > > Once the Wrapper detects that the JVM is shutdown, it is correctly > restarting the JVM. > > > The question is why is the backend socket being closed? This is not > a problem I have ever seen or heard of in the past. Is anything else > in the log file earlier than what you sent? > > How easy is this to reproduce? > *A: We cannot reproduce.* > > Does it always happen at the same time? > *A: No,it does not happen at the sametime.* > > Is it possible that some other application on your system is closing > the socket? > *A:Can't say whether someother application on the system might be > trying to close the socket.Another two applications are running on the > same machine with wrapper having same configuration.* > > Is your system under load at the time of this reset? > *A: Yes, it was under load.* > > Does your Java application respond during the 30 seconds between > the socket being closed and the JVM shutting itself down? > *A: Can't answer* > > Cheers, > Leif > > Ramakrishna Bv Sanku wrote: > > > > Hi All, > > > > I came across a issue with wrapper, the Wrapper is getting degraded > > for sometime and getting into normal state after some time. Please > > check the wrapper log below. > > > > Can anyone help me and provide a solution, how can this be rectified. > > > > *Information from the wrapper log* > > WrapperManager class initialized by thread: main Using classloader: > > sun.misc.Launcher$AppClassLoader@27e3570f > > ............... > > Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org > > ............... > > > > Extract from wrapper log > > > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet > > SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053) > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet > > not sent SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > INFO | jvm 8 | 2008/02/08 01:40:42 | Read Timed out. (Last Ping > > was 30600 milliseconds ago) > > INFO | jvm 8 | 2008/02/08 01:40:42 | Wrapper Manager: The Wrapper > > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > > resynch. > > INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet RESTART : > restart > > INFO | jvm 8 | 2008/02/08 01:40:42 | Thread, Wrapper-Connection, > > handling the shutdown process. > > INFO | jvm 8 | 2008/02/08 01:40:42 | calling listener.stop() > > INFO | jvm 8 | 2008/02/08 01:40:42 | Waiting for > > WrapperListener.stop runner thread to complete. > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner > > thread started. > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperSimpleApp: stop(1) > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner > > thread stopped. > > INFO | jvm 8 | 2008/02/08 01:40:42 | returned from > > listener.stop() -> 1 > > INFO | jvm 8 | 2008/02/08 01:40:42 | shutdownJVM(1) > > Thread:Wrapper-Connection > > INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet STOPPED : 1 > > INFO | jvm 8 | 2008/02/08 01:40:42 | Closing socket. > > INFO | jvm 8 | 2008/02/08 01:40:42 | calling System.exit(1) > > INFO | jvm 8 | 2008/02/08 01:40:42 | 2008-02-08 > > 01:40:22,031|INFO|SequencerTool|shutting down > > DEBUG | wrapperp | 2008/02/08 01:40:42 | server listening on port > 32002. > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet > > not sent SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > INFO | wrapper | 2008/02/08 01:40:42 | Wrapper Process has not > > received any CPU time for 48 seconds. Extending timeouts. > > DEBUG | wrapper | 2008/02/08 01:40:42 | JVM process exited with a > > code of 1, setting the wrapper exit code to 1. > > ERROR | wrapper | 2008/02/08 01:40:42 | JVM exited unexpectedly. > > DEBUG | wrapper | 2008/02/08 01:40:42 | Waiting 5 seconds before > > launching another JVM. > > DEBUG | wrapper | 2008/02/08 01:40:46 | Classpath element, > > wrapper.java.classpath.10, does not exist: ../classes > > STATUS | wrapper | 2008/02/08 01:40:46 | Launching a JVM... > > NONE | wrapper | 2008/02/08 01:40:46 | command: > > "D:\IBM\WBIServer\jre\bin\java.exe" > > -Dsequencer.context=AU04QWS130DCA32 > > -Dsequencer.logs=d:\wppaup\runtime\var\sequencer\logs > > -Drepository.directory=D:\IBM\Sequencer -Djava.library.path="./lib" > > -classpath > > > "./lib/wrapper.jar;./lib/commons-collections-3.1.jar;./lib/commons-lang- 2.1.jar;./lib/commons-logging-1.0.4.jar;./lib/commons-net-1.4.1.jar;./li b/jakarta-oro.jar;./lib/log4j-1.2.7.jar;./lib/spring.jar;./lib/velocity- 1.4.jar;../classes;./lib/sequencer.jar" > > > -Dwrapper.key="2ZXzPWYAZ6Ry7obW" -Dwrapper.port=32002 > > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > > -Dwrapper.debug="TRUE" -Dwrapper.pid=2508 -Dwrapper.version="3.2.3" > > -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > > -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=9 > > org.tanukisoftware.wrapper.WrapperSimpleApp SequencerTool LOOP > > DEBUG | wrapper | 2008/02/08 01:40:46 | JVM started (PID=9500) > > > ------------------------------------------------------------------------ - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user End of Wrapper-user Digest, Vol 21, Issue 9 ******************************************* |
|
From: Eugen H. W. Yu <Eug...@rw...> - 2008-02-21 10:58:08
|
Hello, can I contribute to the project with a binary package for the Windows 2003 Server x64 Edition platform? (Service pack2, 4 prozessor Intel Xeon CPU 2.66Ghz I have cross-compiled the 64bit exe and dll on a widows machine. And it works fine on the 64bit server in combination with a 64bit java vm. Greetings - Eugen Yu |
|
From: Ramakrishna Bv S. <ram...@in...> - 2008-02-20 06:52:18
|
Hi Leif Mortenson, Thank you i will set the property and check what is happening. Best Regards, Ram IBM Global Services India Pvt. Ltd. Mindspace, Survey No 64, APIIC Software Layout, Hi-tech City, Hyderabad -500 081 Phone: +91-40-66956756 INDIA Leif Mortenson <le...@ta...> 20/02/2008 11:53 To wra...@li... cc Ramakrishna Bv Sanku/India/IBM@IBMIN Subject Re: [Wrapper-user] Issue with wrapper Ram, I am a bit of a loss as to what is happening here assuming that you sent me the full logs. DEBUG | wrapperp | 2008/02/08 01:39:48 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:49 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:49 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:53 | send a packet PING : ping DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053) DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet not sent SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE The Wrapper should be attempting to send a PING packet once every 5 seconds as happens at 01:39:48 and 01:39:53. But then there is nothing. The JVM does say that it received the ping and there are no more attempts to send by the Wrapper. The next bessage is 49 seconds later at 01:40:42 when the Service Manager sends an interrogate control code. Both of your logs show the same thing. The wrapper sends a ping which is never acknowledged by the Java side of the Wrapper then about 50 seconds later an interrogate control code shows up which fails to be sent to the JVM. In addition to the wrapper.debug=TRUE property, can you also try setting wrapper.state_output=TRUE This will produce a LOT of output, but it might also shed more light on what is happening to you. Cheers, Leif Ramakrishna Bv Sanku wrote: > Hi Leif Mortenson, > > Thank you for quick response. Please check my answers in Blue for the > questions. > > Please find the attachment for the log. > > > I have checked the logs on other days as well , this issue is occuring > but for the recovery time is less, please check the log below: > > INFO | jvm 9 | 2008/02/10 01:28:46 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/10 01:28:46 | read a packet PING : ok > DEBUG | wrapper | 2008/02/10 01:28:46 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/10 01:28:50 | send a packet PING : ping > INFO | jvm 9 | 2008/02/10 01:28:50 | Received a packet PING : ping > INFO | jvm 9 | 2008/02/10 01:28:50 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/10 01:28:50 | read a packet PING : ok > DEBUG | wrapper | 2008/02/10 01:28:50 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/10 01:28:54 | send a packet PING : ping > DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/10 01:29:25 | send a packet > SERVICE_CONTROL_CODE : 4 > DEBUG | wrapperp | 2008/02/10 01:29:25 | socket send failed. (10053) > DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 9 | 2008/02/10 01:29:25 | Read Timed out. (Last Ping > was 30300 milliseconds ago) > INFO | jvm 9 | 2008/02/10 01:29:25 | Wrapper Manager: The Wrapper > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > resynch. > INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet RESTART : restart > INFO | jvm 9 | 2008/02/10 01:29:25 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 9 | 2008/02/10 01:29:25 | calling listener.stop() > INFO | jvm 9 | 2008/02/10 01:29:25 | Waiting for > WrapperListener.stop runner thread to complete. > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner > thread started. > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperSimpleApp: stop(1) > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner > thread stopped. > INFO | jvm 9 | 2008/02/10 01:29:25 | returned from > listener.stop() -> 1 > INFO | jvm 9 | 2008/02/10 01:29:25 | shutdownJVM(1) > Thread:Wrapper-Connection > INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet STOPPED : 1 > INFO | jvm 9 | 2008/02/10 01:29:25 | Closing socket. > INFO | jvm 9 | 2008/02/10 01:29:25 | calling System.exit(1) > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,188|INFO|SequencerTool|shutting down > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,266|INFO|SequencerTool|ok. > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,266|INFO|SequencerTool|stopped. > DEBUG | wrapperp | 2008/02/10 01:29:25 | server listening on port 32002. > INFO | wrapper | 2008/02/10 01:29:25 | Wrapper Process has not > received any CPU time for 30 seconds. Extending timeouts. > DEBUG | wrapper | 2008/02/10 01:29:25 | JVM process exited with a > code of 1, setting the wrapper exit code to 1. > ERROR | wrapper | 2008/02/10 01:29:25 | JVM exited unexpectedly. > DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/10 01:29:25 | socket not open, so packet > not sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE > DEBUG | wrapper | 2008/02/10 01:29:25 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2008/02/10 01:29:29 | Classpath element, > wrapper.java.classpath.10, does not exist: ../classes > STATUS | wrapper | 2008/02/10 01:29:29 | Launching a JVM... > _________________________________________________________________________________________________ > > INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet > SERVICE_CONTROL_CODE : 4 > INFO | jvm 7 | 2008/02/06 02:31:49 | ServiceControlCode from > Wrapper with code 4 > DEBUG | wrapperp | 2008/02/06 02:31:49 | send a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:49 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/06 02:31:50 | read a packet PING : ok > DEBUG | wrapper | 2008/02/06 02:31:50 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/06 02:31:54 | send a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:54 | Received a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:54 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/06 02:31:54 | read a packet PING : ok > DEBUG | wrapper | 2008/02/06 02:31:54 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/06 02:31:58 | send a packet PING : ping > DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/06 02:32:50 | send a packet > SERVICE_CONTROL_CODE : 4 > DEBUG | wrapperp | 2008/02/06 02:32:50 | socket send failed. (10053) > DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE > DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/06 02:32:50 | socket not open, so packet > not sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 7 | 2008/02/06 02:32:50 | Read Timed out. (Last Ping > was 30400 milliseconds ago) > INFO | jvm 7 | 2008/02/06 02:32:50 | Wrapper Manager: The Wrapper > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > resynch. > INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet RESTART : restart > INFO | jvm 7 | 2008/02/06 02:32:50 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 7 | 2008/02/06 02:32:50 | calling listener.stop() > INFO | jvm 7 | 2008/02/06 02:32:50 | Waiting for > WrapperListener.stop runner thread to complete. > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner > thread started. > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperSimpleApp: stop(1) > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner > thread stopped. > INFO | jvm 7 | 2008/02/06 02:32:50 | returned from > listener.stop() -> 1 > INFO | jvm 7 | 2008/02/06 02:32:50 | shutdownJVM(1) > Thread:Wrapper-Connection > INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet STOPPED : 1 > INFO | jvm 7 | 2008/02/06 02:32:50 | Closing socket. > INFO | jvm 7 | 2008/02/06 02:32:50 | calling System.exit(1) > INFO | jvm 7 | 2008/02/06 02:32:50 | 2008-02-06 > 02:32:26,750|INFO|SequencerTool|shutting down > DEBUG | wrapperp | 2008/02/06 02:32:50 | server listening on port 32002. > INFO | wrapper | 2008/02/06 02:32:50 | Wrapper Process has not > received any CPU time for 51 seconds. Extending timeouts. > DEBUG | wrapper | 2008/02/06 02:32:50 | JVM process exited with a > code of 1, setting the wrapper exit code to 1. > ERROR | wrapper | 2008/02/06 02:32:50 | JVM exited unexpectedly. > DEBUG | wrapper | 2008/02/06 02:32:50 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2008/02/06 02:32:54 | Classpath element, > wrapper.java.classpath.10, does not exist: ../classes > STATUS | wrapper | 2008/02/06 02:32:54 | Launching a JVM... > > Best Regards, > Ram > IBM Global Services India Pvt. Ltd. > Mindspace, Survey No 64, APIIC Software Layout, > Hi-tech City, Hyderabad -500 081 > INDIA > Phone: +91-40-66956756 > > > *Leif Mortenson <le...@ta...>* > Sent by: wra...@li... > > 02/08/2008 01:17 PM > Please respond to > wra...@li... > > > > To > wra...@li... > cc > > Subject > Re: [Wrapper-user] Issue with wrapper > > > > > > > > > > Ramakrishna, > According to the log, the backend socket between the Wrapper and > Java process was somehow closed. The Wrapper is failing saying > that it can no longer communicate with the JVM. It keeps going > though because the JVM process is still running. > > The JVM then gives up after around 30 seconds because it has not > received any communications from the Wrapper for that long. This > is a safety feature to shut the JVM process down just in case the > Wrapper process should ever crash. > > Once the Wrapper detects that the JVM is shutdown, it is correctly > restarting the JVM. > > > The question is why is the backend socket being closed? This is not > a problem I have ever seen or heard of in the past. Is anything else > in the log file earlier than what you sent? > > How easy is this to reproduce? > *A: We cannot reproduce.* > > Does it always happen at the same time? > *A: No,it does not happen at the sametime.* > > Is it possible that some other application on your system is closing > the socket? > *A:Can't say whether someother application on the system might be > trying to close the socket.Another two applications are running on the > same machine with wrapper having same configuration.* > > Is your system under load at the time of this reset? > *A: Yes, it was under load.* > > Does your Java application respond during the 30 seconds between > the socket being closed and the JVM shutting itself down? > *A: Can't answer* > > Cheers, > Leif > > Ramakrishna Bv Sanku wrote: > > > > Hi All, > > > > I came across a issue with wrapper, the Wrapper is getting degraded > > for sometime and getting into normal state after some time. Please > > check the wrapper log below. > > > > Can anyone help me and provide a solution, how can this be rectified. > > > > *Information from the wrapper log* > > WrapperManager class initialized by thread: main Using classloader: > > sun.misc.Launcher$AppClassLoader@27e3570f > > ............... > > Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org > > ............... > > > > Extract from wrapper log > > > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet > > SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053) > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet > > not sent SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > INFO | jvm 8 | 2008/02/08 01:40:42 | Read Timed out. (Last Ping > > was 30600 milliseconds ago) > > INFO | jvm 8 | 2008/02/08 01:40:42 | Wrapper Manager: The Wrapper > > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > > resynch. > > INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet RESTART : > restart > > INFO | jvm 8 | 2008/02/08 01:40:42 | Thread, Wrapper-Connection, > > handling the shutdown process. > > INFO | jvm 8 | 2008/02/08 01:40:42 | calling listener.stop() > > INFO | jvm 8 | 2008/02/08 01:40:42 | Waiting for > > WrapperListener.stop runner thread to complete. > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner > > thread started. > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperSimpleApp: stop(1) > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner > > thread stopped. > > INFO | jvm 8 | 2008/02/08 01:40:42 | returned from > > listener.stop() -> 1 > > INFO | jvm 8 | 2008/02/08 01:40:42 | shutdownJVM(1) > > Thread:Wrapper-Connection > > INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet STOPPED : 1 > > INFO | jvm 8 | 2008/02/08 01:40:42 | Closing socket. > > INFO | jvm 8 | 2008/02/08 01:40:42 | calling System.exit(1) > > INFO | jvm 8 | 2008/02/08 01:40:42 | 2008-02-08 > > 01:40:22,031|INFO|SequencerTool|shutting down > > DEBUG | wrapperp | 2008/02/08 01:40:42 | server listening on port > 32002. > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet > > not sent SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > INFO | wrapper | 2008/02/08 01:40:42 | Wrapper Process has not > > received any CPU time for 48 seconds. Extending timeouts. > > DEBUG | wrapper | 2008/02/08 01:40:42 | JVM process exited with a > > code of 1, setting the wrapper exit code to 1. > > ERROR | wrapper | 2008/02/08 01:40:42 | JVM exited unexpectedly. > > DEBUG | wrapper | 2008/02/08 01:40:42 | Waiting 5 seconds before > > launching another JVM. > > DEBUG | wrapper | 2008/02/08 01:40:46 | Classpath element, > > wrapper.java.classpath.10, does not exist: ../classes > > STATUS | wrapper | 2008/02/08 01:40:46 | Launching a JVM... > > NONE | wrapper | 2008/02/08 01:40:46 | command: > > "D:\IBM\WBIServer\jre\bin\java.exe" > > -Dsequencer.context=AU04QWS130DCA32 > > -Dsequencer.logs=d:\wppaup\runtime\var\sequencer\logs > > -Drepository.directory=D:\IBM\Sequencer -Djava.library.path="./lib" > > -classpath > > > "./lib/wrapper.jar;./lib/commons-collections-3.1.jar;./lib/commons-lang-2.1.jar;./lib/commons-logging-1.0.4.jar;./lib/commons-net-1.4.1.jar;./lib/jakarta-oro.jar;./lib/log4j-1.2.7.jar;./lib/spring.jar;./lib/velocity-1.4.jar;../classes;./lib/sequencer.jar" > > > -Dwrapper.key="2ZXzPWYAZ6Ry7obW" -Dwrapper.port=32002 > > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > > -Dwrapper.debug="TRUE" -Dwrapper.pid=2508 -Dwrapper.version="3.2.3" > > -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > > -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=9 > > org.tanukisoftware.wrapper.WrapperSimpleApp SequencerTool LOOP > > DEBUG | wrapper | 2008/02/08 01:40:46 | JVM started (PID=9500) > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <le...@ta...> - 2008-02-20 06:23:46
|
Ram, I am a bit of a loss as to what is happening here assuming that you sent me the full logs. DEBUG | wrapperp | 2008/02/08 01:39:48 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:49 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:49 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:53 | send a packet PING : ping DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053) DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet not sent SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE The Wrapper should be attempting to send a PING packet once every 5 seconds as happens at 01:39:48 and 01:39:53. But then there is nothing. The JVM does say that it received the ping and there are no more attempts to send by the Wrapper. The next bessage is 49 seconds later at 01:40:42 when the Service Manager sends an interrogate control code. Both of your logs show the same thing. The wrapper sends a ping which is never acknowledged by the Java side of the Wrapper then about 50 seconds later an interrogate control code shows up which fails to be sent to the JVM. In addition to the wrapper.debug=TRUE property, can you also try setting wrapper.state_output=TRUE This will produce a LOT of output, but it might also shed more light on what is happening to you. Cheers, Leif Ramakrishna Bv Sanku wrote: > Hi Leif Mortenson, > > Thank you for quick response. Please check my answers in Blue for the > questions. > > Please find the attachment for the log. > > > I have checked the logs on other days as well , this issue is occuring > but for the recovery time is less, please check the log below: > > INFO | jvm 9 | 2008/02/10 01:28:46 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/10 01:28:46 | read a packet PING : ok > DEBUG | wrapper | 2008/02/10 01:28:46 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/10 01:28:50 | send a packet PING : ping > INFO | jvm 9 | 2008/02/10 01:28:50 | Received a packet PING : ping > INFO | jvm 9 | 2008/02/10 01:28:50 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/10 01:28:50 | read a packet PING : ok > DEBUG | wrapper | 2008/02/10 01:28:50 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/10 01:28:54 | send a packet PING : ping > DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/10 01:29:25 | send a packet > SERVICE_CONTROL_CODE : 4 > DEBUG | wrapperp | 2008/02/10 01:29:25 | socket send failed. (10053) > DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 9 | 2008/02/10 01:29:25 | Read Timed out. (Last Ping > was 30300 milliseconds ago) > INFO | jvm 9 | 2008/02/10 01:29:25 | Wrapper Manager: The Wrapper > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > resynch. > INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet RESTART : restart > INFO | jvm 9 | 2008/02/10 01:29:25 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 9 | 2008/02/10 01:29:25 | calling listener.stop() > INFO | jvm 9 | 2008/02/10 01:29:25 | Waiting for > WrapperListener.stop runner thread to complete. > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner > thread started. > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperSimpleApp: stop(1) > INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner > thread stopped. > INFO | jvm 9 | 2008/02/10 01:29:25 | returned from > listener.stop() -> 1 > INFO | jvm 9 | 2008/02/10 01:29:25 | shutdownJVM(1) > Thread:Wrapper-Connection > INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet STOPPED : 1 > INFO | jvm 9 | 2008/02/10 01:29:25 | Closing socket. > INFO | jvm 9 | 2008/02/10 01:29:25 | calling System.exit(1) > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,188|INFO|SequencerTool|shutting down > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,266|INFO|SequencerTool|ok. > INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 > 01:29:23,266|INFO|SequencerTool|stopped. > DEBUG | wrapperp | 2008/02/10 01:29:25 | server listening on port 32002. > INFO | wrapper | 2008/02/10 01:29:25 | Wrapper Process has not > received any CPU time for 30 seconds. Extending timeouts. > DEBUG | wrapper | 2008/02/10 01:29:25 | JVM process exited with a > code of 1, setting the wrapper exit code to 1. > ERROR | wrapper | 2008/02/10 01:29:25 | JVM exited unexpectedly. > DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/10 01:29:25 | socket not open, so packet > not sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE > DEBUG | wrapper | 2008/02/10 01:29:25 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2008/02/10 01:29:29 | Classpath element, > wrapper.java.classpath.10, does not exist: ../classes > STATUS | wrapper | 2008/02/10 01:29:29 | Launching a JVM... > _________________________________________________________________________________________________ > > INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet > SERVICE_CONTROL_CODE : 4 > INFO | jvm 7 | 2008/02/06 02:31:49 | ServiceControlCode from > Wrapper with code 4 > DEBUG | wrapperp | 2008/02/06 02:31:49 | send a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:49 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/06 02:31:50 | read a packet PING : ok > DEBUG | wrapper | 2008/02/06 02:31:50 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/06 02:31:54 | send a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:54 | Received a packet PING : ping > INFO | jvm 7 | 2008/02/06 02:31:54 | Send a packet PING : ok > DEBUG | wrapperp | 2008/02/06 02:31:54 | read a packet PING : ok > DEBUG | wrapper | 2008/02/06 02:31:54 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/06 02:31:58 | send a packet PING : ping > DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/06 02:32:50 | send a packet > SERVICE_CONTROL_CODE : 4 > DEBUG | wrapperp | 2008/02/06 02:32:50 | socket send failed. (10053) > DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE > DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4) > DEBUG | wrapperp | 2008/02/06 02:32:50 | socket not open, so packet > not sent SERVICE_CONTROL_CODE : 4 > DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE > INFO | jvm 7 | 2008/02/06 02:32:50 | Read Timed out. (Last Ping > was 30400 milliseconds ago) > INFO | jvm 7 | 2008/02/06 02:32:50 | Wrapper Manager: The Wrapper > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > resynch. > INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet RESTART : restart > INFO | jvm 7 | 2008/02/06 02:32:50 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 7 | 2008/02/06 02:32:50 | calling listener.stop() > INFO | jvm 7 | 2008/02/06 02:32:50 | Waiting for > WrapperListener.stop runner thread to complete. > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner > thread started. > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperSimpleApp: stop(1) > INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner > thread stopped. > INFO | jvm 7 | 2008/02/06 02:32:50 | returned from > listener.stop() -> 1 > INFO | jvm 7 | 2008/02/06 02:32:50 | shutdownJVM(1) > Thread:Wrapper-Connection > INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet STOPPED : 1 > INFO | jvm 7 | 2008/02/06 02:32:50 | Closing socket. > INFO | jvm 7 | 2008/02/06 02:32:50 | calling System.exit(1) > INFO | jvm 7 | 2008/02/06 02:32:50 | 2008-02-06 > 02:32:26,750|INFO|SequencerTool|shutting down > DEBUG | wrapperp | 2008/02/06 02:32:50 | server listening on port 32002. > INFO | wrapper | 2008/02/06 02:32:50 | Wrapper Process has not > received any CPU time for 51 seconds. Extending timeouts. > DEBUG | wrapper | 2008/02/06 02:32:50 | JVM process exited with a > code of 1, setting the wrapper exit code to 1. > ERROR | wrapper | 2008/02/06 02:32:50 | JVM exited unexpectedly. > DEBUG | wrapper | 2008/02/06 02:32:50 | Waiting 5 seconds before > launching another JVM. > DEBUG | wrapper | 2008/02/06 02:32:54 | Classpath element, > wrapper.java.classpath.10, does not exist: ../classes > STATUS | wrapper | 2008/02/06 02:32:54 | Launching a JVM... > > Best Regards, > Ram > IBM Global Services India Pvt. Ltd. > Mindspace, Survey No 64, APIIC Software Layout, > Hi-tech City, Hyderabad -500 081 > INDIA > Phone: +91-40-66956756 > > > *Leif Mortenson <le...@ta...>* > Sent by: wra...@li... > > 02/08/2008 01:17 PM > Please respond to > wra...@li... > > > > To > wra...@li... > cc > > Subject > Re: [Wrapper-user] Issue with wrapper > > > > > > > > > > Ramakrishna, > According to the log, the backend socket between the Wrapper and > Java process was somehow closed. The Wrapper is failing saying > that it can no longer communicate with the JVM. It keeps going > though because the JVM process is still running. > > The JVM then gives up after around 30 seconds because it has not > received any communications from the Wrapper for that long. This > is a safety feature to shut the JVM process down just in case the > Wrapper process should ever crash. > > Once the Wrapper detects that the JVM is shutdown, it is correctly > restarting the JVM. > > > The question is why is the backend socket being closed? This is not > a problem I have ever seen or heard of in the past. Is anything else > in the log file earlier than what you sent? > > How easy is this to reproduce? > *A: We cannot reproduce.* > > Does it always happen at the same time? > *A: No,it does not happen at the sametime.* > > Is it possible that some other application on your system is closing > the socket? > *A:Can't say whether someother application on the system might be > trying to close the socket.Another two applications are running on the > same machine with wrapper having same configuration.* > > Is your system under load at the time of this reset? > *A: Yes, it was under load.* > > Does your Java application respond during the 30 seconds between > the socket being closed and the JVM shutting itself down? > *A: Can't answer* > > Cheers, > Leif > > Ramakrishna Bv Sanku wrote: > > > > Hi All, > > > > I came across a issue with wrapper, the Wrapper is getting degraded > > for sometime and getting into normal state after some time. Please > > check the wrapper log below. > > > > Can anyone help me and provide a solution, how can this be rectified. > > > > *Information from the wrapper log* > > WrapperManager class initialized by thread: main Using classloader: > > sun.misc.Launcher$AppClassLoader@27e3570f > > ............... > > Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org > > ............... > > > > Extract from wrapper log > > > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet > > SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053) > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet > > not sent SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > INFO | jvm 8 | 2008/02/08 01:40:42 | Read Timed out. (Last Ping > > was 30600 milliseconds ago) > > INFO | jvm 8 | 2008/02/08 01:40:42 | Wrapper Manager: The Wrapper > > code did not ping the JVM for 30 seconds. Quit and let the Wrapper > > resynch. > > INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet RESTART : > restart > > INFO | jvm 8 | 2008/02/08 01:40:42 | Thread, Wrapper-Connection, > > handling the shutdown process. > > INFO | jvm 8 | 2008/02/08 01:40:42 | calling listener.stop() > > INFO | jvm 8 | 2008/02/08 01:40:42 | Waiting for > > WrapperListener.stop runner thread to complete. > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner > > thread started. > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperSimpleApp: stop(1) > > INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner > > thread stopped. > > INFO | jvm 8 | 2008/02/08 01:40:42 | returned from > > listener.stop() -> 1 > > INFO | jvm 8 | 2008/02/08 01:40:42 | shutdownJVM(1) > > Thread:Wrapper-Connection > > INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet STOPPED : 1 > > INFO | jvm 8 | 2008/02/08 01:40:42 | Closing socket. > > INFO | jvm 8 | 2008/02/08 01:40:42 | calling System.exit(1) > > INFO | jvm 8 | 2008/02/08 01:40:42 | 2008-02-08 > > 01:40:22,031|INFO|SequencerTool|shutting down > > DEBUG | wrapperp | 2008/02/08 01:40:42 | server listening on port > 32002. > > DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) > > DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet > > not sent SERVICE_CONTROL_CODE : 4 > > DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE > > INFO | wrapper | 2008/02/08 01:40:42 | Wrapper Process has not > > received any CPU time for 48 seconds. Extending timeouts. > > DEBUG | wrapper | 2008/02/08 01:40:42 | JVM process exited with a > > code of 1, setting the wrapper exit code to 1. > > ERROR | wrapper | 2008/02/08 01:40:42 | JVM exited unexpectedly. > > DEBUG | wrapper | 2008/02/08 01:40:42 | Waiting 5 seconds before > > launching another JVM. > > DEBUG | wrapper | 2008/02/08 01:40:46 | Classpath element, > > wrapper.java.classpath.10, does not exist: ../classes > > STATUS | wrapper | 2008/02/08 01:40:46 | Launching a JVM... > > NONE | wrapper | 2008/02/08 01:40:46 | command: > > "D:\IBM\WBIServer\jre\bin\java.exe" > > -Dsequencer.context=AU04QWS130DCA32 > > -Dsequencer.logs=d:\wppaup\runtime\var\sequencer\logs > > -Drepository.directory=D:\IBM\Sequencer -Djava.library.path="./lib" > > -classpath > > > "./lib/wrapper.jar;./lib/commons-collections-3.1.jar;./lib/commons-lang-2.1.jar;./lib/commons-logging-1.0.4.jar;./lib/commons-net-1.4.1.jar;./lib/jakarta-oro.jar;./lib/log4j-1.2.7.jar;./lib/spring.jar;./lib/velocity-1.4.jar;../classes;./lib/sequencer.jar" > > > -Dwrapper.key="2ZXzPWYAZ6Ry7obW" -Dwrapper.port=32002 > > -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 > > -Dwrapper.debug="TRUE" -Dwrapper.pid=2508 -Dwrapper.version="3.2.3" > > -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" > > -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=9 > > org.tanukisoftware.wrapper.WrapperSimpleApp SequencerTool LOOP > > DEBUG | wrapper | 2008/02/08 01:40:46 | JVM started (PID=9500) > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <le...@ta...> - 2008-02-20 05:20:38
|
Ben,
I have never seen or heard of any examples of the Wrapper or its
Java component consuming lots of CPU due to the Wrapper.
To confirm, it is the java process and not the wrapper process
that is using up all the CPU.
You might want to try doing some profiling of your JVM to narrow
down the cause. From you classpath, and
configManager.VPNManagement.RegistrarDaemon
class, it is likely that more is going on in your application than
the loop below.
I have seen cases where the java application is not being configured
as expected when running under the wrapper. An incorrect path
for example. Something like that could cause some thrashing of
an outer loop depending on how the error handling code
was written.
You can review the full command used to launch the JVM by adding
the following to your wrapper.conf
wrapper.java.command.loglevel=INFO
Cheers,
Leif
Ben Leibert wrote:
>
> I’m using version 3.2.3 of the wrapper on SuSe Linux 10.1 alongside
> version 1.5 of Java. The “top” command shows the wrapper to
> consistently monopolize the CPU, which I’d ~really~ appreciate help
> resolving. The code I’m testing with looks as follows:
>
> while(true)
>
> {
>
> System.out.println("This just ran");
>
> Thread.currentThread().sleep(3000);
>
> }
>
> Only when run via the wrapper does this dominate the processor.
> Neither changing the wrapper.ping.interval nor the priority (nice)
> properties has had any noticeable affect. My configuration files are
> included below. Thanks in advance for any help!
>
> Cheers,
>
> Ben
>
(snip)
|
|
From: Ben L. <Ben...@As...> - 2008-02-20 02:54:53
|
I'm using version 3.2.3 of the wrapper on SuSe Linux 10.1 alongside
version 1.5 of Java. The "top" command shows the wrapper to consistently
monopolize the CPU, which I'd ~really~ appreciate help resolving. The
code I'm testing with looks as follows:
while(true)
{
System.out.println("This just ran");
Thread.currentThread().sleep(3000);
}
Only when run via the wrapper does this dominate the processor. Neither
changing the wrapper.ping.interval nor the priority (nice) properties
has had any noticeable affect. My configuration files are included
below. Thanks in advance for any help!
Cheers,
Ben
File One:
#! /bin/sh
#
# Copyright (c) 1999, 2006 Tanuki Software Inc.
#
# Java Service Wrapper sh script. Suitable for starting and stopping
# wrapped Java applications on UNIX platforms.
#
#-----------------------------------------------------------------------
------
# These settings can be modified to fit the needs of your application
# NOTE: The APP_NAME may not contain spaces.
APP_NAME="Registrar"
APP_LONG_NAME="Asentria SMP Registrar"
# Wrapper
WRAPPER_CMD="./wrapper"
WRAPPER_CONF="./daemonSettings/registrar.conf"
# Priority at which to run the wrapper. See "man nice" for valid
priorities.
# nice is only used if a priority is specified.
PRIORITY=
# Location of the pid file.
PIDDIR="./daemonSettings"
# If uncommented, causes the Wrapper to be shutdown using an anchor
file.
# When launched with the 'start' command, it will also ignore all INT
and
# TERM signals.
#IGNORE_SIGNALS=true
# If specified, the Wrapper will be run as the specified user.
# IMPORTANT - Make sure that the user has the required privileges to
write
# the PID file and wrapper.log files. Failure to be able to write the
log
# file will cause the Wrapper to exit without any way to write out an
error
# message.
# NOTE - This will set the user which is used to run the Wrapper as well
as
# the JVM and is not useful in situations where a privileged resource
or
# port needs to be allocated prior to the user being changed.
#RUN_AS_USER=
# The following two lines are used by the chkconfig command. Change as
is
# appropriate for your application. They should remain commented.
# chkconfig: 2345 20 80
# description: @app.long.name@
# Do not modify anything beyond this point
#-----------------------------------------------------------------------
------
File Two
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=java
# Java Main class. This class must implement the WrapperListener
interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=.
wrapper.java.classpath.2=../lib/wrapper.jar
wrapper.java.classpath.3=../lib/commons-beanutils.jar
wrapper.java.classpath.4=../lib/commons-collections-3.1.jar
wrapper.java.classpath.5=../lib/commons-collections-3.2.jar
wrapper.java.classpath.6=../lib/commons-collections-testframework-3.2.ja
r
wrapper.java.classpath.7=../lib/commons-dbcp-1.2.1.jar:../lib/commons-di
gester-1.7.jar
wrapper.java.classpath.8=../lib/commons-fileupload-1.1.1.jar:../lib/comm
ons-io-1.2.jar
wrapper.java.classpath.9=../lib/commons-logging-1.1.jar:../lib/commons-l
ogging-adapters-1.1.jar
wrapper.java.classpath.10=../lib/commons-logging-api-1.1.jar:../lib/comm
ons-logging-api.jar
wrapper.java.classpath.11=../lib/commons-logging.jar:../lib/commons-mode
ler-1.1.jar
wrapper.java.classpath.12=../lib/commons-net-1.4.1.jar:../lib/commons-po
ol-1.2.jar
wrapper.java.classpath.13=../lib/commons-pool-1.3.jar:../lib/commons-val
idator-1.1.4.jar
wrapper.java.classpath.14=../lib/jakarta-oro-2.0.8.jar:../lib/jta-1_0_1B
-classes.jar
wrapper.java.classpath.15=../lib/log4j-1.2.11.jar:../lib/postgresql-8.1-
407.jdbc3.jar
wrapper.java.classpath.16=../lib/quartz-1.6.0.jar:../lib/quartz-all-1.6.
0.jar
wrapper.java.classpath.17=../lib/ws-commons-util-1.0.1.jar:../lib/xmlrpc
-1.0.1.jar
wrapper.java.classpath.18=../lib/xmlrpc-1.0.jar:../lib/xmlrpc-client-3.0
.jar
wrapper.java.classpath.19=../lib/xmlrpc-common-3.0.jar:../lib/xmlrpc-ser
ver-3.0.jar
wrapper.java.classpath.20=../lib/jakarta-httpcore-4.0-alpha2-2006-06-08.
jar
wrapper.java.classpath.21=../lib/xmlrpc-client-1.0.jar
wrapper.java.classpath.21=../lib
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib
# Java Additional Parameters
#wrapper.java.additional.1=
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3
# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=configManager.VPNManagement.RegistrarDaemon
wrapper.app.parameter.2=./daemonLogs/Registrar
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM
# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO
# Log file to use for wrapper output logging.
wrapper.logfile=./daemonLogs/RegistrarWrapper_YYYYMMDD.log
# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM
# Valid values are NONE, FATAL, ERROR, STATUS, INFO, and DEBUG
wrapper.logfile.loglevel=INFO
#Log all messages to a file named according to the date
(wrapper_YYYYMMDD.log)
#Retain five such files, deleting older ones.
wrapper.logfile.rollmode=DATE
wrapper.logfile.maxfiles=5
# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE
#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wra...@ap...@
#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
wra...@ap...@
# Display name of the service
wra...@ap...@
# Description of the service
wra...@ap...@
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
|
|
From: Ramakrishna Bv S. <ram...@in...> - 2008-02-18 03:16:08
|
INFO | jvm 8 | 2008/02/08 01:38:38 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:38:38 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:38:38 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:38:42 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:42 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:42 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:38:42 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:38:42 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:38:46 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:47 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:47 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:38:47 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:38:47 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:38:51 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:51 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:51 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:38:51 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:38:51 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:38:55 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:55 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:55 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:38:55 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:38:55 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:38:59 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:59 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:38:59 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:38:59 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:38:59 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:03 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:03 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:03 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:03 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:03 | Got ping response from JVM DEBUG | wrapper | 2008/02/08 01:39:05 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:39:05 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:39:05 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapper | 2008/02/08 01:39:05 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:39:05 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:39:05 | SERVICE_CONTROL_INTERROGATE INFO | jvm 8 | 2008/02/08 01:39:05 | Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 8 | 2008/02/08 01:39:05 | ServiceControlCode from Wrapper with code 4 INFO | jvm 8 | 2008/02/08 01:39:05 | Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 8 | 2008/02/08 01:39:05 | ServiceControlCode from Wrapper with code 4 DEBUG | wrapperp | 2008/02/08 01:39:07 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:07 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:07 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:07 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:07 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:11 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:11 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:11 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:11 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:11 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:15 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:15 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:15 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:15 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:15 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:20 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:20 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:20 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:20 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:20 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:24 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:24 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:24 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:24 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:24 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:28 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:28 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:28 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:28 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:28 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:32 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:32 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:32 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:32 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:32 | Got ping response from JVM DEBUG | wrapper | 2008/02/08 01:39:35 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:39:35 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:39:35 | SERVICE_CONTROL_INTERROGATE INFO | jvm 8 | 2008/02/08 01:39:35 | Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 8 | 2008/02/08 01:39:35 | ServiceControlCode from Wrapper with code 4 DEBUG | wrapper | 2008/02/08 01:39:35 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:39:35 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:39:35 | SERVICE_CONTROL_INTERROGATE INFO | jvm 8 | 2008/02/08 01:39:35 | Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 8 | 2008/02/08 01:39:35 | ServiceControlCode from Wrapper with code 4 DEBUG | wrapperp | 2008/02/08 01:39:36 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:36 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:36 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:36 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:36 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:40 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:40 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:40 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:40 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:40 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:44 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:44 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:44 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:44 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:44 | Got ping response from JVM DEBUG | wrapper | 2008/02/08 01:39:46 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:39:46 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:39:46 | SERVICE_CONTROL_INTERROGATE INFO | jvm 8 | 2008/02/08 01:39:46 | Received a packet SERVICE_CONTROL_CODE : 4 INFO | jvm 8 | 2008/02/08 01:39:46 | ServiceControlCode from Wrapper with code 4 DEBUG | wrapperp | 2008/02/08 01:39:48 | send a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Received a packet PING : ping INFO | jvm 8 | 2008/02/08 01:39:49 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:39:49 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:39:49 | Got ping response from JVM DEBUG | wrapperp | 2008/02/08 01:39:53 | send a packet PING : ping DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet SERVICE_CONTROL_CODE : 4 DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053) DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet not sent SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE INFO | jvm 8 | 2008/02/08 01:40:42 | Read Timed out. (Last Ping was 30600 milliseconds ago) INFO | jvm 8 | 2008/02/08 01:40:42 | Wrapper Manager: The Wrapper code did not ping the JVM for 30 seconds. Quit and let the Wrapper resynch. INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet RESTART : restart INFO | jvm 8 | 2008/02/08 01:40:42 | Thread, Wrapper-Connection, handling the shutdown process. INFO | jvm 8 | 2008/02/08 01:40:42 | calling listener.stop() INFO | jvm 8 | 2008/02/08 01:40:42 | Waiting for WrapperListener.stop runner thread to complete. INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner thread started. INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperSimpleApp: stop(1) INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner thread stopped. INFO | jvm 8 | 2008/02/08 01:40:42 | returned from listener.stop() -> 1 INFO | jvm 8 | 2008/02/08 01:40:42 | shutdownJVM(1) Thread:Wrapper-Connection INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet STOPPED : 1 INFO | jvm 8 | 2008/02/08 01:40:42 | Closing socket. INFO | jvm 8 | 2008/02/08 01:40:42 | calling System.exit(1) INFO | jvm 8 | 2008/02/08 01:40:42 | 2008-02-08 01:40:22,031|INFO|SequencerTool|shutting down DEBUG | wrapperp | 2008/02/08 01:40:42 | server listening on port 32002. DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4) DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet not sent SERVICE_CONTROL_CODE : 4 DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE INFO | wrapper | 2008/02/08 01:40:42 | Wrapper Process has not received any CPU time for 48 seconds. Extending timeouts. DEBUG | wrapper | 2008/02/08 01:40:42 | JVM process exited with a code of 1, setting the wrapper exit code to 1. ERROR | wrapper | 2008/02/08 01:40:42 | JVM exited unexpectedly. DEBUG | wrapper | 2008/02/08 01:40:42 | Waiting 5 seconds before launching another JVM. DEBUG | wrapper | 2008/02/08 01:40:46 | Classpath element, wrapper.java.classpath.10, does not exist: ../classes STATUS | wrapper | 2008/02/08 01:40:46 | Launching a JVM... NONE | wrapper | 2008/02/08 01:40:46 | command: "D:\IBM\WBIServer\jre\bin\java.exe" -Dsequencer.context=AU04QWS130DCA32 -Dsequencer.logs=d:\wppaup\runtime\var\sequencer\logs -Drepository.directory=D:\IBM\Sequencer -Djava.library.path="./lib" -classpath "./lib/wrapper.jar;./lib/commons-collections-3.1.jar;./lib/commons-lang-2.1.jar;./lib/commons-logging-1.0.4.jar;./lib/commons-net-1.4.1.jar;./lib/jakarta-oro.jar;./lib/log4j-1.2.7.jar;./lib/spring.jar;./lib/velocity-1.4.jar;../classes;./lib/sequencer.jar" -Dwrapper.key="2ZXzPWYAZ6Ry7obW" -Dwrapper.port=32002 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=2508 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=9 org.tanukisoftware.wrapper.WrapperSimpleApp SequencerTool LOOP DEBUG | wrapper | 2008/02/08 01:40:46 | JVM started (PID=9500) INFO | jvm 9 | 2008/02/08 01:40:49 | WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@27e3570f INFO | jvm 9 | 2008/02/08 01:40:49 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 9 | 2008/02/08 01:40:49 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 9 | 2008/02/08 01:40:49 | INFO | jvm 9 | 2008/02/08 01:40:49 | Wrapper Manager: JVM #9 INFO | jvm 9 | 2008/02/08 01:40:49 | Running a 32-bit JVM. INFO | jvm 9 | 2008/02/08 01:40:49 | Wrapper Manager: Registering shutdown hook INFO | jvm 9 | 2008/02/08 01:40:49 | Wrapper Manager: Using wrapper INFO | jvm 9 | 2008/02/08 01:40:49 | Load native library. One or more attempts may fail if platform specific libraries do not exist. INFO | jvm 9 | 2008/02/08 01:40:49 | Loading native library failed: wrapper-windows-x86-32.dll Cause: java.lang.UnsatisfiedLinkError: Can't find library wrapper-windows-x86-32 (wrapper-windows-x86-32.dll) in sun.boot.library.path or java.library.path INFO | jvm 9 | 2008/02/08 01:40:49 | sun.boot.library.path=D:\IBM\WBIServer\jre\bin INFO | jvm 9 | 2008/02/08 01:40:49 | java.library.path=./lib INFO | jvm 9 | 2008/02/08 01:40:49 | Loaded native library: wrapper.dll INFO | jvm 9 | 2008/02/08 01:40:49 | Calling native initialization method. INFO | jvm 9 | 2008/02/08 01:40:49 | Initializing WrapperManager native library. INFO | jvm 9 | 2008/02/08 01:40:49 | Java Executable: D:\IBM\WBIServer\jre\bin\java.exe INFO | jvm 9 | 2008/02/08 01:40:49 | Windows version: 5.2.3790 INFO | jvm 9 | 2008/02/08 01:40:49 | Java Version : J2RE 1.4.2 IBM Windows 32 build cn142-20040926 (JIT enabled: jitc) INFO | jvm 9 | 2008/02/08 01:40:49 | Java VM Vendor : IBM Corporation INFO | jvm 9 | 2008/02/08 01:40:49 | INFO | jvm 9 | 2008/02/08 01:40:49 | Startup runner thread started. INFO | jvm 9 | 2008/02/08 01:40:49 | Control event monitor thread started. INFO | jvm 9 | 2008/02/08 01:40:50 | WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@629570f, args["LOOP"]) called by thread: main INFO | jvm 9 | 2008/02/08 01:40:50 | Communications runner thread started. INFO | jvm 9 | 2008/02/08 01:40:50 | Open socket to wrapper...Wrapper-Connection INFO | jvm 9 | 2008/02/08 01:40:50 | Failed attempt to bind using local port 31000 INFO | jvm 9 | 2008/02/08 01:40:50 | Failed attempt to bind using local port 31001 INFO | jvm 9 | 2008/02/08 01:40:50 | Opened Socket from 31002 to 32002 INFO | jvm 9 | 2008/02/08 01:40:50 | Send a packet KEY : 2ZXzPWYAZ6Ry7obW INFO | jvm 9 | 2008/02/08 01:40:50 | handleSocket(Socket[addr=/127.0.0.1,port=32002,localport=31002]) DEBUG | wrapperp | 2008/02/08 01:40:50 | accepted a socket from 127.0.0.1 on port 31002 DEBUG | wrapperp | 2008/02/08 01:40:50 | read a packet KEY : 2ZXzPWYAZ6Ry7obW DEBUG | wrapper | 2008/02/08 01:40:50 | Got key from JVM: 2ZXzPWYAZ6Ry7obW DEBUG | wrapperp | 2008/02/08 01:40:50 | send a packet LOW_LOG_LEVEL : 0 DEBUG | wrapperp | 2008/02/08 01:40:50 | send a packet PING_TIMEOUT : 30 DEBUG | wrapperp | 2008/02/08 01:40:50 | send a packet PROPERTIES : (Property Values) DEBUG | wrapper | 2008/02/08 01:40:50 | Start Application. DEBUG | wrapperp | 2008/02/08 01:40:50 | send a packet START : start INFO | jvm 9 | 2008/02/08 01:40:50 | Received a packet LOW_LOG_LEVEL : 0 INFO | jvm 9 | 2008/02/08 01:40:50 | Wrapper Manager: LowLogLevel from Wrapper is 0 INFO | jvm 9 | 2008/02/08 01:40:50 | Received a packet PING_TIMEOUT : 30 INFO | jvm 9 | 2008/02/08 01:40:50 | PingTimeout from Wrapper is 30000 INFO | jvm 9 | 2008/02/08 01:40:50 | Received a packet PROPERTIES : (Property Values) INFO | jvm 9 | 2008/02/08 01:40:50 | Received a packet START : start INFO | jvm 9 | 2008/02/08 01:40:50 | calling WrapperListener.start() INFO | jvm 9 | 2008/02/08 01:40:50 | Waiting for WrapperListener.start runner thread to complete. INFO | jvm 9 | 2008/02/08 01:40:50 | WrapperListener.start runner thread started. INFO | jvm 9 | 2008/02/08 01:40:50 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete. INFO | jvm 9 | 2008/02/08 01:40:50 | WrapperSimpleApp: invoking main method INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,375|INFO|SequencerTool|starting... INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,484|INFO|SequencerTool|resource META-INF/sequencer.xml...found INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,516|INFO|SequencerTool|resource META-INF/AU04QWS130DCA32/sequencer.xml...not found INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,516|INFO|SequencerTool|resource AU04QWS130DCA32/sequencer.xml...not found INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,547|INFO|SequencerTool|resource local/sequencer.xml...found INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,547|INFO|SequencerTool|resource META-INF/sequencer.properties...found INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,547|INFO|SequencerTool|resource META-INF/AU04QWS130DCA32/sequencer.properties...found INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,547|INFO|SequencerTool|resource AU04QWS130DCA32/sequencer.properties...not found INFO | jvm 9 | 2008/02/08 01:40:50 | 2008-02-08 01:40:50,547|INFO|SequencerTool|resource local/sequencer.properties...found INFO | jvm 9 | 2008/02/08 01:40:51 | Send a packet START_PENDING : 5000 DEBUG | wrapperp | 2008/02/08 01:40:51 | read a packet START_PENDING : 5000 DEBUG | wrapper | 2008/02/08 01:40:51 | JVM signalled a start pending with waitHint of 5000 millis. INFO | jvm 9 | 2008/02/08 01:40:52 | Send a packet START_PENDING : 5000 INFO | jvm 9 | 2008/02/08 01:40:52 | WrapperSimpleApp: start(args) end. Main Completed=false, exitCode=null INFO | jvm 9 | 2008/02/08 01:40:52 | WrapperListener.start runner thread stopped. INFO | jvm 9 | 2008/02/08 01:40:52 | returned from WrapperListener.start() INFO | jvm 9 | 2008/02/08 01:40:52 | Send a packet STARTED : INFO | jvm 9 | 2008/02/08 01:40:52 | Startup runner thread stopped. DEBUG | wrapperp | 2008/02/08 01:40:52 | read a packet START_PENDING : 5000 DEBUG | wrapper | 2008/02/08 01:40:52 | JVM signalled a start pending with waitHint of 5000 millis. DEBUG | wrapperp | 2008/02/08 01:40:52 | read a packet STARTED : DEBUG | wrapper | 2008/02/08 01:40:52 | JVM signalled that it was started. DEBUG | wrapperp | 2008/02/08 01:40:52 | send a packet PING : ping INFO | jvm 9 | 2008/02/08 01:40:52 | Received a packet PING : ping INFO | jvm 9 | 2008/02/08 01:40:52 | Send a packet PING : ok DEBUG | wrapperp | 2008/02/08 01:40:52 | read a packet PING : ok DEBUG | wrapper | 2008/02/08 01:40:52 | Got ping response from JVM |
|
From: Richard E. <rem...@ed...> - 2008-02-13 19:09:06
|
You could always have the server start an ant process and have the ant xml file launch as many processes as you wish. Of course, the wrapper will only monitor the ant task. Richard Kory Hansen wrote: > Is there a way to wrap 2 or more java processes as a single service? We > want something where Service A starts two separate Java processes B and C. > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user -- Quis custodiet ipsos custodes: This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. |
|
From: Kory H. <kha...@gm...> - 2008-02-13 16:23:08
|
Is there a way to wrap 2 or more java processes as a single service? We want something where Service A starts two separate Java processes B and C. |
|
From: Leif M. <le...@ta...> - 2008-02-12 03:28:26
|
Steven, Unfortunately no, this is not going to work as is. The Wrapper only monitors the JVM that it launches itself. One option would be to figure out the command line that your first JVM is generating to launch the second JVM. Then have the Wrapper launch it directly. The only other way to do this is to have your primary JVM wait until its child JVMS have completed. The problem is that when you start adding various failure modes, things are going to get complicated for you very quickly. It is pretty difficult for the Wrapper to try to monitor the child processes of the JVM it launches. There would need to be a way for it to figure out which ones should be waited for and which ones could be left running etc. What happens if it crashes rather than completing, etc, etc, etc. Cheers, Leif Steven A Moussa/MAXIMUS wrote: > > I just configured a wrapper for one of our java applications. Now when > I start it as a Windows service, everything starts just fine and our > java app runs and continues running. The problem is that the Windows > wrapper service stops (even though the app continues to run in the > background just fine). I believe that our programs spawns another java > window to run itself (when you run it manually or with the -c option) > which may be why the wrapper thinks it's not running. Does this all > make sense so far? My question is if our application opens up another > java window to run, is there any way for the wrapper to know all > processes that were spawned by the parent process so that it will > continue to show it as running as a Windows service? That is, without > editing the code itself? > > If it helps, I attached the end of the log: > > INFO | jvm 1 | 2008/02/11 11:54:32 | > INFO | jvm 1 | 2008/02/11 11:54:32 | > INFO | jvm 1 | 2008/02/11 11:54:32 | > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'service.rmi_server_registry.xml' (null/null), priority=16000 > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new RmiServerRegistry map (portal=null/null|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new RmiServerRegistry map > (portal=schoolmax/null|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new RmiServerRegistry map > (portal=schoolmax/teacher|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new RmiServerRegistry map > (portal=schoolmax/admin|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new RmiServerRegistry map > (portal=schoolmax/family|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new RmiServerRegistry map > (portal=schoolmax/substitute|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | Reloading > LifecycleEventRegistry > INFO | jvm 1 | 2008/02/11 11:54:32 | ********* Loading > LifecycleEventRegistry files > INFO | jvm 1 | 2008/02/11 11:54:32 | > LifecycleEventRegistryFactory.loadRegistryFiles: starting > INFO | jvm 1 | 2008/02/11 11:54:32 | **** Opening manifest > 'deployment-manifest.mf' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/code_registry.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/code_registry.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'code_registry.all.all.all.lifecycle_event_registry.xml' (null/null), > priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/default.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/default.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'default.all.all.all.lifecycle_event_registry.xml' (null/null), > priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/external.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/external.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'external.all.all.all.lifecycle_event_registry.xml' (null/null), > priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/minimum.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/minimum.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'minimum.all.all.all.lifecycle_event_registry.xml' (null/null), > priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/pageBuilder.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/pageBuilder.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'pageBuilder.all.all.all.lifecycle_event_registry.xml' (null/null), > priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/pagemgr_config.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/pagemgr_config.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'pagemgr_config.all.all.all.lifecycle_event_registry.xml' (null/null), > priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/rmi_server.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/rmi_server.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'rmi_server.all.all.all.lifecycle_event_registry.xml' (null/null), > priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/script.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/script.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'script.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/notification.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/notification.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'notification.all.all.all.lifecycle_event_registry.xml' (null/null), > priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': 'config/alerts.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': 'config/alerts.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'alerts.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'all': > 'config/schoolmax/default.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver > 'null': > 'config/schoolmax/default.all.all.all.lifecycle_event_registry.xml' > INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: > 'default.all.all.all.lifecycle_event_registry.xml' (schoolmax/null), > priority=50 > INFO | jvm 1 | 2008/02/11 11:54:32 | Portal schoolmax.datamgr not > supported, skipping > INFO | jvm 1 | 2008/02/11 11:54:32 | > config_root='D:/app/schoolmax/instance_root/SMAX_train/config_root' > INFO | jvm 1 | 2008/02/11 11:54:32 | > INFO | jvm 1 | 2008/02/11 11:54:32 | > INFO | jvm 1 | 2008/02/11 11:54:32 | > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new LifecycleEventRegistry map > (portal=null/null|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new LifecycleEventRegistry map > (portal=schoolmax/null|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new LifecycleEventRegistry map > (portal=schoolmax/teacher|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new LifecycleEventRegistry map > (portal=schoolmax/admin|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new LifecycleEventRegistry map > (portal=schoolmax/family|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... > building new LifecycleEventRegistry map > (portal=schoolmax/substitute|overrideAll=true) > INFO | jvm 1 | 2008/02/11 11:54:32 | **************** DONE > RMISERVER Initializing cache manager ******************** > INFO | jvm 1 | 2008/02/11 11:54:32 | attempting to start server... > DEBUG | wrapperp | 2008/02/11 11:54:32 | send a packet PING : ping > INFO | jvm 1 | 2008/02/11 11:54:32 | Received a packet PING : ping > INFO | jvm 1 | 2008/02/11 11:54:32 | Send a packet PING : ok > INFO | jvm 1 | 2008/02/11 11:54:32 | Non-daemon thread count = 2 > - 1(system) = 1 > DEBUG | wrapperp | 2008/02/11 11:54:32 | read a packet PING : ok > DEBUG | wrapper | 2008/02/11 11:54:32 | Got ping response from JVM > INFO | jvm 1 | 2008/02/11 11:54:33 | SEVERE | rmimgr | 8889804 | > RMIServerFactory.getRemoteServer() - the server with the name > "rmi://localhost:1900/ServiceManager" doesn't appear to be running. > Attempting to startup. | Mon Feb 11 11:54:33 EST 2008 > DEBUG | wrapperp | 2008/02/11 11:54:37 | send a packet PING : ping > INFO | jvm 1 | 2008/02/11 11:54:37 | Received a packet PING : ping > INFO | jvm 1 | 2008/02/11 11:54:37 | Send a packet PING : ok > INFO | jvm 1 | 2008/02/11 11:54:37 | Non-daemon thread count = 2 > - 1(system) = 1 > DEBUG | wrapperp | 2008/02/11 11:54:37 | read a packet PING : ok > DEBUG | wrapper | 2008/02/11 11:54:37 | Got ping response from JVM > INFO | jvm 1 | 2008/02/11 11:54:40 | server started successfully! > INFO | jvm 1 | 2008/02/11 11:54:40 | attempting to start server... > INFO | jvm 1 | 2008/02/11 11:54:40 | server started successfully! > INFO | jvm 1 | 2008/02/11 11:54:40 | WrapperSimpleApp: main > method completed > DEBUG | wrapperp | 2008/02/11 11:54:41 | send a packet PING : ping > INFO | jvm 1 | 2008/02/11 11:54:41 | Received a packet PING : ping > INFO | jvm 1 | 2008/02/11 11:54:41 | Send a packet PING : ok > INFO | jvm 1 | 2008/02/11 11:54:41 | Non-daemon thread count = 1 > - 1(system) = 0 > INFO | jvm 1 | 2008/02/11 11:54:41 | All non-daemon threads have > stopped. Exiting. > INFO | jvm 1 | 2008/02/11 11:54:41 | WrapperManager.stop(0) > called by thread: Wrapper-Connection > INFO | jvm 1 | 2008/02/11 11:54:41 | Send a packet STOP : 0 > DEBUG | wrapperp | 2008/02/11 11:54:41 | read a packet PING : ok > DEBUG | wrapper | 2008/02/11 11:54:41 | Got ping response from JVM > DEBUG | wrapperp | 2008/02/11 11:54:41 | read a packet STOP : 0 > DEBUG | wrapper | 2008/02/11 11:54:41 | JVM requested a shutdown. (0) > DEBUG | wrapper | 2008/02/11 11:54:41 | wrapperStopProcess(0) called. > DEBUG | wrapper | 2008/02/11 11:54:41 | Sending stop signal to JVM > DEBUG | wrapperp | 2008/02/11 11:54:41 | send a packet STOP : NULL > INFO | jvm 1 | 2008/02/11 11:54:42 | Thread, Wrapper-Connection, > handling the shutdown process. > INFO | jvm 1 | 2008/02/11 11:54:42 | calling listener.stop() > INFO | jvm 1 | 2008/02/11 11:54:42 | WrapperSimpleApp: stop(0) > INFO | jvm 1 | 2008/02/11 11:54:42 | returned from listener.stop() > INFO | jvm 1 | 2008/02/11 11:54:42 | Send a packet STOPPED : 0 > DEBUG | wrapperp | 2008/02/11 11:54:42 | read a packet STOPPED : 0 > DEBUG | wrapper | 2008/02/11 11:54:42 | JVM signalled that it was > stopped. > INFO | jvm 1 | 2008/02/11 11:54:42 | Closing socket. > DEBUG | wrapperp | 2008/02/11 11:54:42 | socket read no code (closed?). > DEBUG | wrapperp | 2008/02/11 11:54:42 | server listening on port 32001. > INFO | jvm 1 | 2008/02/11 11:54:43 | calling System.exit(0) > DEBUG | wrapper | 2008/02/11 11:54:43 | JVM process exited with a > code of 0, leaving the wrapper exit code set to 0. > DEBUG | wrapper | 2008/02/11 11:54:43 | JVM exited normally. > STATUS | wrapper | 2008/02/11 11:54:44 | <-- Wrapper Stopped > STATUS | wrapper | 2008/02/11 11:55:47 | The rmiserver Service is > installed. > STATUS | wrapper | 2008/02/11 11:55:47 | Start Type: Manual > STATUS | wrapper | 2008/02/11 11:55:47 | Interactive: No > STATUS | wrapper | 2008/02/11 11:55:47 | Running: No > > Thanks in advance |
|
From: Steven A Moussa/M. <Ste...@ma...> - 2008-02-11 17:25:08
|
I just configured a wrapper for one of our java applications. Now when I start it as a Windows service, everything starts just fine and our java app runs and continues running. The problem is that the Windows wrapper service stops (even though the app continues to run in the background just fine). I believe that our programs spawns another java window to run itself (when you run it manually or with the -c option) which may be why the wrapper thinks it's not running. Does this all make sense so far? My question is if our application opens up another java window to run, is there any way for the wrapper to know all processes that were spawned by the parent process so that it will continue to show it as running as a Windows service? That is, without editing the code itself? If it helps, I attached the end of the log: INFO | jvm 1 | 2008/02/11 11:54:32 | INFO | jvm 1 | 2008/02/11 11:54:32 | INFO | jvm 1 | 2008/02/11 11:54:32 | INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'service.rmi_server_registry.xml' (null/null), priority=16000 INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new RmiServerRegistry map (portal=null/null|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new RmiServerRegistry map (portal=schoolmax/null|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new RmiServerRegistry map (portal=schoolmax/teacher|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new RmiServerRegistry map (portal=schoolmax/admin|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new RmiServerRegistry map (portal=schoolmax/family|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new RmiServerRegistry map (portal=schoolmax/substitute|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | Reloading LifecycleEventRegistry INFO | jvm 1 | 2008/02/11 11:54:32 | ********* Loading LifecycleEventRegistry files INFO | jvm 1 | 2008/02/11 11:54:32 | LifecycleEventRegistryFactory.loadRegistryFiles: starting INFO | jvm 1 | 2008/02/11 11:54:32 | **** Opening manifest 'deployment-manifest.mf' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/code_registry.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/code_registry.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'code_registry.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/default.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/default.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'default.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/external.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/external.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'external.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/minimum.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/minimum.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'minimum.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/pageBuilder.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/pageBuilder.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'pageBuilder.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/pagemgr_config.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/pagemgr_config.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'pagemgr_config.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/rmi_server.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/rmi_server.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'rmi_server.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/script.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/script.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'script.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/notification.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/notification.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'notification.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/alerts.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/alerts.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'alerts.all.all.all.lifecycle_event_registry.xml' (null/null), priority=0 INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'all': 'config/schoolmax/default.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | Config file for appserver 'null': 'config/schoolmax/default.all.all.all.lifecycle_event_registry.xml' INFO | jvm 1 | 2008/02/11 11:54:32 | ---> Loading config file: 'default.all.all.all.lifecycle_event_registry.xml' (schoolmax/null), priority=50 INFO | jvm 1 | 2008/02/11 11:54:32 | Portal schoolmax.datamgr not supported, skipping INFO | jvm 1 | 2008/02/11 11:54:32 | config_root='D:/app/schoolmax/instance_root/SMAX_train/config_root' INFO | jvm 1 | 2008/02/11 11:54:32 | INFO | jvm 1 | 2008/02/11 11:54:32 | INFO | jvm 1 | 2008/02/11 11:54:32 | INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new LifecycleEventRegistry map (portal=null/null|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new LifecycleEventRegistry map (portal=schoolmax/null|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new LifecycleEventRegistry map (portal=schoolmax/teacher|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new LifecycleEventRegistry map (portal=schoolmax/admin|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new LifecycleEventRegistry map (portal=schoolmax/family|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | CACHED RESOURCE MANAGER ... building new LifecycleEventRegistry map (portal=schoolmax/substitute|overrideAll=true) INFO | jvm 1 | 2008/02/11 11:54:32 | **************** DONE RMISERVER Initializing cache manager ******************** INFO | jvm 1 | 2008/02/11 11:54:32 | attempting to start server... DEBUG | wrapperp | 2008/02/11 11:54:32 | send a packet PING : ping INFO | jvm 1 | 2008/02/11 11:54:32 | Received a packet PING : ping INFO | jvm 1 | 2008/02/11 11:54:32 | Send a packet PING : ok INFO | jvm 1 | 2008/02/11 11:54:32 | Non-daemon thread count = 2 - 1(system) = 1 DEBUG | wrapperp | 2008/02/11 11:54:32 | read a packet PING : ok DEBUG | wrapper | 2008/02/11 11:54:32 | Got ping response from JVM INFO | jvm 1 | 2008/02/11 11:54:33 | SEVERE | rmimgr | 8889804 | RMIServerFactory.getRemoteServer() - the server with the name "rmi://localhost:1900/ServiceManager" doesn't appear to be running. Attempting to startup. | Mon Feb 11 11:54:33 EST 2008 DEBUG | wrapperp | 2008/02/11 11:54:37 | send a packet PING : ping INFO | jvm 1 | 2008/02/11 11:54:37 | Received a packet PING : ping INFO | jvm 1 | 2008/02/11 11:54:37 | Send a packet PING : ok INFO | jvm 1 | 2008/02/11 11:54:37 | Non-daemon thread count = 2 - 1(system) = 1 DEBUG | wrapperp | 2008/02/11 11:54:37 | read a packet PING : ok DEBUG | wrapper | 2008/02/11 11:54:37 | Got ping response from JVM INFO | jvm 1 | 2008/02/11 11:54:40 | server started successfully! INFO | jvm 1 | 2008/02/11 11:54:40 | attempting to start server... INFO | jvm 1 | 2008/02/11 11:54:40 | server started successfully! INFO | jvm 1 | 2008/02/11 11:54:40 | WrapperSimpleApp: main method completed DEBUG | wrapperp | 2008/02/11 11:54:41 | send a packet PING : ping INFO | jvm 1 | 2008/02/11 11:54:41 | Received a packet PING : ping INFO | jvm 1 | 2008/02/11 11:54:41 | Send a packet PING : ok INFO | jvm 1 | 2008/02/11 11:54:41 | Non-daemon thread count = 1 - 1(system) = 0 INFO | jvm 1 | 2008/02/11 11:54:41 | All non-daemon threads have stopped. Exiting. INFO | jvm 1 | 2008/02/11 11:54:41 | WrapperManager.stop(0) called by thread: Wrapper-Connection INFO | jvm 1 | 2008/02/11 11:54:41 | Send a packet STOP : 0 DEBUG | wrapperp | 2008/02/11 11:54:41 | read a packet PING : ok DEBUG | wrapper | 2008/02/11 11:54:41 | Got ping response from JVM DEBUG | wrapperp | 2008/02/11 11:54:41 | read a packet STOP : 0 DEBUG | wrapper | 2008/02/11 11:54:41 | JVM requested a shutdown. (0) DEBUG | wrapper | 2008/02/11 11:54:41 | wrapperStopProcess(0) called. DEBUG | wrapper | 2008/02/11 11:54:41 | Sending stop signal to JVM DEBUG | wrapperp | 2008/02/11 11:54:41 | send a packet STOP : NULL INFO | jvm 1 | 2008/02/11 11:54:42 | Thread, Wrapper-Connection, handling the shutdown process. INFO | jvm 1 | 2008/02/11 11:54:42 | calling listener.stop() INFO | jvm 1 | 2008/02/11 11:54:42 | WrapperSimpleApp: stop(0) INFO | jvm 1 | 2008/02/11 11:54:42 | returned from listener.stop() INFO | jvm 1 | 2008/02/11 11:54:42 | Send a packet STOPPED : 0 DEBUG | wrapperp | 2008/02/11 11:54:42 | read a packet STOPPED : 0 DEBUG | wrapper | 2008/02/11 11:54:42 | JVM signalled that it was stopped. INFO | jvm 1 | 2008/02/11 11:54:42 | Closing socket. DEBUG | wrapperp | 2008/02/11 11:54:42 | socket read no code (closed?). DEBUG | wrapperp | 2008/02/11 11:54:42 | server listening on port 32001. INFO | jvm 1 | 2008/02/11 11:54:43 | calling System.exit(0) DEBUG | wrapper | 2008/02/11 11:54:43 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. DEBUG | wrapper | 2008/02/11 11:54:43 | JVM exited normally. STATUS | wrapper | 2008/02/11 11:54:44 | <-- Wrapper Stopped STATUS | wrapper | 2008/02/11 11:55:47 | The rmiserver Service is installed. STATUS | wrapper | 2008/02/11 11:55:47 | Start Type: Manual STATUS | wrapper | 2008/02/11 11:55:47 | Interactive: No STATUS | wrapper | 2008/02/11 11:55:47 | Running: No Thanks in advance |
|
From: Ramakrishna Bv S. <ram...@in...> - 2008-02-11 05:19:35
|
Hi Leif Mortenson,
Thank you for quick response. Please check my answers in Blue for the
questions.
Please find the attachment for the log.
(See attached file: wrapperLog.txt)
I have checked the logs on other days as well , this issue is occuring but
for the recovery time is less, please check the log below:
INFO | jvm 9 | 2008/02/10 01:28:46 | Send a packet PING : ok
DEBUG | wrapperp | 2008/02/10 01:28:46 | read a packet PING : ok
DEBUG | wrapper | 2008/02/10 01:28:46 | Got ping response from JVM
DEBUG | wrapperp | 2008/02/10 01:28:50 | send a packet PING : ping
INFO | jvm 9 | 2008/02/10 01:28:50 | Received a packet PING : ping
INFO | jvm 9 | 2008/02/10 01:28:50 | Send a packet PING : ok
DEBUG | wrapperp | 2008/02/10 01:28:50 | read a packet PING : ok
DEBUG | wrapper | 2008/02/10 01:28:50 | Got ping response from JVM
DEBUG | wrapperp | 2008/02/10 01:28:54 | send a packet PING : ping
DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4)
DEBUG | wrapperp | 2008/02/10 01:29:25 | send a packet
SERVICE_CONTROL_CODE : 4
DEBUG | wrapperp | 2008/02/10 01:29:25 | socket send failed. (10053)
DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE
INFO | jvm 9 | 2008/02/10 01:29:25 | Read Timed out. (Last Ping was
30300 milliseconds ago)
INFO | jvm 9 | 2008/02/10 01:29:25 | Wrapper Manager: The Wrapper code
did not ping the JVM for 30 seconds. Quit and let the Wrapper resynch.
INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet RESTART : restart
INFO | jvm 9 | 2008/02/10 01:29:25 | Thread, Wrapper-Connection,
handling the shutdown process.
INFO | jvm 9 | 2008/02/10 01:29:25 | calling listener.stop()
INFO | jvm 9 | 2008/02/10 01:29:25 | Waiting for WrapperListener.stop
runner thread to complete.
INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner
thread started.
INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperSimpleApp: stop(1)
INFO | jvm 9 | 2008/02/10 01:29:25 | WrapperListener.stop runner
thread stopped.
INFO | jvm 9 | 2008/02/10 01:29:25 | returned from listener.stop() ->
1
INFO | jvm 9 | 2008/02/10 01:29:25 | shutdownJVM(1)
Thread:Wrapper-Connection
INFO | jvm 9 | 2008/02/10 01:29:25 | Send a packet STOPPED : 1
INFO | jvm 9 | 2008/02/10 01:29:25 | Closing socket.
INFO | jvm 9 | 2008/02/10 01:29:25 | calling System.exit(1)
INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 01:29:23,188
|INFO|SequencerTool|shutting down
INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 01:29:23,266
|INFO|SequencerTool|ok.
INFO | jvm 9 | 2008/02/10 01:29:25 | 2008-02-10 01:29:23,266
|INFO|SequencerTool|stopped.
DEBUG | wrapperp | 2008/02/10 01:29:25 | server listening on port 32002.
INFO | wrapper | 2008/02/10 01:29:25 | Wrapper Process has not received
any CPU time for 30 seconds. Extending timeouts.
DEBUG | wrapper | 2008/02/10 01:29:25 | JVM process exited with a code of
1, setting the wrapper exit code to 1.
ERROR | wrapper | 2008/02/10 01:29:25 | JVM exited unexpectedly.
DEBUG | wrapper | 2008/02/10 01:29:25 | ServiceControlHandler(4)
DEBUG | wrapperp | 2008/02/10 01:29:25 | socket not open, so packet not
sent SERVICE_CONTROL_CODE : 4
DEBUG | wrapper | 2008/02/10 01:29:25 | SERVICE_CONTROL_INTERROGATE
DEBUG | wrapper | 2008/02/10 01:29:25 | Waiting 5 seconds before
launching another JVM.
DEBUG | wrapper | 2008/02/10 01:29:29 | Classpath element,
wrapper.java.classpath.10, does not exist: ../classes
STATUS | wrapper | 2008/02/10 01:29:29 | Launching a JVM...
_________________________________________________________________________________________________
INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet
SERVICE_CONTROL_CODE : 4
INFO | jvm 7 | 2008/02/06 02:31:49 | ServiceControlCode from Wrapper
with code 4
DEBUG | wrapperp | 2008/02/06 02:31:49 | send a packet PING : ping
INFO | jvm 7 | 2008/02/06 02:31:49 | Received a packet PING : ping
INFO | jvm 7 | 2008/02/06 02:31:49 | Send a packet PING : ok
DEBUG | wrapperp | 2008/02/06 02:31:50 | read a packet PING : ok
DEBUG | wrapper | 2008/02/06 02:31:50 | Got ping response from JVM
DEBUG | wrapperp | 2008/02/06 02:31:54 | send a packet PING : ping
INFO | jvm 7 | 2008/02/06 02:31:54 | Received a packet PING : ping
INFO | jvm 7 | 2008/02/06 02:31:54 | Send a packet PING : ok
DEBUG | wrapperp | 2008/02/06 02:31:54 | read a packet PING : ok
DEBUG | wrapper | 2008/02/06 02:31:54 | Got ping response from JVM
DEBUG | wrapperp | 2008/02/06 02:31:58 | send a packet PING : ping
DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4)
DEBUG | wrapperp | 2008/02/06 02:32:50 | send a packet
SERVICE_CONTROL_CODE : 4
DEBUG | wrapperp | 2008/02/06 02:32:50 | socket send failed. (10053)
DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE
DEBUG | wrapper | 2008/02/06 02:32:50 | ServiceControlHandler(4)
DEBUG | wrapperp | 2008/02/06 02:32:50 | socket not open, so packet not
sent SERVICE_CONTROL_CODE : 4
DEBUG | wrapper | 2008/02/06 02:32:50 | SERVICE_CONTROL_INTERROGATE
INFO | jvm 7 | 2008/02/06 02:32:50 | Read Timed out. (Last Ping was
30400 milliseconds ago)
INFO | jvm 7 | 2008/02/06 02:32:50 | Wrapper Manager: The Wrapper code
did not ping the JVM for 30 seconds. Quit and let the Wrapper resynch.
INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet RESTART : restart
INFO | jvm 7 | 2008/02/06 02:32:50 | Thread, Wrapper-Connection,
handling the shutdown process.
INFO | jvm 7 | 2008/02/06 02:32:50 | calling listener.stop()
INFO | jvm 7 | 2008/02/06 02:32:50 | Waiting for WrapperListener.stop
runner thread to complete.
INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner
thread started.
INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperSimpleApp: stop(1)
INFO | jvm 7 | 2008/02/06 02:32:50 | WrapperListener.stop runner
thread stopped.
INFO | jvm 7 | 2008/02/06 02:32:50 | returned from listener.stop() ->
1
INFO | jvm 7 | 2008/02/06 02:32:50 | shutdownJVM(1)
Thread:Wrapper-Connection
INFO | jvm 7 | 2008/02/06 02:32:50 | Send a packet STOPPED : 1
INFO | jvm 7 | 2008/02/06 02:32:50 | Closing socket.
INFO | jvm 7 | 2008/02/06 02:32:50 | calling System.exit(1)
INFO | jvm 7 | 2008/02/06 02:32:50 | 2008-02-06 02:32:26,750
|INFO|SequencerTool|shutting down
DEBUG | wrapperp | 2008/02/06 02:32:50 | server listening on port 32002.
INFO | wrapper | 2008/02/06 02:32:50 | Wrapper Process has not received
any CPU time for 51 seconds. Extending timeouts.
DEBUG | wrapper | 2008/02/06 02:32:50 | JVM process exited with a code of
1, setting the wrapper exit code to 1.
ERROR | wrapper | 2008/02/06 02:32:50 | JVM exited unexpectedly.
DEBUG | wrapper | 2008/02/06 02:32:50 | Waiting 5 seconds before
launching another JVM.
DEBUG | wrapper | 2008/02/06 02:32:54 | Classpath element,
wrapper.java.classpath.10, does not exist: ../classes
STATUS | wrapper | 2008/02/06 02:32:54 | Launching a JVM...
Best Regards,
Ram
IBM Global Services India Pvt. Ltd.
Mindspace, Survey No 64, APIIC Software Layout,
Hi-tech City, Hyderabad -500 081
INDIA
Phone: +91-40-66956756
Leif Mortenson
<leif@tanukisoftw
are.com> To
Sent by: wra...@li...
wrapper-user-boun cc
ce...@li...
orge.net Subject
Re: [Wrapper-user] Issue with
wrapper
02/08/2008 01:17
PM
Please respond to
wrapper-user@list
s.sourceforge.net
Ramakrishna,
According to the log, the backend socket between the Wrapper and
Java process was somehow closed. The Wrapper is failing saying
that it can no longer communicate with the JVM. It keeps going
though because the JVM process is still running.
The JVM then gives up after around 30 seconds because it has not
received any communications from the Wrapper for that long. This
is a safety feature to shut the JVM process down just in case the
Wrapper process should ever crash.
Once the Wrapper detects that the JVM is shutdown, it is correctly
restarting the JVM.
The question is why is the backend socket being closed? This is not
a problem I have ever seen or heard of in the past. Is anything else
in the log file earlier than what you sent?
How easy is this to reproduce?
A: We cannot reproduce.
Does it always happen at the same time?
A: No,it does not happen at the sametime.
Is it possible that some other application on your system is closing
the socket?
A:Can't say whether someother application on the system might be trying to
close the socket.Another two applications are running on the same machine
with wrapper having same configuration.
Is your system under load at the time of this reset?
A: Yes, it was under load.
Does your Java application respond during the 30 seconds between
the socket being closed and the JVM shutting itself down?
A: Can't answer
Cheers,
Leif
Ramakrishna Bv Sanku wrote:
>
> Hi All,
>
> I came across a issue with wrapper, the Wrapper is getting degraded
> for sometime and getting into normal state after some time. Please
> check the wrapper log below.
>
> Can anyone help me and provide a solution, how can this be rectified.
>
> *Information from the wrapper log*
> WrapperManager class initialized by thread: main Using classloader:
> sun.misc.Launcher$AppClassLoader@27e3570f
> ...............
> Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
> ...............
>
> Extract from wrapper log
>
> DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4)
> DEBUG | wrapperp | 2008/02/08 01:40:42 | send a packet
> SERVICE_CONTROL_CODE : 4
> DEBUG | wrapperp | 2008/02/08 01:40:42 | socket send failed. (10053)
> DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE
> DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4)
> DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet
> not sent SERVICE_CONTROL_CODE : 4
> DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE
> INFO | jvm 8 | 2008/02/08 01:40:42 | Read Timed out. (Last Ping
> was 30600 milliseconds ago)
> INFO | jvm 8 | 2008/02/08 01:40:42 | Wrapper Manager: The Wrapper
> code did not ping the JVM for 30 seconds. Quit and let the Wrapper
> resynch.
> INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet RESTART : restart
> INFO | jvm 8 | 2008/02/08 01:40:42 | Thread, Wrapper-Connection,
> handling the shutdown process.
> INFO | jvm 8 | 2008/02/08 01:40:42 | calling listener.stop()
> INFO | jvm 8 | 2008/02/08 01:40:42 | Waiting for
> WrapperListener.stop runner thread to complete.
> INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner
> thread started.
> INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperSimpleApp: stop(1)
> INFO | jvm 8 | 2008/02/08 01:40:42 | WrapperListener.stop runner
> thread stopped.
> INFO | jvm 8 | 2008/02/08 01:40:42 | returned from
> listener.stop() -> 1
> INFO | jvm 8 | 2008/02/08 01:40:42 | shutdownJVM(1)
> Thread:Wrapper-Connection
> INFO | jvm 8 | 2008/02/08 01:40:42 | Send a packet STOPPED : 1
> INFO | jvm 8 | 2008/02/08 01:40:42 | Closing socket.
> INFO | jvm 8 | 2008/02/08 01:40:42 | calling System.exit(1)
> INFO | jvm 8 | 2008/02/08 01:40:42 | 2008-02-08
> 01:40:22,031|INFO|SequencerTool|shutting down
> DEBUG | wrapperp | 2008/02/08 01:40:42 | server listening on port 32002.
> DEBUG | wrapper | 2008/02/08 01:40:42 | ServiceControlHandler(4)
> DEBUG | wrapperp | 2008/02/08 01:40:42 | socket not open, so packet
> not sent SERVICE_CONTROL_CODE : 4
> DEBUG | wrapper | 2008/02/08 01:40:42 | SERVICE_CONTROL_INTERROGATE
> INFO | wrapper | 2008/02/08 01:40:42 | Wrapper Process has not
> received any CPU time for 48 seconds. Extending timeouts.
> DEBUG | wrapper | 2008/02/08 01:40:42 | JVM process exited with a
> code of 1, setting the wrapper exit code to 1.
> ERROR | wrapper | 2008/02/08 01:40:42 | JVM exited unexpectedly.
> DEBUG | wrapper | 2008/02/08 01:40:42 | Waiting 5 seconds before
> launching another JVM.
> DEBUG | wrapper | 2008/02/08 01:40:46 | Classpath element,
> wrapper.java.classpath.10, does not exist: ../classes
> STATUS | wrapper | 2008/02/08 01:40:46 | Launching a JVM...
> NONE | wrapper | 2008/02/08 01:40:46 | command:
> "D:\IBM\WBIServer\jre\bin\java.exe"
> -Dsequencer.context=AU04QWS130DCA32
> -Dsequencer.logs=d:\wppaup\runtime\var\sequencer\logs
> -Drepository.directory=D:\IBM\Sequencer -Djava.library.path="./lib"
> -classpath
>
"./lib/wrapper.jar;./lib/commons-collections-3.1.jar;./lib/commons-lang-2.1.jar;./lib/commons-logging-1.0.4.jar;./lib/commons-net-1.4.1.jar;./lib/jakarta-oro.jar;./lib/log4j-1.2.7.jar;./lib/spring.jar;./lib/velocity-1.4.jar;../classes;./lib/sequencer.jar"
> -Dwrapper.key="2ZXzPWYAZ6Ry7obW" -Dwrapper.port=32002
> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
> -Dwrapper.debug="TRUE" -Dwrapper.pid=2508 -Dwrapper.version="3.2.3"
> -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE"
> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=9
> org.tanukisoftware.wrapper.WrapperSimpleApp SequencerTool LOOP
> DEBUG | wrapper | 2008/02/08 01:40:46 | JVM started (PID=9500)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: Hayes, P. <Pet...@fm...> - 2008-02-08 18:38:17
|
Hi, I have just started using the wrapper on an AIX machine and have run into a few issues. The wrapper.java.library.path.append_system_path configuration parameter does not use the LIBPATH environment variable on AIX, it looks for LD_LIBRARY_PATH (for Solaris and Linux). I haven't tested on HP-UX or Mac OS X but those use the variables SHLIB_PATH and DYLD_LIBRARY_PATH respectively. My second issue is that it would seem to be a better implementation of library path management if instead of setting the java system property java.library.path, to instead just set the platform specific environment variable in case a library has to load another library. Any reason why this wouldn't be better. Finally, I need to control both the library path and the regular path (PATH) for my applications and it would be good if the PATH was managed for you through the configuration file in the same manner as library path. Thanks, Peter Hayes Architecture & Shared Technology Services | Fidelity Investments Management Technology |
165 messages has been excluded from this view by a project administrator.
