Re: [Wrapper-user] killing jboss process kills wrapper process

[Hoa Lu <hl...@sc...>]

Thanks Leif.  Kill -9 17197 for the example below did the trick.  The
wrapper restarted the jboss in a second jvm.


On 12/13/09 7:09 PM, "Leif Mortenson" <lei...@ta...>
wrote:

> Hoa,
> If you kill the JVM using "kill <NNN>" then the Java process will
> receive a SIGTERM.   That is a sift kill which the JVM has the
> opportunity to respond to or ignore.   See the javadocs for the
> WrapperListener.controlEvent method.
> http://wrapper.tanukisoftware.org/doc/english/javadocs.html?org/tanukisoftware
> /wrapper/WrapperListener.html
> 
> If your application decided to honor the SIGTERM request, then it will
> begin the JVM/Wrapper shutdown process as you are seeing.
> 
> If you wish to simulate a JVM crash, please use "kill -9 <NNN>" to
> forcibly kill the Java process.  In this case, the Wrapper will always
> restart the JVM.
> 
> If you kill the Wrapper process in this way, the JVM will shut itself
> down cleanly after the configured ping timeout has expired (30 seconds
> by default) but nothing will be restarted.
> 
> You can also create an actual JVM crash by calling
> WrapperManager.accessViolationNative()
> http://wrapper.tanukisoftware.org/doc/english/javadocs.html?org/tanukisoftware
> /wrapper/WrapperManager.html
> 
> Let me know if you have any more questions.
> 
> Cheers,
> Leif
> 
> On Sat, Dec 12, 2009 at 2:38 AM, Hoa Lu <hl...@sc...> wrote:
>> Resending this since I¹m not sure if it went through the first time.  It
>> didn¹t show up in the archives online.
>> 
>> Hi,
>> 
>> I downloaded the wrapper and followed the instructions for Integration
>> Method 1 using jboss.  How do I stimulate jboss jvm failure?  Whenever I try
>> to kill the jboss process, it seems to kill the wrapper process as well.
>>  I¹m running in a linux box.  Here is what I did:
>> 
>> ps ­ef | grep jboss
>> 
>> And get :
>> ------------------------
>> gateway  17195     1  0 11:06 ?        00:00:00
>> /home/gateway/jboss-5.1.0.GA/bin/./wrapper
>> <http://jboss-5.1.0.GA/bin/./wrapper>
>>  /home/gateway/jboss-5.1.0.GA/bin/../conf/wrapper.conf
>> <http://jboss-5.1.0.GA/bin/../conf/wrapper.conf>  wrapper.syslog.ident=jboss
>> wrapper.pidfile=/home/gateway/jboss-5.1.0.GA/bin/./jboss.pid
>> <http://jboss-5.1.0.GA/bin/./jboss.pid>  wrapper.name <http://wrapper.name>
>> =jboss wrapper.displayname=JBoss Application Server wrapper.daemonize=TRUE
>> 
>> gateway  17197 17195 99 11:06 ?        00:00:22
>> /usr/java/jdk1.6.0_11/bin/java -Dprogram.name=run.sh
>> -Djava.library.path=../lib -classpath
>> ../lib/wrapper.jar:./run.jar:/usr/java/jdk1.5.0_11/lib/tools.jar
>> -Dwrapper.key=rKAoI1Pvy2FtDsh8 -Dwrapper.port=32000
>> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
>> -Dwrapper.disable_console_input=TRUE -Dwrapper.pid=17195
>> -Dwrapper.version=3.3.9 -Dwrapper.native_library=wrapper
>> -Dwrapper.service=TRUE -Dwrapper.cpu.timeout=10 -Dwrapper.jvmid=1
>> org.tanukisoftware.wrapper.WrapperSimpleApp org.jboss.Main
>> 
>> gateway  17220 15030  0 11:06 pts/2    00:00:00 grep jboss
>> ----------------------------------
>> ./jboss status tells me  JBoss Application Server is running (PID:17195)
>> 
>> Which process can I kill to stimulate jboss going down and the wrapper will
>> restart jboss?  I tried both 17197 or 17195, and the end result is the same,
>> the wrapper gets killed.
>> 
>> Thanks,
>> Hoa
> 
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user