[Wrapper-user] RESTART not wanting to work

[David M. <dmc...@ch...>]

I've got the wrapper working well on a CentOS 3.6 system to wrap JBoss 4
(with Sun's Java 1.5.0_05-b05).  It starts and stops perfectly, but I
was really needing the restart filter to work on out of memory errors
(something we've had a problem with historically).  I added the trigger,
and it attempts to do a restart when I create an OOME, but the wrapper
crashes 9 times out of 10 when it checks to see if the JVM halted:

Shutdown complete
Halting VM
Critical error: wait for JVM process failed (No child processes)

I've tried all sorts of wrapper.conf settings to see if something works,
but it's only restarted twice, and it never did it more than once in a
row.  Here's the latest config file for what it's worth.  I'm really
hoping I'm just doing something stupid because JSW kicks ass!

set.JAVA_HOME=/usr/local/java
set.JBOSS_HOME=/usr/local/jboss
wrapper.java.command=%JAVA_HOME%/bin/java
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=%JBOSS_HOME%/bin/run.jar
wrapper.java.classpath.3=%JAVA_HOME%/lib/tools.jar
wrapper.java.library.path.1=../lib
wrapper.java.additional.1=-Dprogram.name=run.sh
wrapper.java.additional.2=-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
wrapper.java.additional.3=-Djava.endorsed.dirs=%JBOSS_HOME%/lib/endorsed
wrapper.java.additional.4=-verbosegc
wrapper.java.initmemory=1024
wrapper.java.maxmemory=1024
wrapper.app.parameter.1=org.jboss.Main
wrapper.console.format=M
wrapper.console.loglevel=INFO
wrapper.logfile=../jboss.log
wrapper.logfile.format=LTM
wrapper.logfile.loglevel=INFO
wrapper.logfile.maxsize=10m
wrapper.logfile.maxfiles=4
wrapper.syslog.loglevel=NONE
wrapper.filter.trigger.1=java.lang.OutOfMemoryError
wrapper.filter.action.1=RESTART
wrapper.restart.delay=30

If anyone can throw some light my way, I'd be most indebted!

David