Re: [Wrapper-user] Wrapper kills the application unexpectedly

[Erik D. <eri...@fj...>]

Leif Mortenson wrote:
> The Wrapper is receiving a SIGCHLD signal from the OS and interpreting
> it as the Java process having stopped.  From the log however, it
> appears that JVM still exists as it continues on to shut it down.

Yes, we have implemented a shutdown hook in the application, so the 
application shuts down cleanly when it receives the shutdown notification.

> Can you tell me a little about your application?   Does your Java
> application run any child processes of its own?  I am wondering if
> such a grandchild process exiting might be causing this.  I am going
> to need to go back and run some more tests if that is the case.

No child processes.


> As a note, when you query the status, it is reporting as running
> because the Wrapper process itself is still running.  At the end of
> the log, it appears the Wrapper is just about to launch a second JVM
> invocation to recover from this problem.

It doesn't appear to try to relaunch the app, as far as I can see.

As a note, we have the same application deployed on other nodes where 
this problem does not occur. Which types of environment differences 
might be related?
(The Java version, JSW version and distro is as far as I can tell 
identical)



-- 
Best regards,

Erik Drolshammer