Re: [Wrapper-user] JVM exits when user logs off, even when interactive=false

[Scott V. <van...@gm...>]

Yes I'm using a 64 bit JVM - java.exe is the executable. 



On Jan 13, 2011, at 5:41 PM, Christian Mueller <chr...@ta...> wrote:

> Scott,
> 
> When a user logs off windows send a signal to all running processes so
> they can respond accordingly.
> The wrapper catched the logoff signal and thus running as service
> ignoring this signal. However, a JVM by it's nature is not expected to
> continue running after a user logoff. Therefore the JVM by default
> start the shutdown (as it is in your case).
> Usually, the native library of the wrapper (wrapper.dll) protects the
> JVM in a way as it is catching this signal from the OS and in case of
> running as service also ignores this making it possible for the JVM to
> keep running even after receiving the logoff signal.
> 
> if the jvm you are using is also a 32-bit jvm and loading the 32-bit
> wrapper.dll, the native library should actually catch those signal.
> 
> Are you getting a message similar to this when the wrapper starts the JVM?
> 
> jvm 1    | WrapperManager: WARNING - Unable to load the Wrapper's
> native library because none of the
> jvm 1    | WrapperManager:           following files:
> jvm 1    | WrapperManager:             wrapper-windows-x86-32.dll
> jvm 1    | WrapperManager:             wrapper.dll
> jvm 1    | WrapperManager:           could be located on the following
> java.library.path:
> jvm 1    | WrapperManager:             C:\.......\lib
> jvm 1    | WrapperManager:           Please see the documentation for
> the wrapper.java.library.path
> jvm 1    | WrapperManager:           configuration property.
> jvm 1    | WrapperManager:           System signals will not be
> handled correctly.
> 
> 
> Furthermore what JVM version are you using? We noticed that javaw.exe
> is not always reliably processing the signal to the native library and
> initiating a shutdown of itself when the signal got delivered.
> 
> If you think the above mentioned did not apply to you, could you
> please enable debug mode, reproduce the issue and send us the full log
> output of that?
> 
> Cheers,
> Christian
> 
> On Fri, Jan 14, 2011 at 6:53 AM, Scott Vandezande <van...@gm...> wrote:
>> I have the following in my wrapper config file:
>> wrapper.ntservice.interactive=false
>> But when someone is logged into the console session (session 0) and then
>> logs off, the JVM exits, with the following in the log file:
>> INFO   | wrapper  | 2011/01/13 12:51:40 | User logged out.  Ignored.
>> STATUS | wrapper  | 2011/01/13 12:51:43 | <-- Wrapper Stopped
>> I'm using the 32-bit dll on a 64-bit OS.  Is this a known behavior in this
>> situation?
>> Thank you,
>> Scott
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand
>> malware threats, the impact they can have on your business, and how you
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>> 
>> 
> 
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand 
> malware threats, the impact they can have on your business, and how you 
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user