wrapper-user — User issues for Wrapper. (Support questions, etc.)

Re: [Wrapper-user] Non-console application shutdown

[Richard E. <rem...@ed...>]

On one of our windows machines the application is currently runing (a 
nightly build
and run test). So I ssh in and tail the wraper log, then I vpn in 
logging in as a windows
user. Then I log  out and I do not see the message: "User logged out. 
Ignored."; there
is nothing in the log indicating that I had logged out.

How do I generate the user logout event on a windows machine (I'm rather 
Linux
oriented)?

Thanks

Richard

Leif Mortenson wrote:

> Also what is happening while this is running?   Are there user 
> accounts being logged in
> and out?
>
> Cheers,
> Leif
>
> Richard Emberson wrote:
>
>> 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
>>>
>>
>>
>
>
>
> -------------------------------------------------------
> 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.

Re: [Wrapper-user] Non-console application shutdown

[Richard E. <rem...@ed...>]

This log is from a customer site. It is a machine that is dedicate to 
the application
being controlled by the wrapper. That said, sysadmin or folks involved with
application might be logging in/out, if not for anything else than 
making sure
things are up and running or looking at the log files.

I will have to see if I can get them to reproduce it problem (I will be 
trying to
do so here). If they can, I will suggest putting the wrapper in debug mode.

We've been wrapping the JBoss application here on linux, solaris and windows
for over three years so the situation at the customer site is unexpected.


Related question: recommendations of tools that wrap the wrapper; when the
wrapper exits how does one notify support staff that the wrapper is down?

Richard

Leif Mortenson wrote:

> Also what is happening while this is running?   Are there user 
> accounts being logged in
> and out?
>
> Cheers,
> Leif
>
> Richard Emberson wrote:
>
>> 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
>>>
>>
>>
>
>
>
> -------------------------------------------------------
> 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.

Re: [Wrapper-user] Non-console application shutdown

[Leif M. <le...@ta...>]

Also what is happening while this is running?   Are there user accounts 
being logged in
and out?

Cheers,
Leif

Richard Emberson wrote:

> 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
>>
>
>

Re: [Wrapper-user] Non-console application shutdown

[Leif M. <le...@ta...>]

Richard,
    As I said in my last message, could you please rerun this with 
wrapper.debug=true set?
That will give be more info to go on.

Cheers,
Leif

Richard Emberson wrote:

> 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
>>
>
>

Re: [Wrapper-user] Non-console application shutdown

[Richard E. <rem...@ed...>]

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.

Re: [Wrapper-user] Non-console application shutdown

[Leif M. <le...@ta...>]

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
>

Re: [Wrapper-user] Non-console application shutdown

[Richard E. <rem...@ed...>]

Thanks for replying. Unfortunately I do not have the start of the 
wrapper log,
just the end of it. We've got an installation script that generates the 
install
directories as well as instantiating various files with values, in 
particular,
the conf file. So, unless someone post install hand edited the file, I don't
think that the problem is that the wrapper.dll can not be found ... of 
course
someone might have moved the dll or changed its permissions but I don't
know that either.
I will investigate further.

Richard


Frank Fischer wrote:

>Hi
>
>I had a similar problem some days ago.
>It was because of a misconfiguration in the wrapper.conf.
>Check the path ot the wrapper.dll.
>More information about this specifc topic:
>http://wrapper.tanukisoftware.org/doc/english/faq.html#6
>
>Greetings
>Frank
>
>
>
>
>-------------------------------------------------------
>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.

RE: [Wrapper-user] Non-console application shutdown

[Frank F. <fra...@di...>]

Hi

I had a similar problem some days ago.
It was because of a misconfiguration in the wrapper.conf.
Check the path ot the wrapper.dll.
More information about this specifc topic:
http://wrapper.tanukisoftware.org/doc/english/faq.html#6

Greetings
Frank

[Wrapper-user] Non-console application shutdown

[Richard E. <rem...@ed...>]

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

-- 
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.

RE: [Wrapper-user] 64 bit Solaris sparc build

[<nic...@uk...>]

Ok cool.
I will give it a spin.

Leif, do you want to host a sparc-64 build of JSW?

-Nick





Internet
en...@df...@lists.sourceforge.net - 31/10/2005 15:29


Please respond to wra...@li...

Sent by:    wra...@li...



To:    wrapper-user

