Menu
▾
▴
Re: [Wrapper-user] Non-console application shutdown
|
From: Richard E. <rem...@ed...> - 2005-11-03 14:56:07
|
The wrapper is being run as a service. The following is in the log file: INFO | jvm 5 | 2005/10/31 14:32:26 | [java] [Thr 4336] RFC Instrument: cosaccepttp reset uuid INFO | wrapper | 2005/10/31 14:37:19 | User logged out. Ignored. INFO | wrapper | 2005/10/31 14:37:19 | User logged out. Ignored. INFO | jvm 5 | 2005/10/31 14:37:20 | [java] Shutting down INFO | jvm 5 | 2005/10/31 14:37:20 | [java] Shutdown complete INFO | jvm 5 | 2005/10/31 14:37:20 | [java] Halting VM INFO | wrapper | 2005/10/31 14:37:20 | User logged out. Ignored. INFO | wrapper | 2005/10/31 14:37:20 | User logged out. Ignored. INFO | jvm 5 | 2005/10/31 14:38:23 | INFO | jvm 5 | 2005/10/31 14:38:23 | BUILD SUCCESSFUL INFO | jvm 5 | 2005/10/31 14:38:23 | Total time: 5,938 minutes 26 seconds ERROR | wrapper | 2005/10/31 14:38:24 | JVM exited unexpectedly. STATUS | wrapper | 2005/10/31 14:40:01 | Launching a JVM... INFO | jvm 6 | 2005/10/31 14:40:02 | Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org INFO | jvm 6 | 2005/10/31 14:40:02 | The first line is normal output from the application. The lines containing: "Shutting down", "Shutdown complete" and "Halting VM" are all being printed in the JBoss Shutdown Hook. The timing of the entries I would assume imply that they are all related, related to the user logout event. Something called System.exit() in the JBoss process - something triggered by the logout event - but how can that be if the wrapper is handling the event (as a code walkthru seems to indicate). Richard Leif Mortenson wrote: > Richard, > The "User logged out. Ignored." Messages show up when the Wrapper > is being run as > a service and an actual user who is logged in logs out to the Windows > login screen. The > service stays running in the background. This message is there to > help record the timing > of that event. > The message is displayed in response to a LOGOUT signal being > received from the > OS. Some Windows versions sent multiple signals, thus the duplicate > messages. It > is nothing to worry about and unrelated to shutdown. > > In this case, is what is happening is that your JBoss application > is calling System.exit > as it shuts down. Normally, this would cause the Wrapper to exit as > the application > had completed normally. When System.exit is called, the Java executes > all registered > shutdown hooks. The Wrapper registers such a shutdown hook to handle > the smooth > shutdown of the JVM. > The problem is that in your case, you have specifically disabled > the shutdown hooks. > When this is done, the Wrapper's shutdown hook is not run and the > Wrapper process > has no way of telling if the JVM crashed or shutdown intentionally. > So it states that > fact, assumes a crash and restarts the JVM. > Take a look at this page: > http://wrapper.tanukisoftware.org/doc/english/prop-disable-shutdown-hook.html > > > From your last sentence, it sounds like you are not expecting the > Java application > to be exiting? But that conflicts with what I am seeing in the log > file? Are you asking > why JBoss is shutting down in the first place? > > If you rerun your application with wrapper.debug=true then I can > tell you exactly > what is initiating the JVM shutdown (If it is being done by the > Wrapper). But I am > pretty sure your app is calling System.exit. Just not sure what is > initiating that. > > Cheers, > Leif > > Richard Emberson wrote: > >> I have the following in a wrapper log: >> >> INFO | wrapper | 2005/10/31 14:37:19 | User logged out. Ignored. >> INFO | wrapper | 2005/10/31 14:37:19 | User logged out. >> Ignored. INFO | jvm 5 | 2005/10/31 14:37:20 | [java] >> Shutting down >> INFO | jvm 5 | 2005/10/31 14:37:20 | [java] Shutdown >> complete INFO | jvm 5 | 2005/10/31 14:37:20 | [java] >> Halting VM >> INFO | wrapper | 2005/10/31 14:37:20 | User logged out. >> Ignored. INFO | wrapper | 2005/10/31 14:37:20 | User logged >> out. Ignored. >> INFO | jvm 5 | 2005/10/31 14:38:23 >> | INFO | jvm 5 | 2005/10/31 >> 14:38:23 | BUILD SUCCESSFUL >> INFO | jvm 5 | 2005/10/31 14:38:23 | Total time: 5,938 minutes >> 26 >> seconds >> >> ERROR | wrapper | 2005/10/31 14:38:24 | JVM exited unexpectedly. >> STATUS | wrapper | 2005/10/31 14:40:01 | Launching a >> JVM... INFO | jvm 6 | 2005/10/31 14:40:02 | Wrapper >> (Version 3.1.2) http://wrapper.tanukisoftware.org >> >> The line "Shutting down", "Sutdown complete" and "Halting VM" are >> being printed >> to standard out by a Shutdown Hook registered by JBoss, the >> application being >> controled by the wrapper. >> >> The "User logged out. Ignored" indicates that the wrapper is not >> being run in a >> console (looking at the source code) and when ignored, the wrapper >> does not >> kill its application. The wrapper then gones on to restart the >> application. >> >> Don't think its relevant, but: >> wrapper.disable_shutdown_hook=TRUE >> >> Why would there be multiple "User logged out. Ignored" lines? >> >> Any hints as to what mechanism(s) might lead to the wrapped application >> to stop? >> >> Thanks. >> >> Richard >> > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > -- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. |
