|
From: Simon C. \(Funmobile\) <sim...@fu...> - 2007-06-24 01:50:02
|
Hi Leif, the following is the wrapper.conf: #******************************************************************** # TestWrapper Properties # # NOTE - Please use src/conf/wrapper.conf.in as a template for your # own application rather than the values used for the # TestWrapper sample. #******************************************************************** # Java Application wrapper.java.command=3D/usr/java/jdk1.5.0_07/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=3Dorg.tanukisoftware.wrapper.test.Main wrapper.java.mainclass=3Dorg.tanukisoftware.wrapper.WrapperStartStopApp # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 # wrapper.java.classpath.1=3D../lib/wrappertest.jar # wrapper.java.classpath.2=3D../lib/wrapper.jar wrapper.java.classpath.1=3D/usr/local/wrapper-linux-x86-32-3.2.3/lib/wrap= per.jar wrapper.java.classpath.2=3D/usr/apache-tomcat-5.5.17/bin/bootstrap.jar wrapper.java.classpath.3=3D/usr/apache-tomcat-5.5.17/bin/commons-logging-= api.jar wrapper.java.classpath.4=3D/usr/java/jdk1.5.0_07/lib/tools.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) # wrapper.java.library.path.1=3D../lib wrapper.java.library.path.1=3D/usr/local/wrapper-linux-x86-32-3.2.3/lib # Java Additional Parameters #wrapper.java.additional.1=3D wrapper.java.additional.1=3D-Djava.endorsed.dirs=3D/usr/apache-tomcat-5.5= .17/common/endorsed wrapper.java.additional.2=3D-Dcatalina.base=3D/usr/apache-tomcat-5.5.17 wrapper.java.additional.3=3D-Dcatalina.home=3D/usr/apache-tomcat-5.5.17 wrapper.java.additional.4=3D-Djava.io.tmpdir=3D/usr/apache-tomcat-5.5.17/= temp wrapper.java.additional.5=3D-XX:MaxPermSize=3D64m # Initial Java Heap Size (in MB) #wrapper.java.initmemory=3D3 wrapper.java.initmemory=3D768 # Maximum Java Heap Size (in MB) #wrapper.java.maxmemory=3D64 wrapper.java.maxmemory=3D768 # Application parameters. Add parameters as needed starting from 1 #wrapper.app.parameter.1=3D wrapper.app.parameter.1=3Dorg.apache.catalina.startup.Bootstrap wrapper.app.parameter.2=3D1 wrapper.app.parameter.3=3Dstart wrapper.app.parameter.4=3Dorg.apache.catalina.startup.Bootstrap wrapper.app.parameter.5=3Dtrue wrapper.app.parameter.6=3D1 wrapper.app.parameter.7=3Dstop #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=3DPM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=3DINFO # Log file to use for wrapper output logging. wrapper.logfile=3D/var/log/tomcat/tomcat-1.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=3DLPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=3DDEBUG # 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 =3D 10 megabytes. wrapper.logfile.maxsize=3D0 # 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=3D0 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=3DDEBUG wrapper.ping.timeout=3D60 wrapper.statusfile=3D/var/run/tomcat/wrapper_1.status wrapper.filter.trigger.1=3Djava.lang.OutOfMemoryError wrapper.filter.action.1=3DRESTART and we use it for monitor tomcat 5.5.17. and the following is the debug = log: DEBUG | wrapperp | 2007/06/23 16:47:17 | read a packet PING : ok DEBUG | wrapper | 2007/06/23 16:47:17 | Got ping response from JVM DEBUG | wrapperp | 2007/06/23 16:47:22 | send a packet PING : ping INFO | jvm 2 | 2007/06/23 16:47:22 | Received a packet PING : ping INFO | jvm 2 | 2007/06/23 16:47:22 | Send a packet PING : ok DEBUG | wrapperp | 2007/06/23 16:47:22 | read a packet PING : ok DEBUG | wrapper | 2007/06/23 16:47:22 | Got ping response from JVM DEBUG | wrapperp | 2007/06/23 16:47:26 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:47:31 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:47:35 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:47:40 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:47:44 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:47:49 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:47:53 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:47:58 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:48:02 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:48:07 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:48:11 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:48:16 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:48:20 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:48:25 | send a packet PING : ping DEBUG | wrapperp | 2007/06/23 16:48:29 | send a packet PING : ping ERROR | wrapper | 2007/06/23 16:48:32 | JVM appears hung: Timed out = waiting for signal from JVM. wrapper seeems hang after this and cannot try to restart JVM. it is so = strange? I need to try to increase the value of ping timeout? Regards Simon. ----- Original Message -----=20 From: "Leif Mortenson" <le...@ta...> To: <wra...@li...> Sent: Sunday, June 24, 2007 8:45 AM Subject: Re: [Wrapper-user] JVM appears hung: Timed out waiting for = signal from JVM. problem > Simon, > Can you post your wrapper.conf file? Also if you are able to > reproduce this, can you set the wrapper.debug=3Dtrue property > and post the resulting wrapper.conf file as well? >=20 > >From what you posted, it looks like the Wrapper is detecting > that the JVM is hung, at which point it should be killing and > restarting the JVM process. I am not clear exactly what you > are see at that point however. >=20 > Cheers, > Leif >=20 > Simon Chan (Funmobile) wrote: > > hi all, > > I am using wrapper to monitor my tomcat 5.5.17 (use java 1.5) now. > > but I see that it is hung and show the following error: > > INFO | jvm 1 | 2007/06/22 18:34:25 | Send a packet PING : ok > > ERROR | wrapper | 2007/06/22 18:35:36 | JVM appears hung: Timed out > > waiting for signal from JVM. > > wrapper seems don't try to restart it and just leave it and make > > tomcat die. > > do u have any idea? > > Regards > > Simon. > > = ------------------------------------------------------------------------ > > > > = -------------------------------------------------------------------------= > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > = ------------------------------------------------------------------------ > > > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > =20 >=20 >=20 >=20 -------------------------------------------------------------------------= ------- > = -------------------------------------------------------------------------= > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ -------------------------------------------------------------------------= ------- > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user >=20 -------------------------------------------------------------------------= ------- No virus found in this incoming message. Checked by AVG Free Edition.=20 Version: 7.5.472 / Virus Database: 269.9.6/862 - Release Date: 6/22/2007 = 3:04 PM |