cc:


Subject:    RE: [Wrapper-user] 64 bit Solaris sparc build


I actually built one and linked it for myself using GCC. It's quite easy


-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of
nic...@uk...
Sent: Wednesday, October 26, 2005 8:06 PM
To: wra...@li...
Subject: [Wrapper-user] 64 bit Solaris sparc build


Does anyone know if a JSW build exists for 64 bit solaris?


Cheers,
Nick



This message and any attachments (the "message") is intended solely for
the addressees and is confidential.
If you receive this message in error, please delete it and immediately
notify the sender. Any use not in accord with its purpose, any
dissemination or disclosure, either whole or partial, is prohibited
except formal approval. The internet can not guarantee the integrity of
this message.
BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable
for the message if modified.

************************************************************************
**********************

BNP Paribas Private Bank London Branch is authorised by CECEI & AMF and
is regulated by the Financial Services Authority for the conduct of its
investment business in the United Kingdom.

BNP Paribas Securities Services London Branch is authorised by CECEI &
AMF and is regulated by the Financial Services Authority for the conduct
of its investment business in the United Kingdom.

BNP Paribas Fund Services UK Limited is authorised and regulated by the
Financial Services Authority



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Wrapper-user mailing list
Wra...@li...
 https://lists.sourceforge.net/lists/listinfo/wrapper-user

RE: [Wrapper-user] 64 bit Solaris sparc build

[Errol N. <en...@df...>]

I actually built one and linked it for myself using GCC. It's quite easy


-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of
nic...@uk...
Sent: Wednesday, October 26, 2005 8:06 PM
To: wra...@li...
Subject: [Wrapper-user] 64 bit Solaris sparc build


Does anyone know if a JSW build exists for 64 bit solaris?


Cheers,
Nick



This message and any attachments (the "message") is intended solely for
the addressees and is confidential.=20
If you receive this message in error, please delete it and immediately
notify the sender. Any use not in accord with its purpose, any
dissemination or disclosure, either whole or partial, is prohibited
except formal approval. The internet can not guarantee the integrity of
this message.
BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable
for the message if modified.=20

************************************************************************
**********************

BNP Paribas Private Bank London Branch is authorised by CECEI & AMF and
is regulated by the Financial Services Authority for the conduct of its
investment business in the United Kingdom.

BNP Paribas Securities Services London Branch is authorised by CECEI &
AMF and is regulated by the Financial Services Authority for the conduct
of its investment business in the United Kingdom.
 =20
BNP Paribas Fund Services UK Limited is authorised and regulated by the
Financial Services Authority



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] 64 bit Solaris sparc build

[<nic...@uk...>]

Does anyone know if a JSW build exists for 64 bit solaris?


Cheers,
Nick



This message and any attachments (the "message") is 
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified. 

**********************************************************************************************

BNP Paribas Private Bank London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in
the United Kingdom.

BNP Paribas Securities Services London Branch is authorised 
by CECEI & AMF and is regulated by the Financial Services 
Authority for the conduct of its investment business in 
the United Kingdom.
  
BNP Paribas Fund Services UK Limited is authorised and 
regulated by the Financial Services Authority

[Wrapper-user] tomcat 5.5

[John L. <mai...@st...>]

Hi - I know long time no post.

Say does the wrapper work with tomcat 5.5 or does it even need it since memory
managment appears to be much improved?

Thanks!

John

Re: [Wrapper-user] Useful functions accessiable via JNI from the wrapper-lib/dll?

[Leif M. <le...@ta...>]

Michael 'buk' Scherer wrote:

>Good morning.
>
>When talking about 3.2.0 you talk about the current HEAD in CVS?
>And, next question as usual, are there any docs? :]
>  
>
Yes its the HEAD in CVS.   The docs for the service related features are 
mainly in
the javadocs of the new classes, but there are several related 
properties which
have been added as well.  Each property has its own documentation page.

You can build the docs by running "build doc"

Cheers,
Leif

