Re: [Wrapper-user] Wrapper Service Shutting Down on Log Out

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

Shannon.
Ok great.  Glad you got things working.

Cheers,
Leif

On Wed, Aug 7, 2013 at 10:24 PM, Shannon Sumner <sha...@gm...>wrote:

> Hi Leif,
>
> I need to apologize. It was a simple fix.  Just adding the dll and the
> application worked fine.  Thanks for your time.
>
> Shannon
>
>
> On Wed, Aug 7, 2013 at 9:07 AM, Shannon Sumner <sha...@gm...>wrote:
>
>> Hi Leif,
>>
>> I'm running on Windows Server 2003.  The Java version is 1.6.0_37.  The
>> Wrapper version is 3.5.20.
>>
>> I am getting a DLL error!
>>
>> WARNING - Unable to load the Wrapper's native library because none of the
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> following files:
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> wrapper-windows-x86-32.dll
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> wrapper.dll
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:           could
>> be located on the following java.library.path:
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> C:\XXX\PCI\AspectSSLDaemon\bin\.
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> Please see the documentation for the wrapper.java.library.path
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> configuration property.
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> System signals will not be handled correctly.
>>
>>
>> Let me look into fixing this.
>>
>> Thanks,
>>
>> Shannon
>>
>>
>> On Tue, Aug 6, 2013 at 10:04 PM, Leif Mortenson <
>> lei...@ta...> wrote:
>>
>>> Shannon,
>>> I am sorry for the trouble.  What environment are you running on?  Java
>>> version and bits?  OS version and bits? Wrapper version and bits?
>>>
>>> When the Wrapper first launches the JVM, are you seeing any warnings
>>> about the Wrapper.dll being missing or failing to load?  The Wrapper.dll is
>>> required for this and several other functions to work correctly.
>>>
>>> Cheers,
>>> Leif
>>>
>>>
>>> On Wed, Aug 7, 2013 at 12:55 AM, Shannon Sumner <sha...@gm...
>>> > wrote:
>>>
>>>> Hello All,
>>>>
>>>> I've created a Java Socket Listener Service extending WrapperListener.
>>>> It works wonderfully as a service until I logout.
>>>>
>>>> This is what appears in the logs:
>>>>
>>>>
>>>> INFO   | wrapper  | 2013/08/06 11:25:48 | User logged out.  Ignored.
>>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
>>>> ShutdownHook started
>>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
>>>> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
>>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Send a
>>>> packet STOP : 0
>>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Pausing
>>>> for 1,000ms to allow a clean shutdown...
>>>>
>>>>
>>>> I'm not sure how to fix this
>>>>
>>>> Here is my config file:
>>>>
>>>> # Java Main class. This class must implement the WrapperListener
>>>> interface
>>>> # or guarantee that the WrapperManager class is initialized. Helper
>>>> # classes are provided to do this for you. See the Integration section
>>>> # of the documentation for details.
>>>> wrapper.java.mainclass=com.xxx.pci.executor.AspectSSLDaemon
>>>>
>>>> # Java Classpath (include wrapper.jar) Add class path elements as
>>>> wrapper.java.classpath.1=../lib/*.jar
>>>>
>>>> # Name of the service
>>>> wrapper.name=AspectSSLDaemon
>>>>
>>>> # Display name of the service
>>>> wrapper.displayname=Aspect SSL Daemon
>>>>
>>>> # Description of the service
>>>> wrapper.description=Secure Aspect Daemon
>>>>
>>>> # Mode in which the service is installed. AUTO_START, DELAY_START or
>>>> DEMAND_START
>>>> wrapper.ntservice.starttype=AUTO_START
>>>> wrapper.debug=true
>>>> wrapper.ignore_user_logoffs=TRUE
>>>> wrapper.ignore_signals=TRUE
>>>>
>>>> # Log file to use for wrapper output logging.
>>>> wrapper.logfile=../logs/wrapper.log
>>>>
>>>> # Format of output for the log file.  (See docs for formats)
>>>> wrapper.logfile.format=LPTM
>>>>
>>>> # Log Level for log file output.  (See docs for log levels)
>>>> wrapper.logfile.loglevel=INFO
>>>>
>>>> # Maximum size that the log file will be allowed to grow to before
>>>> #  the log is rolled. Size is specified in bytes.  The default value
>>>> #  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
>>>> #  'm' (mb) suffix.  For example: 10m = 10 megabytes.
>>>> wrapper.logfile.maxsize=0
>>>>
>>>> # Maximum number of rolled log files which will be allowed before old
>>>> #  files are deleted.  The default value of 0 implies no limit.
>>>> wrapper.logfile.maxfiles=0
>>>>
>>>> # Log Level for sys/event log output.  (See docs for log levels)
>>>> wrapper.syslog.loglevel=NONE
>>>>
>>>> wrapper.ntservice.interactive=false
>>>>
>>>> Thanks,
>>>>
>>>> Shannon Sumner
>>>>
>>>>