Menu
▾
▴
Re: [Wrapper-user] Wrapper not respecting wrapper.restart.delay
|
From: Leif M. <lei...@ta...> - 2008-12-13 02:23:34
|
Matt, I just went back and retested this with 3.2.3 and appears to be working as expected. The following log shows a normal restart with the wrapper.restart.delay=30 property set: --- STATUS | wrapper | 2008/12/13 11:01:52 | JVM requested a restart. INFO | jvm 1 | 2008/12/13 11:01:53 | stop(0) STATUS | wrapper | 2008/12/13 11:02:24 | Launching a JVM... --- This second test is for the case where the JVM is frozen and is forcibly killed. --- ERROR | wrapper | 2008/12/13 11:07:01 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2008/12/13 11:07:01 | JVM did not exit on request, terminated INFO | wrapper | 2008/12/13 11:07:01 | JVM exited on its own while waiting to kill the application. STATUS | wrapper | 2008/12/13 11:07:01 | JVM exited in response to signal SIGKILL (9). STATUS | wrapper | 2008/12/13 11:07:30 | Launching a JVM... --- Your configuration file appears to be correct. From the log fragment you sent, it is not even waiting for the default 5 seconds. There was a related bug fixed in 3.3.0 which you may be seeing here: --- Fix a problem where the UNIX versions of the Wrapper would shutdown rather than restarting a frozen JVM if the arrival of the SIGCHLD signal from the old JVM process was delayed by more than a second or two. --- The "Unable to start a JVM" message shows up when the attempt to execute the JVM process is failing. That does not explain why it is happening immediately rather than after a 30 second wait. Is this a problem that you are able to reproduce? If so, would it be possible for you set the wrapper.debug=true property then send me the log file? The log file would contain information that would help me narrow this down. If this is reproduceable it would also be useful to see the debug output using version 3.3.1. Thanks in advance, Leif On Sat, Dec 13, 2008 at 4:29 AM, Matt Pierce <Mat...@co...> wrote: > I am using wrapper version 3.2.3 for an app running on Java Version: > 1.6.0_04-b12 Java HotSpot(TM) Server VM on Redhat Enterprise > 2.6.18-53.el5xen. I am having a problem I have seen in many other forums, > which has the following signature: > > ERROR | wrapper | 2008/12/11 08:03:59 | JVM appears hung: Timed out > waiting for signal from JVM. > ERROR | wrapper | 2008/12/11 08:03:59 | JVM did not exit on request, > terminated > STATUS | wrapper | 2008/12/11 08:04:01 | JVM exited in response to signal > SIGKILL (9). > ERROR | wrapper | 2008/12/11 08:04:01 | Unable to start a JVM > > The explanation in the other cases is that there are resources which have > not been freed up when the wrapper tries to restart. The fix suggested is > to set the wrapper.restart.delay property to some value high enough for the > resources to be freed again. I have set it to 30, but it doesn't seem to be > taking effect. The output from my log above is from after having set the > property and restarted the app with the wrapper. Below is the content of > our wrapper.conf. Any suggestions would be appreciated! > > Thanks, > Matt Pierce > > #******************************************************************** > # Wrapper Properties > #******************************************************************** > # Java Application > wrapper.java.command=%JAVA_HOME%/bin/java > > # Java Main class. This class must implement the WrapperListener interface > # or guarantee that the WrapperManager class is initialized. Helper > # classes are provided to do this for you. See the Integration section > # of the documentation for details. > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp > > # Java Classpath (include wrapper.jar) Add class path elements as > # needed starting from 1 > wrapper.java.classpath.1=../wrapper/wrapper.jar > wrapper.java.classpath.2=../bin/bootstrap.jar > wrapper.java.classpath.3=../bin/commons-logging-api.jar > wrapper.java.classpath.4=%JAVA_HOME%/lib/tools.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=../wrapper > wrapper.java.library.path.2=../webapps/catalog_engine/WEB-INF/lib > > # Java Additional Parameters > wrapper.java.additional.1=-server > wrapper.java.additional.2=-Dapp=CATENGINE > wrapper.java.additional.3=-Djava.endorsed.dirs=/home/catengine/tomcat/common/endorsed > wrapper.java.additional.4=-Dcatalina.base=/home/catengine/tomcat > wrapper.java.additional.5=-Dcatalina.home=/home/catengine/tomcat > wrapper.java.additional.6=-Djava.io.tmpdir=/home/catengine/tomcat/temp > #wrapper.java.additional.7=-XX:+DisableExplicitGC > wrapper.java.additional.7=-Dmail.smtp.connectiontimeout=300000 > wrapper.java.additional.8=-Dmail.smtp.timeout=300000 > #wrapper.java.additional.10=-XX:-OmitStackTraceInFastThrow > #wrapper.java.additional.10=-XX:SurvivorRatio=6 > #wrapper.java.additional.11=-XX:MaxNewSize=384M > wrapper.java.additional.9=-Xss256k > wrapper.java.additional.10=-XX:NewSize=768M > wrapper.java.additional.11=-XX:MaxNewSize=768M > wrapper.java.additional.12=-XX:+UseConcMarkSweepGC > wrapper.java.additional.13=-Djava.net.preferIPv4Stack=true > wrapper.java.additional.14=-Dcom.sun.management.jmxremote > wrapper.java.additional.15=-Dcom.sun.management.jmxremote.port=1099 > wrapper.java.additional.16=-Dcom.sun.management.jmxremote.authenticate=true > wrapper.java.additional.17=-Dcom.sun.management.jmxremote.ssl=false > wrapper.java.additional.18=-Dcom.sun.management.jmxremote.password.file=/home/catengine/jmxremote.password > wrapper.java.additional.19=-verbose:gc > wrapper.java.additional.20=-XX:+PrintGCDetails > > # Initial Java Heap Size (in MB) > wrapper.java.initmemory=2560 > > # Maximum Java Heap Size (in MB) > wrapper.java.maxmemory=2560 > > # Application parameters. Add parameters as needed starting from 1 > wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap > wrapper.app.parameter.2=1 > wrapper.app.parameter.3=start > wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap > wrapper.app.parameter.5=true > wrapper.app.parameter.6=1 > wrapper.app.parameter.7=stop > > #******************************************************************** > # 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=DEBUG > > # Log file to use for wrapper output logging. > wrapper.logfile=../logs/wrapper.log > > # Format of output for the log file. (See docs for formats) > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > #wrapper.logfile.loglevel=DEBUG > 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=50m > > # 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=10 > > # Log Level for sys/event log output. (See docs for log levels) > wrapper.syslog.loglevel=ERROR > > #******************************************************************** > # Wrapper NT 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. > > wrapper.ping.timeout=300 > > # Name of the service > wrapper.ntservice.name=prodtomcat > > # Display name of the service > wrapper.ntservice.displayname=Production Tomcat > > # Description of the service > wrapper.ntservice.description=Production Tomcat > > # 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 > > wrapper.restart.delay=30 > ------------------------------------------------------------------------------ > SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. > The future of the web can't happen without you. Join us at MIX09 to help > pave the way to the Next Web now. Learn more and register at > http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