>Greetings,
> Michael
>
>On Thu, 20 Oct 2005 - 12:11am, Leif Mortenson wrote:
>
>  
>
>>Michael,
>>  The 3.2.0 release already has several new features for working with services
>>implemented.   (I know I need to get it completed and released...)  I think I
>>actually have everything you have asked for and more already implemented.
>>Don't know if you have the ability to build from source, but it is all in CVS
>>if
>>you do.
>>
>>  In 3.1.2, you might want to take a look at the wrapper.pidfile and
>>wrapper.jvm.pidfile properties.  They make it possible to output pid files that
>>can be used to tell whether or not the Service is currently running.
>>
>>Cheers,
>>Leif
>>
>>Michael 'buk' Scherer wrote:
>>
>>    
>>
>>>Good day list.
>>>
>>>I'm currently looking for some features I would need to implement into my
>>>application. I developed an application that fiddles with an xml-file which
>>>used to configure our main-java-services. Besides that my application
>>>generates JSW-config-files from the properties specified in that xml.
>>>
>>>One purpose for my application is, when running under Windows, to give the
>>>possibilty to install/remove/update a service.
>>>My problem now is, that I need to know
>>>a) is the service already installed
>>>b) is it running
>>>c) ...
>>>
>>>Cause my app is implemented in java as well I'm looking for a way to achive
>>>informations about installed windows-service in some one.
>>>Currently I'm parsing the output of srvinfo.exe, which is a bit ugly.
>>>
>>>Are there any function in the jsw-lib/dll to be called via JNI to achive my
>>>goals?
>>>
>>>Any other hints to libs/dlls are welcome as well.
>>>
>>>Thanks in advance.
>>>
>>>Greetings,
>>>Michael
>>>
>>> 
>>>
>>>      
>>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by:
>>Power Architecture Resource Center: Free content, downloads, discussions,
>>and more. http://solutions.newsforge.com/ibmarch.tmpl
>>_______________________________________________
>>Wrapper-user mailing list
>>Wra...@li...
>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>>
>>    
>>
>
>
>  
>

Re: [Wrapper-user] Useful functions accessiable via JNI from the wrapper-lib/dll?

[Michael 'b. S. <msc...@gi...>]

Good morning.

When talking about 3.2.0 you talk about the current HEAD in CVS?
And, next question as usual, are there any docs? :]

Greetings,
 Michael

On Thu, 20 Oct 2005 - 12:11am, Leif Mortenson wrote:

> Michael,
>   The 3.2.0 release already has several new features for working with services
> implemented.   (I know I need to get it completed and released...)  I think I
> actually have everything you have asked for and more already implemented.
> Don't know if you have the ability to build from source, but it is all in CVS
> if
> you do.
>
>   In 3.1.2, you might want to take a look at the wrapper.pidfile and
> wrapper.jvm.pidfile properties.  They make it possible to output pid files that
> can be used to tell whether or not the Service is currently running.
>
> Cheers,
> Leif
>
> Michael 'buk' Scherer wrote:
>
>> Good day list.
>>
>> I'm currently looking for some features I would need to implement into my
>> application. I developed an application that fiddles with an xml-file which
>> used to configure our main-java-services. Besides that my application
>> generates JSW-config-files from the properties specified in that xml.
>>
>> One purpose for my application is, when running under Windows, to give the
>> possibilty to install/remove/update a service.
>> My problem now is, that I need to know
>> a) is the service already installed
>> b) is it running
>> c) ...
>>
>> Cause my app is implemented in java as well I'm looking for a way to achive
>> informations about installed windows-service in some one.
>> Currently I'm parsing the output of srvinfo.exe, which is a bit ugly.
>>
>> Are there any function in the jsw-lib/dll to be called via JNI to achive my
>> goals?
>>
>> Any other hints to libs/dlls are welcome as well.
>>
>> Thanks in advance.
>>
>> Greetings,
>> Michael
>>
>>  
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>


-- 
 I am root. If you see me laughing, you better have a backup.

[Wrapper-user] Re: Wrapper service problem

[Leif M. <le...@ta...>]

Leif Mortenson wrote:

> Jani,
> Figured it out...   I added the following to the documentation for the 
> next release:
>
>                Note that under Windows XP and Windows 2000 SP3 and 
> above, by default,
>                the system will not allow services to be run for 
> accounts which do not
>                have a password set.
>
>                To make it possible to run as an account without a 
> password, you need to
>                disable the "Accounts: Limit local account use of blank 
> password to
>                console logon only." setting.  Go to the Administrative 
> Tools folder in
>                your control panel. Open the Local Security Policy 
> applet. Expand Local
>                Policy and then click on Security Options. On the right 
> side you will
>                find the above setting.   Right click to access its 
> properties dialog
>                and then disable it.
>
> Cheers,
> Leif
>
> jan...@pe... wrote:
>
>> Hello!
>>
>> I have a question about wrapper. We try to use it for running java
>> application on Windows 2000 Workstation as windows service.
>> We want to run this service as user xxxx  which has no password.
>>
>> In our .conf file we set option:
>> wrapper.ntservice.account=.\xxxx
>> This option is processed OK by wrapper.
>>
>> What should we do to tell wrapper that this user has no password? We 
>> tryed
>> option:
>> wrapper.ntservice.password=
>> We also tryed without this option (default should be no password).
>>
>> When we ty to start this service it doesn't start and we get a response:
>> The service did not start due to a logon failure.
>>
>> If we manually change logon properties of our service on windows 
>> services
>> (GUI), it starts OK after we delete all * characters in password fields.
>>
>> Since our plan is to install our service on many machines, it is wery 
>> hard
>> job to manually update passwords of service.
>> If you can suggest me any solution of this problem, please let me know!
>>
>>
>> Thanks in advance!
>>
>> Best regards,
>> Jani Kavcic
>>  
>>
>
>

[Wrapper-user] Re: Wrapper service problem

[Leif M. <le...@ta...>]

Leif Mortenson wrote:

> Jani,
> I have been trying to figure this one out tonight.  According the docs 
> on the CreateService
> API, it should be working as is by doing the following:
> wrapper.ntservice.password=
>
> That said however, I have not been able to start a service running as 
> a user without
> a password set.   You mentioned that you modify the installed service 
> settings manually
> are able to get it to work?  How are you setting it to a blank 
> password.   I tried clearing
> the password from the service properties dialog, but the service 
> startup still fails with
> a login error.   I have been trying to figure out whether or not the 
> password is actually
> being cleared...
>
> I have been trying to get this working under XP Pro SP2.
>
> Cheers,
> Leif
>
> jan...@pe... wrote:
>
>> Hello!
>>
>> I have a question about wrapper. We try to use it for running java
>> application on Windows 2000 Workstation as windows service.
>> We want to run this service as user xxxx  which has no password.
>>
>> In our .conf file we set option:
>> wrapper.ntservice.account=.\xxxx
>> This option is processed OK by wrapper.
>>
>> What should we do to tell wrapper that this user has no password? We 
>> tryed
>> option:
>> wrapper.ntservice.password=
>> We also tryed without this option (default should be no password).
>>
>> When we ty to start this service it doesn't start and we get a response:
>> The service did not start due to a logon failure.
>>
>> If we manually change logon properties of our service on windows 
>> services
>> (GUI), it starts OK after we delete all * characters in password fields.
>>
>> Since our plan is to install our service on many machines, it is wery 
>> hard
>> job to manually update passwords of service.
>> If you can suggest me any solution of this problem, please let me know!
>>
>>
>> Thanks in advance!
>>
>> Best regards,
>> Jani Kavcic
>>  
>>
>
>

[Wrapper-user] Wrapper service problem

[Leif M. <le...@ta...>]

Good question for the list.

Re: [Wrapper-user] I want to do sthg when I reach wrapper.max_failed_invocations!

[<nic...@uk...>]

Thanks Leif.

-Nick







Internet
le...@ta...@lists.sourceforge.net - 19/10/2005 16:47


Please respond to wra...@li...

Sent by:    wra...@li...



To:    wrapper-user

cc:


Subject:    Re: [Wrapper-user] I want to do sthg when I reach
       wrapper.max_failed_invocations!


nic...@uk... wrote:

>Are there hooks into these JVM lifecycle events (ie some way of notifying
>the outside world that a restart has occurred?)
>
>-Nick
>
>
Not currently.  There are requests to be able to execute arbitrary
external commands
when things like restarts take place, but they are not yet
implemented.   The only way
to do this right now would be to check the WrapperManager.getJVMId() method
when the JVM starts up and do any notifications from there if the id is
greater than 1.

Cheers,
Leif


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wrapper-user mailing list
Wra...@li...
 https://lists.sourceforge.net/lists/listinfo/wrapper-user


This message and any attachments (the "message") is 
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified. 

**********************************************************************************************

BNP Paribas Private Bank London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in
the United Kingdom.

BNP Paribas Securities Services London Branch is authorised 
by CECEI & AMF and is regulated by the Financial Services 
Authority for the conduct of its investment business in 
the United Kingdom.
  
BNP Paribas Fund Services UK Limited is authorised and 
regulated by the Financial Services Authority

Re: [Wrapper-user] I want to do sthg when I reach wrapper.max_failed_invocations!

[Leif M. <le...@ta...>]

nic...@uk... wrote:

>Are there hooks into these JVM lifecycle events (ie some way of notifying
>the outside world that a restart has occurred?)
>
>-Nick
>  
>
Not currently.  There are requests to be able to execute arbitrary 
external commands
when things like restarts take place, but they are not yet 
implemented.   The only way
to do this right now would be to check the WrapperManager.getJVMId() method
when the JVM starts up and do any notifications from there if the id is 
greater than 1.

Cheers,
Leif

Re: [Wrapper-user] I want to do sthg when I reach wrapper.max_failed_invocations!

[Leif M. <le...@ta...>]

Sebastien Chateau wrote:

> Hi Leif, just thanks for your fast and appropriate answer. My problem 
> is solved. Do you want to marry me? ;)
> Seb

Glad that worked for you.

I usually settle for donations :-)
Cheers,
Leif

Re: [Wrapper-user] I want to do sthg when I reach wrapper.max_failed_invocations!

[<nic...@uk...>]

Are there hooks into these JVM lifecycle events (ie some way of notifying
the outside world that a restart has occurred?)

-Nick







Internet
le...@ta...@lists.sourceforge.net - 19/10/2005 14:57


Please respond to wra...@li...

Sent by:    wra...@li...



To:    wrapper-user

cc:


Subject:    Re: [Wrapper-user] I want to do sthg when I reach
       wrapper.max_failed_invocations!


Sebastien,
This kind of thing is in the works for a future version.  But for now it
is not
directly supported.

There is a simple workaround however.  Write a new main class.  In it
simply do the following:

public void main( String[] args )
{
    if (WrapperManager.getJVMId() <= 5 )
    {
        MainClass.main( args );
    }
    else
    {
        RecoveryClass.main( args );
    }
}

Then increase the max failed invocations from 5 to 6.

Cheers,
Leif

Sebastien Chateau wrote:

> Hi,
> I'm using this great product to wrap my java application (some kind of
> client multimedia player) and I'm totally satisfied with it. So I'd like
> to first say thanks for developping it.
> Now, let my explain my will : my application is relatively unstable yet,
> and some conditions can make its lauch impossible. I have set
> /wrapper.max_failed_invocations /with value 5. After 5 failed
> invocations, the wrapper stops invoking, like it's supposed to do.
> Now, I'd like to be able to "catch" this "giving up event", and for
> example trigger the invocation of another main class on this giving up.
> My purpose is to keep a trace of these events (e.g. in a local file)
> because they reveal important information to me.
> Is there any way to do this? Thanks in advance!
> Seb
>
> PS : for now I regularely check the file "wrapper.log" and look inside
> if I can find the pattern "There were 5 failed launches in a row, each
> lasting less than 300 seconds.  Giving up."
>



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wrapper-user mailing list
Wra...@li...
 https://lists.sourceforge.net/lists/listinfo/wrapper-user


This message and any attachments (the "message") is 
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified. 

**********************************************************************************************

BNP Paribas Private Bank London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in
the United Kingdom.

BNP Paribas Securities Services London Branch is authorised 
by CECEI & AMF and is regulated by the Financial Services 
Authority for the conduct of its investment business in 
the United Kingdom.
  
BNP Paribas Fund Services UK Limited is authorised and 
regulated by the Financial Services Authority

Re: [Wrapper-user] I want to do sthg when I reach wrapper.max_failed_invocations!

[Sebastien C. <sch...@mi...>]

Hi Leif, just thanks for your fast and appropriate answer. My problem is 
solved. Do you want to marry me? ;)
Seb


Leif Mortenson wrote:

> Sebastien,
> This kind of thing is in the works for a future version.  But for now 
> it is not
> directly supported.
>
> There is a simple workaround however.  Write a new main class.  In it
> simply do the following:
>
> public void main( String[] args )
> {
>    if (WrapperManager.getJVMId() <= 5 )
>    {
>        MainClass.main( args );
>    }
>    else
>    {
>        RecoveryClass.main( args );
>    }
> }
>
> Then increase the max failed invocations from 5 to 6.
>
> Cheers,
> Leif
>
> Sebastien Chateau wrote:
>
>> Hi,
>> I'm using this great product to wrap my java application (some kind of
>> client multimedia player) and I'm totally satisfied with it. So I'd like
>> to first say thanks for developping it.
>> Now, let my explain my will : my application is relatively unstable yet,
>> and some conditions can make its lauch impossible. I have set
>> /wrapper.max_failed_invocations /with value 5. After 5 failed
>> invocations, the wrapper stops invoking, like it's supposed to do.
>> Now, I'd like to be able to "catch" this "giving up event", and for
>> example trigger the invocation of another main class on this giving up.
>> My purpose is to keep a trace of these events (e.g. in a local file)
>> because they reveal important information to me.
>> Is there any way to do this? Thanks in advance!
>> Seb
>>
>> PS : for now I regularely check the file "wrapper.log" and look inside
>> if I can find the pattern "There were 5 failed launches in a row, each
>> lasting less than 300 seconds.  Giving up."
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>


-- 
Sébastien CHATEAU
Mirane SAS
-------------------------
sch...@mi...
www.mirane.com
-------------------------
Tel : 05 57 77 12 15
Fax : 05 57 77 34 90

Re: [Wrapper-user] Useful functions accessiable via JNI from the wrapper-lib/dll?

[Leif M. <le...@ta...>]

Michael,
    The 3.2.0 release already has several new features for working with 
services
implemented.   (I know I need to get it completed and released...)  I 
think I
actually have everything you have asked for and more already implemented.
Don't know if you have the ability to build from source, but it is all 
in CVS if
you do.

    In 3.1.2, you might want to take a look at the wrapper.pidfile and
wrapper.jvm.pidfile properties.  They make it possible to output pid 
files that
can be used to tell whether or not the Service is currently running.

Cheers,
Leif

Michael 'buk' Scherer wrote:

>Good day list.
>
>I'm currently looking for some features I would need to implement into my 
>application. I developed an application that fiddles with an xml-file which 
>used to configure our main-java-services. Besides that my application generates 
>JSW-config-files from the properties specified in that xml.
>
>One purpose for my application is, when running under Windows, to give the 
>possibilty to install/remove/update a service.
>My problem now is, that I need to know
>a) is the service already installed
>b) is it running
>c) ...
>
>Cause my app is implemented in java as well I'm looking for a way to achive 
>informations about installed windows-service in some one.
>Currently I'm parsing the output of srvinfo.exe, which is a bit ugly.
>
>Are there any function in the jsw-lib/dll to be called via JNI to achive my 
>goals?
>
>Any other hints to libs/dlls are welcome as well.
>
>Thanks in advance.
>
>Greetings,
> Michael
>
>  
>

Re: [Wrapper-user] I want to do sthg when I reach wrapper.max_failed_invocations!

[Leif M. <le...@ta...>]

Sebastien,
This kind of thing is in the works for a future version.  But for now it 
is not
directly supported.

There is a simple workaround however.  Write a new main class.  In it
simply do the following:

public void main( String[] args )
{
    if (WrapperManager.getJVMId() <= 5 )
    {
        MainClass.main( args );
    }
    else
    {
        RecoveryClass.main( args );
    }
}

Then increase the max failed invocations from 5 to 6.

Cheers,
Leif

Sebastien Chateau wrote:

> Hi,
> I'm using this great product to wrap my java application (some kind of
> client multimedia player) and I'm totally satisfied with it. So I'd like
> to first say thanks for developping it.
> Now, let my explain my will : my application is relatively unstable yet,
> and some conditions can make its lauch impossible. I have set
> /wrapper.max_failed_invocations /with value 5. After 5 failed
> invocations, the wrapper stops invoking, like it's supposed to do.
> Now, I'd like to be able to "catch" this "giving up event", and for
> example trigger the invocation of another main class on this giving up.
> My purpose is to keep a trace of these events (e.g. in a local file)
> because they reveal important information to me.
> Is there any way to do this? Thanks in advance!
> Seb
>
> PS : for now I regularely check the file "wrapper.log" and look inside
> if I can find the pattern "There were 5 failed launches in a row, each
> lasting less than 300 seconds.  Giving up."
>