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

[Wrapper-user] Configuring Tomcat with wapper

[Adrian W. <adr...@as...>]

Hi,

I am trying to configure tomcat to run as a Windows Service using 
wrapper.  I have followed the instructions from the wrapper site which 
even uses tomcat as an example on how to set-up a service using the 
WrapperStartStopApp class.  See: 
http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html

However when I try to run Tomcat.bat to test it deploys OK before 
installing it as a service I get an exception and I cannot figure out 
what the problem is.  I have attached the wrapper log file and the conf 
file.  If anyone can help shed some light on this it would be greatly 
appriciated. 

Thanks in advance,
Adrian.

-- 
Adrian Walls				
Tel: +44 28 9072 5094			
E-mail: a....@as...	

Asidua Ltd.
Office Address: 10 Weavers Court, Belfast BT12 5GH.
Registered in Northern Ireland No. 043987

This electronic message contains information from Asidua Ltd. which may be privileged or confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or email (to the numbers or address above) immediately.

Re: [Wrapper-user] Wrapper, Cruisecontrol, Win32

[floor <flo...@ya...>]

Thanks for the info.  I'll have to look into that
software!  Just as a followup, though, I got wrapper
working with cruisecontrol by adding 

wrapper.startup.timeout=5000
wrapper.cpu.timeout=6000

to the conf file.  

--floor


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

[Wrapper-user] Error loading: C:\j2sdk1.4.2_03\jre\bin\client\jvm.dl

[Raj P. <coo...@gm...>]

I'm getting this error when I load up a large number of tomcat instances,
the number it takes varies from machine to machine but it seems
to be between 10-20
 wrapper | JVM started (PID=3D19416)
jvm 3 | Error loading: C:\j2sdk1.4.2_03\jre\bin\client\jvm.dll

I currently have a machine with 17 instances, if I try to add another
i get the above error. If I shut down one of the existing instances
I can start the new one. Then if I reboot ALL instances startup
just fine for a total of 18 instances.

Any ideas?

Re: [Wrapper-user] Wrapper, Cruisecontrol, Win32

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

Not really answering your question - but consider
http://www.pols.co.uk/beetlejuice/index.html instead of cruise control.
(Its much nicer/simpler than CC and its actually integrated with java
service wrapper - and for the moment its still free)





Internet
flo...@ya...@lists.sourceforge.net - 17/11/2005 23:03


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

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



To:    wrapper-user

cc:


Subject:    [Wrapper-user] Wrapper, Cruisecontrol, Win32


Has anyone gotten Wrapper to work with Cruisecontrol
on Win32?  If so, could you send your config file?  I
get it to start, but then get the message, "startup
failed: Timed out waiting for signal from the JVM."





__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com


-------------------------------------------------------
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. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
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

[Wrapper-user] Wrapper, Cruisecontrol, Win32

[anonymous a. <flo...@ya...>]

Has anyone gotten Wrapper to work with Cruisecontrol
on Win32?  If so, could you send your config file?  I
get it to start, but then get the message, "startup
failed: Timed out waiting for signal from the JVM."




		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

RE: [Wrapper-user] cannot load native lib on HPUX

[Tatalovich, N. <NTa...@fi...>]

Using Java Service Wrapper 3.1.2 with the HPUX platform requires that
the libwrapper.so file be renamed to libwrapper.sl and that you install
the gcc compiler in order to satisfy the dynamic link requirement to the
gcc library
/sww/bin/../lib/gcc-lib/hppa2.0w-hp-hpux11.11/3.2/../../../libgcc_s.sl

Any chance you will be fixing the HPUX build to remove the dependency on
the gcc library, thereby not implicating the gcc OSS and the associated
GNU GPL license?
Alternatively, if a fix includes the gcc library statically linked,
would that change the JSW license or are you able to get some type of
exception to the gcc GNU GPL V2.0 license?

Nicki

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: Friday, August 12, 2005 9:25 AM
To: wra...@li...
Subject: Re: [Wrapper-user] cannot load native lib on HPUX

Olaf,
    I have modified the build process for the 3.2.0 release so that the
distribution names will include both the processor and OS.   This should
help make this kind of thing clear, as well as making it possible to
have
multiple HPUX platform versions.

Cheers,
Leif

Olaf Zschiedrich wrote:

>HPUX can run on different processor architectures (PA-RISC and
Itanium).
>These two are not binary compatible. Normaly there should be 2
downloads
>for the wrapper on HPUX but there is only one and hint where it was
>build on. May be this one is not the correct one for your architecture.

>I posted to the newgroujp because of this! I have a customer using HPUX
>on both architectues and like to use the wrapper. My problem is that i
>have no access to the machines in order to build the wrapper from
>scratch there.
>May u can do this? I realy interressted to get the wrapper running
HPUX!
>Cu Olaf
>
>
>Am Do, den 28.07.2005 schrieb Andreas Wendt um 9:53:
>  
>
>>Hi Nicki,
>>
>>this is also the case on my system (HP-UX 11.11 with Java 1.4.2).
>>When looking inside the shared library with the chatr tool (similar to
ldd on Linux), I found a dependency on this GCC library:
>>
>>Running chatr lib/libwrapper.so...
>>chatr(warning): dl_header_ext.size != sizeof(dl_header_ext). Please
update your version of the chatr tool. 
>>lib/libwrapper.sl: 
>>         shared library 
>>         shared library dynamic path search:
>>             SHLIB_PATH     disabled  second 
>>             embedded path  disabled  first  Not Defined
>>         shared library list:
>>             dynamic
/sww/bin/../lib/gcc-lib/hppa2.0w-hp-hpux11.11/3.2/../../../libgcc_s.sl
>>         shared vtable support disabled
>>         static branch prediction disabled
>>         executable from stack: D (default)
>>         kernel assisted branch prediction enabled
>>         lazy swap allocation disabled
>>         text segment locking disabled
>>         data segment locking disabled
>>         third quadrant private data space disabled
>>         fourth quadrant private data space disabled
>>         third quadrant global data space disabled
>>         data page size: D (default)
>>         instruction page size: D (default)
>>         nulptr references enabled
>>
>>When running this tool on the wrapper library of version 3.0.5 (the
one I still use), I get this:
>>Running chatr lib/libwrapper.so...
>>chatr(warning): dl_header_ext.size != sizeof(dl_header_ext). Please
update your version of the linker. 
>>libwrapper.sl: 
>>         shared library 
>>         shared library dynamic path search:
>>             SHLIB_PATH     enabled   first  
>>             embedded path  disabled  second Not Defined
>>         shared library list:
>>             dynamic   /usr/lib/libc.2
>>             dynamic   /usr/lib/libnsl.1
>>             dynamic   /usr/lib/libpthread.1
>>         shared vtable support disabled
>>         static branch prediction disabled
>>         executable from stack: D (default)
>>         kernel assisted branch prediction enabled
>>         lazy swap allocation disabled
>>         text segment locking disabled
>>         data segment locking disabled
>>         third quadrant private data space disabled
>>         fourth quadrant private data space disabled
>>         third quadrant global data space disabled
>>         data page size: D (default)
>>         instruction page size: D (default)
>>
>>So it seems that somehow a GCC shared library is got linked in. If you
do not have GCC installed on your system, the loading of the wrapper lib
will fail.
>>So the HP-UX maintainer, Ashish Gawarikar, should have a look inside
his makefile to figure out, how GCC is forced not to include one of its
own libraries.
>>
>>Cheers,
>>Andreas
>>
>>
>>    
>>
>>>  
>>>
>>>I am trying to run the Java Service Wrapper 3.1.2 on HPUX B.11.11
with HP JVM 1.4.0 and having problems loading the wrapper's native
library. 
>>>
>>>Anyone know which HP JVM the Wrapper has been tested with or works
with HPUX? 
>>>
>>>Any help would be appreciated, I'm stuck and not sure what else to
try. 
>>>
>>>  
>>>
>>>FYI, I have this running on Windows, Solaris, Linux, and one of my 2
service apps is running on AIX using the first configuration specified
below. 
>>>
>>>  
>>>
>>>Detailed results of my test cases for HPUX follows: 
>>>
>>>  
>>>
>>>I am trying to start the James Mail Server v2.2.0 with the following
configuration: 
>>>
>>>JamesMailServer/bin holds wrapper, wrapper.jar, libwrapper.so 
>>>
>>>JamesMailServer/conf holds wrapper.conf with: 
>>>
>>>            wrapper.java.classpath.1=phoenix-loader.jar 
>>>
>>>            wrapper.java.classpath.2=wrapper.jar 
>>>
>>>            wrapper.java.library.path=./ 
>>>
>>>            There are wrapper.java.additional.#'s set up for phoenix
(app framework that James runs under) items 
>>>
>>>  
>>>
>>>Wrapper reports: 
>>>
>>>STATUS | wrapper  | 2005/07/25 20:09:27 | --> Wrapper Started as
Daemon 
>>>
>>>STATUS | wrapper  | 2005/07/25 20:09:27 | Launching a JVM... 
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 |  
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 | WARNING - Unable to load
the Wrapper's native library 'libwrapper.so'. 
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 |           The file is
located on the path at the following location but 
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 |           could not be
loaded: 
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 |
/opt/FileNet/Collaboration/JamesMailServer/bin/./libwrapper.so 
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 |           Please verify
that the file is readable by the current user 
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 |           and that the file
has not been corrupted in any way. 
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 |           System signals
will not be handled correctly. 
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 |  
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 | Wrapper (Version 3.1.2)
http://wrapper.tanukisoftware.org
>>>
>>>INFO   | jvm 1    | 2005/07/25 20:09:28 | 
>>>
>>>  
>>>
>>>I tried re-downloading and replacing the libwrapper.so but no change.

>>>
>>>  
>>>
>>>I turned on wrapper.debug and get the following: 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Spawning intermediate
process... 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Spawning daemon process... 
>>>
>>>STATUS | wrapper  | 2005/07/26 18:53:45 | --> Wrapper Started as
Daemon 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Using system timer. 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 18:53:45 | server listening on port
15012. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[0] :
../../_jvm/bin/java 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[1] :
-Djava.ext.dirs=../lib 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[2] :
-Dphoenix.home=.. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[3] :
-Djava.security.policy=jar:file:phoenix-loader.jar!/META-INF/java.policy

>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[4] :
-Djava.security.manager 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[5] :
-Dlog4j.configuration=file:../log4j.properties 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[6] : -Xms16m 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[7] : -Xmx64m 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[8] :
-Djava.library.path=./ 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[9] : -classpath 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[10] :
phoenix-loader.jar:wrapper.jar 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[11] :
-Dwrapper.key=7ZmDBln32MYoPDJB 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[12] :
-Dwrapper.port=15012 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[13] :
-Dwrapper.debug=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[14] :
-Dwrapper.use_system_time=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[15] :
-Dwrapper.version=3.1.2 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[16] :
-Dwrapper.native_library=wrapper 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[17] :
-Dwrapper.service=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[18] :
-Dwrapper.cpu.timeout=10 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[19] :
-Dwrapper.jvmid=1 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:45 | Command[20] :
org.apache.avalon.phoenix.launcher.DaemonLauncher 
>>>
>>>STATUS | wrapper  | 2005/07/26 18:53:45 | Launching a JVM... 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | WrapperManager class
initialized by thread: main  Using classloader:
sun.misc.Launcher$AppClassLoader@ae000d 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Wrapper Manager: JVM #1 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Wrapper Manager:
Registering shutdown hook 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Wrapper Manager: Using
wrapper 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Loading native library
failed: libwrapper.so  Cause: java.lang.UnsatisfiedLinkError: no wrapper
in java.library.path 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | WARNING - Unable to load
the Wrapper's native library 'libwrapper.so'. 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |           The file is
located on the path at the following location but 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |           could not be
loaded: 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |
/opt/FileNet/Collaboration/JamesMailServer/bin/./libwrapper.so 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |           Please verify
that the file is readable by the current user 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |           and that the file
has not been corrupted in any way. 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |           System signals
will not be handled correctly. 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Java Version   :
1.4.0.00-020529-18:43 Java HotSpot(TM) Server VM 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Java VM Vendor :
Hewlett-Packard Company 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Wrapper (Version 3.1.2)
http://wrapper.tanukisoftware.org
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |
WrapperManager.start(org.apache.avalon.phoenix.launcher.DaemonLauncher@f
dc96c, args[]) called by thread: main 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Open socket to wrapper... 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Opened Socket 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Send a packet KEY :
7ZmDBln32MYoPDJB 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |
handleSocket(Socket[addr=/127.0.0.1,port=15012,localport=65199]) 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 18:53:46 | accepted a socket from
127.0.0.1 on port 65199 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 18:53:46 | read a packet KEY :
7ZmDBln32MYoPDJB 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:46 | Got key from JVM:
7ZmDBln32MYoPDJB 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 18:53:46 | send a packet LOW_LOG_LEVEL
: 1 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 18:53:46 | send a packet PING_TIMEOUT
: 30 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:46 | Start Application. 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 18:53:46 | send a packet START : start

>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Received a packet
LOW_LOG_LEVEL : 1 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Wrapper Manager:
LowLogLevel from Wrapper is 1 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Received a packet
PING_TIMEOUT : 30 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Wrapper Manager:
PingTimeout from Wrapper is 30000 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Received a packet START :
start 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | calling listener.start() 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Send a packet START_PENDING
: 45000 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | DaemonLauncher: Starting up
Phoenix 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 18:53:46 | read a packet START_PENDING
: 45000 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 18:53:46 | JVM signalled a start
pending with waitHint of 45000 millis. 
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 18:53:46 | Phoenix 4.0.1 
>>>
>>>  
>>>
>>>  
>>>
>>>I changed the configuration as follows: 
>>>
>>>JamesMailServer/bin holds wrapper 
>>>
>>>JamesMailServer/lib holds wrapper.jar, libwrapper.so 
>>>
>>>JamesMailServer/conf holds wrapper.conf with: 
>>>
>>>            wrapper.java.classpath.1=phoenix-loader.jar 
>>>
>>>            wrapper.java.classpath.2=wrapper.jar 
>>>
>>>            wrapper.java.library.path=../lib 
>>>
>>>  
>>>
>>>Now it cannot find wrapper.jar, which is probably to be expected
since I didn't change the classpath.2 to ../lib/wrapper.jar 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Spawning intermediate
process... 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Spawning daemon process... 
>>>
>>>STATUS | wrapper  | 2005/07/26 19:23:58 | --> Wrapper Started as
Daemon 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Using system timer. 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 19:23:58 | server listening on port
15012. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Classpath element,
wrapper.java.classpath.2, does not exist: wrapper.jar 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[0] :
../../_jvm/bin/java 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[1] :
-Djava.ext.dirs=../lib 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[2] :
-Dphoenix.home=.. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[3] :
-Djava.security.policy=jar:file:phoenix-loader.jar!/META-INF/java.policy

>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[4] :
-Djava.security.manager 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[5] :
-Dlog4j.configuration=file:../log4j.properties 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[6] : -Xms16m 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[7] : -Xmx64m 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[8] :
-Djava.library.path=../lib 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[9] : -classpath 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[10] :
phoenix-loader.jar:wrapper.jar 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[11] :
-Dwrapper.key=oBu_BydY68Glrk6Y 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[12] :
-Dwrapper.port=15012 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[13] :
-Dwrapper.debug=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[14] :
-Dwrapper.use_system_time=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[15] :
-Dwrapper.version=3.1.2 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[16] :
-Dwrapper.native_library=wrapper 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[17] :
-Dwrapper.service=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[18] :
-Dwrapper.cpu.timeout=10 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[19] :
-Dwrapper.jvmid=1 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:58 | Command[20] :
org.apache.avalon.phoenix.launcher.DaemonLauncher 
>>>
>>>STATUS | wrapper  | 2005/07/26 19:23:58 | Launching a JVM... 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 | Exception in thread "main"
java.lang.ExceptionInInitializerError 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
com.silveregg.wrapper.WrapperManager.start(WrapperManager.java:203) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
org.apache.avalon.phoenix.launcher.DaemonLauncher.main(DaemonLauncher.ja
va:174) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 | Caused by:
java.security.AccessControlException: access denied
(java.util.PropertyPermission wrapper.debug read) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
java.security.AccessControlContext.checkPermission(AccessControlContext.
java:270) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
java.security.AccessController.checkPermission(AccessController.java:401
) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
java.lang.SecurityManager.checkPermission(SecurityManager.java:546) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1323)

>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
java.lang.System.getProperty(System.java:572) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
org.tanukisoftware.wrapper.WrapperManager.getBooleanProperty(WrapperMana
ger.java:772) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   at
org.tanukisoftware.wrapper.WrapperManager.<clinit>(WrapperManager.java:4
22) 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:23:58 |   ... 2 more 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:59 | JVM process exited with a
code of 1, setting the wrapper exit code to 1. 
>>>
>>>ERROR  | wrapper  | 2005/07/26 19:23:59 | JVM exited while loading
the application. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:59 | JVM was only running for 0
seconds leading to a failed restart count of 1. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:23:59 | Waiting 5 seconds before
launching another JVM. 
>>>
>>>  
>>>
>>>I changed the configuration as follows: 
>>>
>>>JamesMailServer/bin holds wrapper, wrapper.jar 
>>>
>>>JamesMailServer/lib holds libwrapper.so 
>>>
>>>JamesMailServer/conf holds wrapper.conf with: 
>>>
>>>            wrapper.java.classpath.1=phoenix-loader.jar 
>>>
>>>            wrapper.java.classpath.2=wrapper.jar 
>>>
>>>            wrapper.java.library.path=../lib 
>>>
>>>  
>>>
>>>Now it complains that it cannot load the native library because there
is no wrapper in java.library.path, which is correct, the wrapper is in
the bin directory not the lib directory. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Spawning intermediate
process... 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Spawning daemon process... 
>>>
>>>STATUS | wrapper  | 2005/07/26 19:32:01 | --> Wrapper Started as
Daemon 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Using system timer. 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 19:32:01 | server listening on port
15012. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[0] :
../../_jvm/bin/java 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[1] :
-Djava.ext.dirs=../lib 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[2] :
-Dphoenix.home=.. 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[3] :
-Djava.security.policy=jar:file:phoenix-loader.jar!/META-INF/java.policy

>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[4] :
-Djava.security.manager 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[5] :
-Dlog4j.configuration=file:../log4j.properties 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[6] : -Xms16m 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[7] : -Xmx64m 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[8] :
-Djava.library.path=../lib 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[9] : -classpath 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[10] :
phoenix-loader.jar:wrapper.jar 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[11] :
-Dwrapper.key=6aMwYbl_yezX8ds9 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[12] :
-Dwrapper.port=15012 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[13] :
-Dwrapper.debug=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[14] :
-Dwrapper.use_system_time=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[15] :
-Dwrapper.version=3.1.2 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[16] :
-Dwrapper.native_library=wrapper 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[17] :
-Dwrapper.service=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[18] :
-Dwrapper.cpu.timeout=10 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[19] :
-Dwrapper.jvmid=1 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:01 | Command[20] :
org.apache.avalon.phoenix.launcher.DaemonLauncher 
>>>
>>>STATUS | wrapper  | 2005/07/26 19:32:01 | Launching a JVM... 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | WrapperManager class
initialized by thread: main  Using classloader:
sun.misc.Launcher$AppClassLoader@ae000d 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Wrapper Manager: JVM #1 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Wrapper Manager:
Registering shutdown hook 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Wrapper Manager: Using
wrapper 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Loading native library
failed: libwrapper.so  Cause: java.lang.UnsatisfiedLinkError: no wrapper
in java.library.path 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | WARNING - Unable to load
the Wrapper's native library 'libwrapper.so'. 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |           The file is
located on the path at the following location but 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |           could not be
loaded: 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |
/opt/FileNet/Collaboration/JamesMailServer/bin/../lib/libwrapper.so 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |           Please verify
that the file is readable by the current user 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |           and that the file
has not been corrupted in any way. 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |           System signals
will not be handled correctly. 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Java Version   :
1.4.0.00-020529-18:43 Java HotSpot(TM) Server VM 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Java VM Vendor :
Hewlett-Packard Company 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Wrapper (Version 3.1.2)
http://wrapper.tanukisoftware.org
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |
WrapperManager.start(org.apache.avalon.phoenix.launcher.DaemonLauncher@e
4cbc4, args[]) called by thread: main 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Open socket to wrapper... 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Opened Socket 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Send a packet KEY :
6aMwYbl_yezX8ds9 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |
handleSocket(Socket[addr=/127.0.0.1,port=15012,localport=49327]) 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 19:32:02 | accepted a socket from
127.0.0.1 on port 49327 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 19:32:02 | read a packet KEY :
6aMwYbl_yezX8ds9 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:02 | Got key from JVM:
6aMwYbl_yezX8ds9 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 19:32:02 | send a packet LOW_LOG_LEVEL
: 1 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 19:32:02 | send a packet PING_TIMEOUT
: 30 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:02 | Start Application. 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 19:32:02 | send a packet START : start

>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Received a packet
LOW_LOG_LEVEL : 1 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Wrapper Manager:
LowLogLevel from Wrapper is 1 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Received a packet
PING_TIMEOUT : 30 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Wrapper Manager:
PingTimeout from Wrapper is 30000 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Received a packet START :
start 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | calling listener.start() 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Send a packet START_PENDING
: 45000 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | DaemonLauncher: Starting up
Phoenix 
>>>
>>>DEBUG  | wrapperp | 2005/07/26 19:32:02 | read a packet START_PENDING
: 45000 
>>>
>>>DEBUG  | wrapper  | 2005/07/26 19:32:02 | JVM signalled a start
pending with waitHint of 45000 millis. 
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 |  
>>>
>>>INFO   | jvm 1    | 2005/07/26 19:32:02 | Phoenix 4.0.1 
>>>
>>>  
>>>
>>>I changed the configuration as follows: 
>>>
>>>JamesMailServer/bin holds wrapper 
>>>
>>>JamesMailServer/lib holds libwrapper.so, wrapper.jar 
>>>
>>>JamesMailServer/conf holds wrapper.conf with: 
>>>
>>>            wrapper.java.classpath.1=phoenix-loader.jar 
>>>
>>>            wrapper.java.classpath.2=../lib/wrapper.jar 
>>>
>>>            wrapper.java.library.path=../lib 
>>>
>>>  
>>>
>>>Now I get access denied but I'm not sure what it is having trouble
accessing: 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Spawning intermediate
process... 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Spawning daemon process... 
>>>
>>>STATUS | wrapper  | 2005/07/27 15:41:54 | --> Wrapper Started as
Daemon 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Using system timer. 
>>>
>>>DEBUG  | wrapperp | 2005/07/27 15:41:54 | server listening on port
15012. 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[0] :
../../_jvm/bin/java 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[1] :
-Djava.ext.dirs=../lib 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[2] :
-Dphoenix.home=.. 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[3] :
-Djava.security.policy=jar:file:phoenix-loader.jar!/META-INF/java.policy

>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[4] :
-Djava.security.manager 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[5] :
-Dlog4j.configuration=file:../log4j.properties 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[6] : -Xms16m 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[7] : -Xmx64m 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[8] :
-Djava.library.path=../lib 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[9] : -classpath 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[10] :
phoenix-loader.jar:../lib/wrapper.jar 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[11] :
-Dwrapper.key=4LSJ4LeJ1boXnqoH 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[12] :
-Dwrapper.port=15012 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[13] :
-Dwrapper.debug=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[14] :
-Dwrapper.use_system_time=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[15] :
-Dwrapper.version=3.1.2 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[16] :
-Dwrapper.native_library=wrapper 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[17] :
-Dwrapper.service=TRUE 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[18] :
-Dwrapper.cpu.timeout=10 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[19] :
-Dwrapper.jvmid=1 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:54 | Command[20] :
org.apache.avalon.phoenix.launcher.DaemonLauncher 
>>>
>>>STATUS | wrapper  | 2005/07/27 15:41:54 | Launching a JVM... 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 | Exception in thread "main"
java.lang.ExceptionInInitializerError 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
com.silveregg.wrapper.WrapperManager.start(WrapperManager.java:203) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
org.apache.avalon.phoenix.launcher.DaemonLauncher.main(DaemonLauncher.ja
va:174) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 | Caused by:
java.security.AccessControlException: access denied
(java.util.PropertyPermission wrapper.debug read) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
java.security.AccessControlContext.checkPermission(AccessControlContext.
java:270) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
java.security.AccessController.checkPermission(AccessController.java:401
) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
java.lang.SecurityManager.checkPermission(SecurityManager.java:546) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1323)

>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
java.lang.System.getProperty(System.java:572) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
org.tanukisoftware.wrapper.WrapperManager.getBooleanProperty(WrapperMana
ger.java:772) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   at
org.tanukisoftware.wrapper.WrapperManager.<clinit>(WrapperManager.java:4
22) 
>>>
>>>INFO   | jvm 1    | 2005/07/27 15:41:55 |   ... 2 more 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:55 | JVM process exited with a
code of 1, setting the wrapper exit code to 1. 
>>>
>>>ERROR  | wrapper  | 2005/07/27 15:41:55 | JVM exited while loading
the application. 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:55 | JVM was only running for 0
seconds leading to a failed restart count of 1. 
>>>
>>>DEBUG  | wrapper  | 2005/07/27 15:41:55 | Waiting 5 seconds before
launching another JVM. 
>>>
>>>  
>>>
>>>File permissions are as follows: 
>>>
>>>-rwxrwxr-x   1 root       sys         151744 Oct  2  2004 wrapper 
>>>
>>>-r--r--r--   1 root       sys          20480 Oct  2  2004
libwrapper.so 
>>>
>>>-r--r--r--   1 root       sys          51939 Oct  2  2004 wrapper.jar

>>>
>>>-rw-rw-rw-   1 root       sys           4865 Jul 27 15:40
wrapper.conf 
>>>
>>>  
>>>
>>>I've also tried to run Java Service Wrapper 3.1.1 with the same
results. 
>>>
>>>  
>>>
>>>Could someone please help me. 
>>>
>>>   
>>>
>>>Nicki  
>>>
>>>  
>>>
>>>FileNet Corporation 
>>>
>>>www.filenet.com
>>>
>>>nta...@Fi... 
>>>
>>>Phone: (714) 327-3690 
>>>
>>>Fax:      (714) 327-5076 
>>>
>>>CONFIDENTIAL NOTICE: The contents of this message, including any
attachments, are confidential and are intended solely for the use of the
person or entity to whom the message was addressed. If you are not the
intended recipient of this message, please be advised that any
dissemination, distribution, or use of the contents of this message is
strictly prohibited. If you received this message in error, please
notify the sender. Please also permanently delete all copies of the
original message and any attached documentation. Thank you. 
>>>      
>>>



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing &
QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] SERVICE_CONTROL_INTERROGATE - Service Dies.

[Sean R. <sea...@px...>]

This unfortunalety is not easily reproducable as it only happens 
periodically.

I can confirm that I am using  Wrapper Version 3.1.2.  This info comes 
from the wrapper.log file during the startup of the service.

I have also check the file sizes for the wrapper.exe and wrapper.dll 
etc. with those included in the 3.1.2 binary distribution.  I have asked 
the support people to contact me as soon as they see this event occur 
again at which time I will be able to check the existance of java.exe in 
the process list as well as get the last minute or so from the log file.

Many thanks for the reply.

Regards
Sean Riley



Leif Mortenson wrote:

> Sean,
>    That thread discussed a bug that existed in version 3.1.0 which was 
> fixed in version
> 3.1.1.  There were some synchronization problems in the logging 
> code.   There have
> been no such problems reported in 3.1.2.
>
>    Is this reproduceable?   Could you post the last minute or so of 
> your wrapper.log
> file with debug output enabled so I can take a look at it?  Also 
> reconfirm that you
> really are using version 3.1.2.  The version should show up in the log 
> immediately
> after the JVM is launched.  I only ask because this really sounds like 
> a bug that
> should be fixed in 3.1.2.
>
>    When your application gets into this state, can you take a look at 
> the task manager.
> Can you find the wrapper.exe process and a java.exe process?  Or is 
> the java.exe
> process missing?   The JVM side of the wrapper code is designed to 
> shutdown the
> JVM if it ever loses contact with the Wrapper.   This will happen if 
> the Wrapper
> process has frozen for any reason.
>
> Cheers,
> Leif
>
> Sean Riley wrote:
>
>> Hi,
>>
>> I have read 
>> http://sourceforge.net/mailarchive/message.php?msg_id=9490872 and am 
>> experiencing the same issue.
>>
>> I am running v3.1.2 on a machine that has 1 processor unfortunately 
>> the service seems to intermitantly hang.  The message before this 
>> problem occurs is as follows
>>
>> ServiceControlHandler(4)
>> SERVICE_CONTROL_INTERROGATE
>>
>> The service looks as if it is still running however my app is not 
>> doing its job.. (I.e. monitoring a dir for the existance of files and 
>> writing to a log file)
>>
>> Is there anybody that has had this issue and been able to fix it? or 
>> Is there somthing I can do to narrow my search while troubleshooting.
>>
>> Many Thanks
>> Sean
>
>
>
>
>
> -------------------------------------------------------
> 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] SERVICE_CONTROL_INTERROGATE - Service Dies.

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

Sean,
    That thread discussed a bug that existed in version 3.1.0 which was 
fixed in version
3.1.1.  There were some synchronization problems in the logging code.   
There have
been no such problems reported in 3.1.2.

    Is this reproduceable?   Could you post the last minute or so of 
your wrapper.log
file with debug output enabled so I can take a look at it?  Also 
reconfirm that you
really are using version 3.1.2.  The version should show up in the log 
immediately
after the JVM is launched.  I only ask because this really sounds like a 
bug that
should be fixed in 3.1.2.

    When your application gets into this state, can you take a look at 
the task manager.
Can you find the wrapper.exe process and a java.exe process?  Or is the 
java.exe
process missing?   The JVM side of the wrapper code is designed to 
shutdown the
JVM if it ever loses contact with the Wrapper.   This will happen if the 
Wrapper
process has frozen for any reason.

Cheers,
Leif

Sean Riley wrote:

> Hi,
>
> I have read 
> http://sourceforge.net/mailarchive/message.php?msg_id=9490872 and am 
> experiencing the same issue.
>
> I am running v3.1.2 on a machine that has 1 processor unfortunately 
> the service seems to intermitantly hang.  The message before this 
> problem occurs is as follows
>
> ServiceControlHandler(4)
> SERVICE_CONTROL_INTERROGATE
>
> The service looks as if it is still running however my app is not 
> doing its job.. (I.e. monitoring a dir for the existance of files and 
> writing to a log file)
>
> Is there anybody that has had this issue and been able to fix it? or 
> Is there somthing I can do to narrow my search while troubleshooting.
>
> Many Thanks
> Sean

[Wrapper-user] SERVICE_CONTROL_INTERROGATE - Service Dies.

[Sean R. <sea...@bc...>]

Hi,

I have read 
http://sourceforge.net/mailarchive/message.php?msg_id=9490872 and am 
experiencing the same issue.

I am running v3.1.2 on a machine that has 1 processor unfortunately the 
service seems to intermitantly hang.  The message before this problem 
occurs is as follows

ServiceControlHandler(4)
SERVICE_CONTROL_INTERROGATE

The service looks as if it is still running however my app is not doing 
its job.. (I.e. monitoring a dir for the existance of files and writing 
to a log file)

Is there anybody that has had this issue and been able to fix it? or Is 
there somthing I can do to narrow my search while troubleshooting.

Many Thanks
Sean

Re: [Wrapper-user] tomcat 5.5

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

I still prefer to use JSW with tomcat - we still occasionally have jvm
crashes - and JSW means our users never notice these.

FWIW, I have done a slightly tighter integration between JSW and tomcat.

The StartStopApp approach has the flaw that start/stop are somewhat
asynchronous (ie the StopApp exits before tomcat)

This has the disadvantage that doing a "restart" usually results in a new
instance of tomcat starting before the previous one has finished exiting -
then you get port conflicts etc.

The "tighter" integration is still very simple - and still uses tomcat's
Bootstrap class to start and stop it. (ie it doesnt get involved in tomcat
internals)

If ppl think its valuable, I am quite happy to contribute it. (I have
copied it below in any case)

-Nick





import java.lang.management.ManagementFactory;

import javax.management.MBeanServer;
import javax.management.ObjectName;

import org.apache.catalina.startup.Bootstrap;
import org.tanukisoftware.wrapper.WrapperListener;
import org.tanukisoftware.wrapper.WrapperManager;

public class TomcatServiceWrapper implements WrapperListener {

    private static final String DEFAULT_WRAPPER_MBEAN_NAME =
"wrapper:type=Java Service Wrapper Control";
    private static final String WRAPPER_BEAN_NAME_KEY =
"wrapper.mbean.name";

    public static final String TOMCAT_START = "startd";
    public static final String TOMCAT_STOP = "stopd";

    private static final int JDK15_NOT_FOUND_EXIT_CODE = 1;

    public Integer start(String[] args) {
        if (isNotJDK15()) {
            WrapperManager.log(WrapperManager.WRAPPER_LOG_LEVEL_FATAL,
"-------------- !! TOMCAT FAILED TO START !! --------------\tJDK 1.5+ NOT
detected. JDK 1.5 or above is required");
            WrapperManager.stop(JDK15_NOT_FOUND_EXIT_CODE);
        }

        if (WrapperManager.getJVMId() > 1) {
            // we have restarted. Add hook here to run shell/bat command
        }
        registerServiceWrapperMbean();
        Bootstrap.main(new String[]{TOMCAT_START});
        WrapperManager.log(WrapperManager.WRAPPER_LOG_LEVEL_STATUS,
"--------------TOMCAT STARTED SUCCESSFULLY--------------");
        return null;
    }

    public int stop(int exitCode) {
        Bootstrap.main(new String[]{TOMCAT_STOP});
        return exitCode;
    }

    public void controlEvent(int event) {
        if (WrapperManager.isControlledByNativeWrapper()) {
            // The Wrapper will take care of this event
            WrapperManager.log(WrapperManager.WRAPPER_LOG_LEVEL_INFO,
"Control Event: to be handled by Native Wrapper");
        }
        else {
            // We are not being controlled by the Wrapper, so handle the
event ourselves.
            if ((event == WrapperManager.WRAPPER_CTRL_C_EVENT) ||
                (event == WrapperManager.WRAPPER_CTRL_CLOSE_EVENT) ||
                (event == WrapperManager.WRAPPER_CTRL_SHUTDOWN_EVENT)) {
                WrapperManager.stop(0);
            }
        }
    }

    public static void main(String[] args) {
        WrapperManager.start(new TomcatServiceWrapper(), args);
    }

    private boolean isNotJDK15() {
        try {
            Class.forName("java.lang.management.ManagementFactory");
            return false;
        }
        catch (ClassNotFoundException ignore) {
            return true;
        }
    }

    private void registerServiceWrapperMbean() {
        try {
            System.out.println("JDK 1.5+ detected, registering Java Service
Wrapper MBean");
            org.tanukisoftware.wrapper.jmx.WrapperManager managerBean = new
org.tanukisoftware.wrapper.jmx.WrapperManager();
            ObjectName name = new ObjectName(getName());
            MBeanServer server =
ManagementFactory.getPlatformMBeanServer();
            server.registerMBean(managerBean, name);
        }
        catch (Exception e) {
            System.err.println("Failed to register ServiceWrapper MBeans");
            e.printStackTrace();
        }
    }

    private String getName() {
        String name = System.getProperty(WRAPPER_BEAN_NAME_KEY);
        if (name == null) {
            System.out.println("Property \"" + WRAPPER_BEAN_NAME_KEY + "\"
not set. Using default : \"" + DEFAULT_WRAPPER_MBEAN_NAME + "\"");
            name = DEFAULT_WRAPPER_MBEAN_NAME;
        }
        return name.replaceAll("\"", "");
    }
}






Internet
mai...@st...@lists.sourceforge.net - 08/11/2005 01:40


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

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



To:    wrapper-user

cc:


Subject:    Re: [Wrapper-user] tomcat 5.5


Thanks!

I only use the error detection and recovery features as I run the
containers on linux.

I was just wondering if the wrapper was necessary with the new tomcat
5.5 and its better memory management.

John Larsen
Storm's i Media, LLC.
Java | Pipe

.................:DISCLAIMER:.....................
This e-mail and the information it contains is confidential and is
intended only for the addressee(s) named above or in the case of an
incorrectly addressed e-mail message, the intended recipient. If you
have received this e-mail and you are not the intended recipient any
disclosure, distribution, copying or any other use of this information
is strictly prohibited. If you have received this e-mail in error,
please accept our apologies and please notify the sender by e-mailing
jo...@st.... Please then delete this e-mail and any attachment
from your system. The views and opinions expressed in this e-mail are
the author's own and may not reflect the views and opinions of Storm's
i Media, LLC.

Although this email, including any attachments, is believed to be free
of any virus, or other defect which might affect any computer or IT
systeminto which it is received and opened, it is the responsibility of
the recipient to ensure that it is virus free, and no responsibility is
accepted for any loss or damage arising in any way from its use.

On Nov 7, 2005, at 1:14 AM, Leif Mortenson wrote:

> John,
>    It had been a while since I tried out the newer Tomcat versions so
> I gave it a try with
> the latest and greatest Tomcat 5.5.12.   Following the directions on
> the Wrapper site,
> it worked perfectly.  There were a couple differences in the actual
> configuration values
> as the new version appears to expect a couple more system properties.
> But the
> instructions lead the user to the correct config file.
>
>    I went ahead and attached it to this mail.
>
>    It looks like Tomcat 5.5 contains its own native binary capable of
> installing and
> running Tomcat as a service.   If that is the only feature of the
> Wrapper that you are
> looking for then it should meet your needs.   The Wrapper does go much
> farther
> however, particularly the error detection and recovery features.
>
> Cheers,
> Leif
>
> John Larsen wrote:
>
>> 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
>>
>
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=%JAVA_HOME%/bin/java
>
> # 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=org.tanukisoftware.wrapper.WrapperStartStopApp
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=../common/lib/wrapper.jar
> wrapper.java.classpath.2=%JAVA_HOME%/lib/tools.jar
> wrapper.java.classpath.3=../bin/bootstrap.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=../common/lib
>
> # Java Additional Parameters
> wrapper.java.additional.1=-
> Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> wrapper.java.additional.2=-Djava.util.logging.config.file=../conf/
> logging.properties
> wrapper.java.additional.3=-Djava.endorsed.dirs=../common/endorsed
> wrapper.java.additional.4=-Dcatalina.base=..
> wrapper.java.additional.5=-Dcatalina.home=..
> wrapper.java.additional.6=-Djava.io.tmpdir=../temp
>
> # Initial Java Heap Size (in MB)
> #wrapper.java.initmemory=3
>
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>
> # Application parameters.  Add parameters as needed starting from 1
> wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.2=1
> wrapper.app.parameter.3=start
> wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.5=true
> wrapper.app.parameter.6=1
> wrapper.app.parameter.7=stop
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Format of output for the console.  (See docs for formats)
> wrapper.console.format=PM
>
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=INFO
>
> # 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 Windows Properties
> #********************************************************************
> # Title to use when running as a console
> wrapper.console.title=Tomcat
>
> #********************************************************************
> # Wrapper Windows NT/2000/XP Service Properties
> #********************************************************************
> # WARNING - Do not modify any of these properties when an application
> #  using this configuration file has been installed as a service.
> #  Please uninstall the service before modifying this section.  The
> #  service can then be reinstalled.
>
> # Name of the service
> wrapper.ntservice.name=Tomcat
>
> # Display name of the service
> wrapper.ntservice.displayname=Tomcat
>
> # Description of the service
> wrapper.ntservice.description=Tomcat
>
> # Service dependencies.  Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed.  AUTO_START or DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
>



-------------------------------------------------------
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 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] tomcat 5.5

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

Thanks!

I only use the error detection and recovery features as I run the  
containers on linux.

I was just wondering if the wrapper was necessary with the new tomcat  
5.5 and its better memory management.

John Larsen
Storm's i Media, LLC.
Java | Pipe

................:DISCLAIMER:.....................
This e-mail and the information it contains is confidential and is  
intended only for the addressee(s) named above or in the case of an  
incorrectly addressed e-mail message, the intended recipient. If you  
have received this e-mail and you are not the intended recipient any  
disclosure, distribution, copying or any other use of this information  
is strictly prohibited. If you have received this e-mail in error,  
please accept our apologies and please notify the sender by e-mailing  
jo...@st.... Please then delete this e-mail and any attachment  
from your system. The views and opinions expressed in this e-mail are  
the author's own and may not reflect the views and opinions of Storm's  
i Media, LLC.

Although this email, including any attachments, is believed to be free  
of any virus, or other defect which might affect any computer or IT  
systeminto which it is received and opened, it is the responsibility of  
the recipient to ensure that it is virus free, and no responsibility is  
accepted for any loss or damage arising in any way from its use.

On Nov 7, 2005, at 1:14 AM, Leif Mortenson wrote:

> John,
>    It had been a while since I tried out the newer Tomcat versions so  
> I gave it a try with
> the latest and greatest Tomcat 5.5.12.   Following the directions on  
> the Wrapper site,
> it worked perfectly.  There were a couple differences in the actual  
> configuration values
> as the new version appears to expect a couple more system properties.   
> But the
> instructions lead the user to the correct config file.
>
>    I went ahead and attached it to this mail.
>
>    It looks like Tomcat 5.5 contains its own native binary capable of  
> installing and
> running Tomcat as a service.   If that is the only feature of the  
> Wrapper that you are
> looking for then it should meet your needs.   The Wrapper does go much  
> farther
> however, particularly the error detection and recovery features.
>
> Cheers,
> Leif
>
> John Larsen wrote:
>
>> 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
>>
>
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=%JAVA_HOME%/bin/java
>
> # 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=org.tanukisoftware.wrapper.WrapperStartStopApp
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=../common/lib/wrapper.jar
> wrapper.java.classpath.2=%JAVA_HOME%/lib/tools.jar
> wrapper.java.classpath.3=../bin/bootstrap.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=../common/lib
>
> # Java Additional Parameters
> wrapper.java.additional.1=- 
> Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> wrapper.java.additional.2=-Djava.util.logging.config.file=../conf/ 
> logging.properties
> wrapper.java.additional.3=-Djava.endorsed.dirs=../common/endorsed
> wrapper.java.additional.4=-Dcatalina.base=..
> wrapper.java.additional.5=-Dcatalina.home=..
> wrapper.java.additional.6=-Djava.io.tmpdir=../temp
>
> # Initial Java Heap Size (in MB)
> #wrapper.java.initmemory=3
>
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>
> # Application parameters.  Add parameters as needed starting from 1
> wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.2=1
> wrapper.app.parameter.3=start
> wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.5=true
> wrapper.app.parameter.6=1
> wrapper.app.parameter.7=stop
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Format of output for the console.  (See docs for formats)
> wrapper.console.format=PM
>
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=INFO
>
> # 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 Windows Properties
> #********************************************************************
> # Title to use when running as a console
> wrapper.console.title=Tomcat
>
> #********************************************************************
> # Wrapper Windows NT/2000/XP Service Properties
> #********************************************************************
> # WARNING - Do not modify any of these properties when an application
> #  using this configuration file has been installed as a service.
> #  Please uninstall the service before modifying this section.  The
> #  service can then be reinstalled.
>
> # Name of the service
> wrapper.ntservice.name=Tomcat
>
> # Display name of the service
> wrapper.ntservice.displayname=Tomcat
>
> # Description of the service
> wrapper.ntservice.description=Tomcat
>
> # Service dependencies.  Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed.  AUTO_START or DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
>

RE: [Wrapper-user] Problem with SMTP on Windows

[<hak...@la...>]

Hi!
I've added the javax.mail.Session and javax.mail.Message objects to the =
log.
Also set debug to true on Session object.
The latter was shown in wrapper.log
...
INFO   | jvm 1    | 2005/11/07 09:10:58 | Received a packet PING : ping
INFO   | jvm 1    | 2005/11/07 09:10:58 | Send a packet PING : ok
DEBUG  | wrapperp | 2005/11/07 09:10:58 | read a packet PING : ok
DEBUG  | wrapper  | 2005/11/07 09:10:58 | Got ping response from JVM
DEBUG  | wrapper  | 2005/11/07 09:11:00 | ServiceControlHandler(4)
DEBUG  | wrapper  | 2005/11/07 09:11:00 |   SERVICE_CONTROL_INTERROGATE
INFO   | jvm 1    | 2005/11/07 09:11:01 | DEBUG: setDebug: JavaMail =
version
1.3.3
INFO   | jvm 1    | 2005/11/07 09:11:01 | DEBUG: getProvider() returning
javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun
Microsystems, Inc]
INFO   | jvm 1    | 2005/11/07 09:11:01 | DEBUG SMTP: useEhlo true, =
useAuth
false
INFO   | jvm 1    | 2005/11/07 09:11:01 | DEBUG SMTP: trying to connect =
to
host "212.32.186.35", port 25, isSSL false
DEBUG  | wrapper  | 2005/11/07 09:11:01 | ServiceControlHandler(4)
DEBUG  | wrapper  | 2005/11/07 09:11:01 |   SERVICE_CONTROL_INTERROGATE
DEBUG  | wrapperp | 2005/11/07 09:11:02 | send a packet PING : ping
INFO   | jvm 1    | 2005/11/07 09:11:02 | Received a packet PING : ping
...


Below is the application log
...
(INFO, Thread-53, EVENT_LOG) 2005-11-07 09:11:00,828=20
<logvo logid=3D"4585b422785ac9de:1394894:10769c6689d:-7fde"=20
usr=3D"N/A"=20
class=3D"se.cesp.delivery.impl.OfferWebbEmail"=20
method=3D"handleDeliveryResult(DeliveryLogVO)"=20
hostip=3D"212.32.186.130">
<message>
OfferWebEmail.handleDeliveryResult: E-postlista
</message>
<logdata>
<var name=3D"emailList"><list>
  <string>rob...@la...</string>
  <string>ha...@cs...</string>
</list></var>
</logdata>
</logvo>=20

(INFO, Thread-53, EVENT_LOG) 2005-11-07 09:11:00,984=20
<logvo logid=3D"4585b422785ac9de:1394894:10769c6689d:-7fde"=20
usr=3D"N/A"=20
class=3D"se.cesp.delivery.common.util.EmailCommunicator"=20
method=3D"send(MessageVO, ArrayList)"=20
hostip=3D"212.32.186.130">
<message>
EmailCommunicator.send: convertedaddresses
</message>
<logdata>
<var =
name=3D"adresses">rob...@la...,ha...@cs...</var>
</logdata>
</logvo>=20

(ERROR, Thread-53, EVENT_LOG) 2005-11-07 09:11:02,078=20
<logvo logid=3D"4585b422785ac9de:1394894:10769c6689d:-7fde"=20
usr=3D"N/A"=20
class=3D"se.cesp.delivery.common.util.EmailCommunicator"=20
method=3D"send(MessageVO, ArrayList)"=20
hostip=3D"212.32.186.130">
<message>
Utskick f=F6r personen kunde inte slutf=F6ras.
</message>
<logdata>
<var name=3D"javax.mail.Message"><javax.mail.Message>
  <dh>
    <dataSource isNull=3D"true"></dataSource>
    <objDataSource isNull=3D"true"></objDataSource>
    <object class=3D"string">&lt;HTML&gt;
&lt;HEAD&gt;
&lt;TITLE&gt;
Stadspuls
&lt;/TITLE&gt;
&lt;/HEAD&gt;
&lt;BODY&gt;
&lt;a href=3D"http://www.stadspuls.se"&gt;&lt;img
src=3D"http://www.stadspuls.se/files/6e5ac004-72e9-4ccf-b809-011fdbf468c7=
/581b
91bd-b142-4c5b-802c-927d3362c0e5/ad6887c5-fcb3-4a52-82ac-25670bd6d0c9.jpg=
"&g
t;
&lt;/a&gt;
&lt;table style=3D"font-family:Verdana;font-size:10"&gt;	&lt;tr&gt;
&lt;td&gt;			&lt;table
style=3D"font-family:Verdana;font-size:10"&gt;
&lt;tr&gt;					&lt;td&gt;Skickat:
&lt;b&gt;2005-11-07&lt;/b&gt;					&lt;/td&gt;
&lt;/tr&gt;				&lt;tr&gt;
&lt;td&gt;Slutdatum: &lt;b&gt;2005-11-09&lt;/b&gt;
&lt;/td&gt;				&lt;/tr&gt;
&lt;tr&gt;					&lt;td&gt;Avs=E4ndare:
&lt;b&gt;STADSPULS&lt;/b&gt;					&lt;/td&gt;
&lt;/tr&gt;			&lt;/table&gt;		&lt;/td&gt;
&lt;td&gt;&lt;img
src=3D"http://www.stadspuls.se/files/6e5ac004-72e9-4ccf-b809-011fdbf468c7=
/Logo
type/Logotype.jpg"&gt;
		&lt;/td&gt;	&lt;/tr&gt;&lt;/table&gt;&lt;/BODY&gt;
&lt;/HTML&gt;
</object>
    <objectMimeType>text/html</objectMimeType>
    <currentCommandMap isNull=3D"true"></currentCommandMap>
    <transferFlavors/>
    <dataContentHandler isNull=3D"true"></dataContentHandler>
    <factoryDCH isNull=3D"true"></factoryDCH>
    <oldFactory isNull=3D"true"></oldFactory>
    <shortType isNull=3D"true"></shortType>
  </dh>
  <content isNull=3D"true"></content>
  <contentStream isNull=3D"true"></contentStream>
  <headers>
    <headers>
      <javax.mail.internet.hdr>
        <name>Return-Path</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Received</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Message-Id</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Resent-Date</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Date</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Resent-From</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>From</name>
        <line>From: se...@st...</line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Reply-To</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Sender</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>To</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Subject</name>
        <line>Subject: =3D?Cp1252?Q?testa_det_h=3DE4r?=3D</line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Cc</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>In-Reply-To</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Resent-Message-Id</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Errors-To</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>MIME-Version</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Content-Type</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Content-Transfer-Encoding</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Content-MD5</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Bcc</name>
        <line>Bcc: rob...@la..., ha...@cs...</line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>:</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Content-Length</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
      <javax.mail.internet.hdr>
        <name>Status</name>
        <line isNull=3D"true"></line>
      </javax.mail.internet.hdr>
    </headers>
  </headers>
  <flags>
    <system__flags>0</system__flags>
    <user__flags isNull=3D"true"></user__flags>
  </flags>
  <modified>true</modified>
  <saved>false</saved>
  <strict>true</strict>
  <msgnum>0</msgnum>
  <expunged>false</expunged>
  <folder isNull=3D"true"></folder>
  <session>
    <props>
      <property name=3D"mail.smtp.port" value=3D"25"/>
      <property name=3D"mail.transport.protocol" value=3D"smtp"/>
      <property name=3D"mail.smtp.host" value=3D"212.32.186.35"/>
    </props>
    <authenticator isNull=3D"true"></authenticator>
    <authTable/>
    <debug>true</debug>
    <out isNull=3D"true"></out>
    <providers>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>imap</protocol>
        <className>com.sun.mail.imap.IMAPStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>imaps</protocol>
        <className>com.sun.mail.imap.IMAPSSLStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
      <javax.mail.Provider>
        <type>
          <type>Transport</type>
        </type>
        <protocol>smtp</protocol>
        <className>com.sun.mail.smtp.SMTPTransport</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
      <javax.mail.Provider>
        <type>
          <type>Transport</type>
        </type>
        <protocol>smtps</protocol>
        <className>com.sun.mail.smtp.SMTPSSLTransport</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>pop3</protocol>
        <className>com.sun.mail.pop3.POP3Store</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>pop3s</protocol>
        <className>com.sun.mail.pop3.POP3SSLStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </providers>
    <providersByProtocol>
      <entry>
        <string>imaps</string>
        <javax.mail.Provider>
          <type>
            <type>Store</type>
          </type>
          <protocol>imaps</protocol>
          <className>com.sun.mail.imap.IMAPSSLStore</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>imap</string>
        <javax.mail.Provider>
          <type>
            <type>Store</type>
          </type>
          <protocol>imap</protocol>
          <className>com.sun.mail.imap.IMAPStore</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>smtps</string>
        <javax.mail.Provider>
          <type>
            <type>Transport</type>
          </type>
          <protocol>smtps</protocol>
          <className>com.sun.mail.smtp.SMTPSSLTransport</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>pop3</string>
        <javax.mail.Provider>
          <type>
            <type>Store</type>
          </type>
          <protocol>pop3</protocol>
          <className>com.sun.mail.pop3.POP3Store</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>pop3s</string>
        <javax.mail.Provider>
          <type>
            <type>Store</type>
          </type>
          <protocol>pop3s</protocol>
          <className>com.sun.mail.pop3.POP3SSLStore</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>smtp</string>
        <javax.mail.Provider>
          <type>
            <type>Transport</type>
          </type>
          <protocol>smtp</protocol>
          <className>com.sun.mail.smtp.SMTPTransport</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
    </providersByProtocol>
    <providersByClassName>
      <entry>
        <string>com.sun.mail.smtp.SMTPSSLTransport</string>
        <javax.mail.Provider>
          <type>
            <type>Transport</type>
          </type>
          <protocol>smtps</protocol>
          <className>com.sun.mail.smtp.SMTPSSLTransport</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>com.sun.mail.smtp.SMTPTransport</string>
        <javax.mail.Provider>
          <type>
            <type>Transport</type>
          </type>
          <protocol>smtp</protocol>
          <className>com.sun.mail.smtp.SMTPTransport</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>com.sun.mail.imap.IMAPSSLStore</string>
        <javax.mail.Provider>
          <type>
            <type>Store</type>
          </type>
          <protocol>imaps</protocol>
          <className>com.sun.mail.imap.IMAPSSLStore</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>com.sun.mail.pop3.POP3SSLStore</string>
        <javax.mail.Provider>
          <type>
            <type>Store</type>
          </type>
          <protocol>pop3s</protocol>
          <className>com.sun.mail.pop3.POP3SSLStore</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>com.sun.mail.imap.IMAPStore</string>
        <javax.mail.Provider>
          <type>
            <type>Store</type>
          </type>
          <protocol>imap</protocol>
          <className>com.sun.mail.imap.IMAPStore</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
      <entry>
        <string>com.sun.mail.pop3.POP3Store</string>
        <javax.mail.Provider>
          <type>
            <type>Store</type>
          </type>
          <protocol>pop3</protocol>
          <className>com.sun.mail.pop3.POP3Store</className>
          <vendor>Sun Microsystems, Inc</vendor>
          <version isNull=3D"true"></version>
        </javax.mail.Provider>
      </entry>
    </providersByClassName>
    <addressMap>
      <property name=3D"rfc822" value=3D"smtp"/>
    </addressMap>
  </session>
</javax.mail.Message></var>
<var name=3D"javax.mail.Session"><javax.mail.Session>
  <props>
    <property name=3D"mail.smtp.port" value=3D"25"/>
    <property name=3D"mail.transport.protocol" value=3D"smtp"/>
    <property name=3D"mail.smtp.host" value=3D"212.32.186.35"/>
  </props>
  <authenticator isNull=3D"true"></authenticator>
  <authTable/>
  <debug>true</debug>
  <out isNull=3D"true"></out>
  <providers>
    <javax.mail.Provider>
      <type>
        <type>Store</type>
      </type>
      <protocol>imap</protocol>
      <className>com.sun.mail.imap.IMAPStore</className>
      <vendor>Sun Microsystems, Inc</vendor>
      <version isNull=3D"true"></version>
    </javax.mail.Provider>
    <javax.mail.Provider>
      <type>
        <type>Store</type>
      </type>
      <protocol>imaps</protocol>
      <className>com.sun.mail.imap.IMAPSSLStore</className>
      <vendor>Sun Microsystems, Inc</vendor>
      <version isNull=3D"true"></version>
    </javax.mail.Provider>
    <javax.mail.Provider>
      <type>
        <type>Transport</type>
      </type>
      <protocol>smtp</protocol>
      <className>com.sun.mail.smtp.SMTPTransport</className>
      <vendor>Sun Microsystems, Inc</vendor>
      <version isNull=3D"true"></version>
    </javax.mail.Provider>
    <javax.mail.Provider>
      <type>
        <type>Transport</type>
      </type>
      <protocol>smtps</protocol>
      <className>com.sun.mail.smtp.SMTPSSLTransport</className>
      <vendor>Sun Microsystems, Inc</vendor>
      <version isNull=3D"true"></version>
    </javax.mail.Provider>
    <javax.mail.Provider>
      <type>
        <type>Store</type>
      </type>
      <protocol>pop3</protocol>
      <className>com.sun.mail.pop3.POP3Store</className>
      <vendor>Sun Microsystems, Inc</vendor>
      <version isNull=3D"true"></version>
    </javax.mail.Provider>
    <javax.mail.Provider>
      <type>
        <type>Store</type>
      </type>
      <protocol>pop3s</protocol>
      <className>com.sun.mail.pop3.POP3SSLStore</className>
      <vendor>Sun Microsystems, Inc</vendor>
      <version isNull=3D"true"></version>
    </javax.mail.Provider>
  </providers>
  <providersByProtocol>
    <entry>
      <string>imaps</string>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>imaps</protocol>
        <className>com.sun.mail.imap.IMAPSSLStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>imap</string>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>imap</protocol>
        <className>com.sun.mail.imap.IMAPStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>smtps</string>
      <javax.mail.Provider>
        <type>
          <type>Transport</type>
        </type>
        <protocol>smtps</protocol>
        <className>com.sun.mail.smtp.SMTPSSLTransport</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>pop3</string>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>pop3</protocol>
        <className>com.sun.mail.pop3.POP3Store</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>pop3s</string>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>pop3s</protocol>
        <className>com.sun.mail.pop3.POP3SSLStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>smtp</string>
      <javax.mail.Provider>
        <type>
          <type>Transport</type>
        </type>
        <protocol>smtp</protocol>
        <className>com.sun.mail.smtp.SMTPTransport</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
  </providersByProtocol>
  <providersByClassName>
    <entry>
      <string>com.sun.mail.smtp.SMTPSSLTransport</string>
      <javax.mail.Provider>
        <type>
          <type>Transport</type>
        </type>
        <protocol>smtps</protocol>
        <className>com.sun.mail.smtp.SMTPSSLTransport</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>com.sun.mail.smtp.SMTPTransport</string>
      <javax.mail.Provider>
        <type>
          <type>Transport</type>
        </type>
        <protocol>smtp</protocol>
        <className>com.sun.mail.smtp.SMTPTransport</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>com.sun.mail.imap.IMAPSSLStore</string>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>imaps</protocol>
        <className>com.sun.mail.imap.IMAPSSLStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>com.sun.mail.pop3.POP3SSLStore</string>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>pop3s</protocol>
        <className>com.sun.mail.pop3.POP3SSLStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>com.sun.mail.imap.IMAPStore</string>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>imap</protocol>
        <className>com.sun.mail.imap.IMAPStore</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
    <entry>
      <string>com.sun.mail.pop3.POP3Store</string>
      <javax.mail.Provider>
        <type>
          <type>Store</type>
        </type>
        <protocol>pop3</protocol>
        <className>com.sun.mail.pop3.POP3Store</className>
        <vendor>Sun Microsystems, Inc</vendor>
        <version isNull=3D"true"></version>
      </javax.mail.Provider>
    </entry>
  </providersByClassName>
  <addressMap>
    <property name=3D"rfc822" value=3D"smtp"/>
  </addressMap>
</javax.mail.Session></var>
</logdata>
</logvo>=20
javax.mail.MessagingException: Could not connect to SMTP host:
212.32.186.35, port: 25;
  nested exception is:
	java.net.ConnectException: Connection refused: connect
	at
com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1227)
	at
com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:322)
	at javax.mail.Service.connect(Service.java:236)
	at javax.mail.Service.connect(Service.java:137)
	at javax.mail.Service.connect(Service.java:86)
	at javax.mail.Transport.send0(Transport.java:150)
	at javax.mail.Transport.send(Transport.java:80)
	at
se.cesp.delivery.common.util.EmailCommunicator.send(EmailCommunicator.jav=
a:1
92)
	at
se.cesp.delivery.impl.OfferWebbEmail.handleDeliveryResult(OfferWebbEmail.=
jav
a:219)
	at
se.cesp.delivery.common.util.DeliveryMonitorInvoker.run(DeliveryMonitorIn=
vok
er.java:95)
	at java.lang.Thread.run(Thread.java:534)

(ERROR, Thread-53, EVENT_LOG) 2005-11-07 09:11:02,093=20
<logvo logid=3D"4585b422785ac9de:1394894:10769c6689d:-7fde"=20
usr=3D"N/A"=20
class=3D"se.cesp.delivery.impl.OfferWebbEmail"=20
method=3D"handleDeliveryResult(DeliveryLogVO)"=20
hostip=3D"212.32.186.130">
<message>
Throwable occured, code: 302010001
</message>
<logdata>
<var name=3D"MessageVO"><MessageVO>
  <parameters class=3D"hashtable">
    <entry>
      <string>URL</string>
      <se.cesp.delivery.common.vo.MessageDataVO>
        <value>http://www.stadspuls.se</value>
        <path isNull=3D"true"></path>
        <componentName>URL</componentName>
      </se.cesp.delivery.common.vo.MessageDataVO>
    </entry>
    <entry>
      <string>Bild</string>
      <se.cesp.delivery.common.vo.MessageDataVO>
        <value>teknikmagasinetpowerball2.jpg</value>
=20
<path>6e5ac004-72e9-4ccf-b809-011fdbf468c7/581b91bd-b142-4c5b-802c-927d33=
62c
0e5/ad6887c5-fcb3-4a52-82ac-25670bd6d0c9.jpg</path>
        <componentName>Bild</componentName>
      </se.cesp.delivery.common.vo.MessageDataVO>
    </entry>
    <entry>
      <string>Rubrik</string>
      <se.cesp.delivery.common.vo.MessageDataVO>
        <value>testa det h=E4r</value>
        <path isNull=3D"true"></path>
        <componentName>Rubrik</componentName>
      </se.cesp.delivery.common.vo.MessageDataVO>
    </entry>
  </parameters>
  <templateId>2D30A9DF-366E-4367-96A5-C87796AA3B03</templateId>
  <companyName>STADSPULS</companyName>
=20
<logotypeUrl>6e5ac004-72e9-4ccf-b809-011fdbf468c7/Logotype/Logotype.jpg</=
log
otypeUrl>
  <interest isNull=3D"true"></interest>
</MessageVO></var>
<var name=3D"emailList"><list>
  <string>rob...@la...</string>
  <string>ha...@cs...</string>
</list></var>
</logdata>
</logvo>=20
se.cesp.delivery.common.util.exception.CespSystemException
	at
se.cesp.delivery.common.util.EmailCommunicator.send(EmailCommunicator.jav=
a:2
01)
	at
se.cesp.delivery.impl.OfferWebbEmail.handleDeliveryResult(OfferWebbEmail.=
jav
a:219)
	at
se.cesp.delivery.common.util.DeliveryMonitorInvoker.run(DeliveryMonitorIn=
vok
er.java:95)
	at java.lang.Thread.run(Thread.java:534)








-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: den 7 november 2005 05:35
To: wra...@li...
Subject: Re: [Wrapper-user] Problem with SMTP on Windows

Hakan,
Could you try putting some debug information around the code trying to=20
send the mail?
I have SMTP mail features in most of the applications I write to notify=20
administrators of
problems and have never had any problems with it. I use the SUN Javamail =

jars.
There are some restrictions about accessing windows network drives and=20
printers
when running as a service, but not about opening arbitrary sockets.
Could you post the error message and stack trace you are getting? It=20
might give me
some ideas.

Cheers,
Leif

H=E5kan Fransson wrote:

>Hi again and thanks for the answer. First i would like to say that
>it's a nice framework, easy to understand and very configurable.
>
>The smtp settings seems to work fine, it's through a regular=20
>property file. E.g mail server and port is from property file and=20
>their properties come out in the stacktrace so it's probably not that.
>I've changed the user on the service to administrator as with console =
but
>it doesn't help. I wonder if it's some security policy in windows but i =

>have no clue.
>/H=E5kan
>
>
>-----Original Message-----
>From: wra...@li...
>[mailto:wra...@li...] On Behalf Of Leif
>Mortenson
>Sent: den 6 november 2005 12:38
>To: wra...@li...
>Subject: Re: [Wrapper-user] Problem with SMTP on Windows
>
>Hakan,
>How are the SMTP settings being configured in your application? There=20
>shouldn't be
>anything about the Wrapper that would prevent you from connecting to=20
>your mail server
>if it is being configured correctly. Try adding the =
wrapper.debug=3Dtrue=20
>property and
>verify that the command line being used to launch the JVM contains all=20
>of the expected
>values.
>A common problem is problems with environment variables. Make sure that =
any
>variables your application needs are defined system wide and not just=20
>for your user.
>
>Cheers,
>Leif
>
>
>H=E5kan Fransson wrote:
>
> =20
>
>>Hi!
>>I=92m just started to use the wrapper to make a Windows service of my =
java
>>application. It works perfectly when
>>i run it as a consle  but when i=92m try to send an email with wrapper =
as a
>>windows service i get:
>>
>>javax.mail.MessagingException: Could not connect to SMTP host:
>>mail.steencon.se, port: 25;
>> nested exception is:
>>	java.net.ConnectException: Connection refused: connect
>>	at
>>com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1227)
>>	at
>>com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:322)=

>>	at javax.mail.Service.connect(Service.java:236)
>>	at javax.mail.Service.connect(Service.java:137)
>>	at javax.mail.Service.connect(Service.java:86)
>>	at javax.mail.Transport.send0(Transport.java:150)
>>	at javax.mail.Transport.send(Transport.java:80)
>>	at
>>se.cesp.delivery.common.util.EmailCommunicator.send(EmailCommunicator.j=
ava
:
>>   =20
>>
>1
> =20
>
>>88)
>>	at
>>se.cesp.delivery.impl.OfferWebbEmail.execute(OfferWebbEmail.java:95)
>>	at
>>se.cesp.delivery.common.util.DeliveryInvoker.run(DeliveryInvoker.java:8=
1)
>>	at java.lang.Thread.run(Thread.java:534)
>>
>>It doesn=92t matter i run the service with system account or
administrator(as
>>with console), it=92s the same
>>result.
>>The java application also uses FTP and it works fine in both ways.
>>Any ideas?
>>
>>Thanks in advance H=E5kan
>>
>>----------------------------------------------------------------
>>H=E5kan Fransson	Phone: +46(0)90 - 786 74 93
>>Ladokenheten	Fax: +46(0)90 - 786 69 91
>>Ume=E5 University	www: www.umu.se/ladokenheten
>>SE - 90187 Ume=E5
>>-------------------------------------------------------------
>>=20
>>   =20
>>



-------------------------------------------------------
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] 64 bit Solaris sparc build

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

Nick,
    Thank you for the offer.  I added you my list of "helpers" and will 
ask you to help
out for the next release.    You don't happen to have access to a 
sparc-32 machine
do you?   I have always built those in the past, but no longer have 
access to one.

    Also, can you tell me what the ${os.name} and ${os.arch} Ant 
variables return
on Sparc 64?   On most platforms, there doesn't appear to be a way to 
differentiate
between 64 and 32 bit platforms from within Ant....  I will not be able 
to completely
automate the build without figuring something out.

    Are you able to check out the source from CVS?  If so I would 
appreciate you
giving the latest source a go.   There have been a large number of 
changes since
3.1.2.

Cheers,
Leif

nic...@uk... wrote:

>Ok cool.
>I will give it a spin.
>
>Leif, do you want to host a sparc-64 build of JSW?
>
>-Nick
>  
>

Re: [Wrapper-user] tomcat 5.5

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

John,
    It had been a while since I tried out the newer Tomcat versions so I 
gave it a try with
the latest and greatest Tomcat 5.5.12.   Following the directions on the 
Wrapper site,
it worked perfectly.  There were a couple differences in the actual 
configuration values
as the new version appears to expect a couple more system properties.  
But the
instructions lead the user to the correct config file.

    I went ahead and attached it to this mail.

    It looks like Tomcat 5.5 contains its own native binary capable of 
installing and
running Tomcat as a service.   If that is the only feature of the 
Wrapper that you are
looking for then it should meet your needs.   The Wrapper does go much 
farther
however, particularly the error detection and recovery features.

Cheers,
Leif

John Larsen wrote:

>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] Permissions of generated files

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

Juergen
    Thanks for suggesting this.  It has been implemented for the 3.2.0 
release and is
in CVS.

    From the release notes:

* Add the ability to specify integer property values in base 8 or 16 in
  addition to base 10.  Base 8 values start with a '0' and base 16 values
  start with a '0x'.
* Make it possible to set the umask on all files created by the Wrapper
  as well as the default umask of files created by the JVM.  Added new
  wrapper.umask, wrapper.java.umask, wrapper.pidfile.umask,
  wrapper.java.pidfile.umask, wrapper.java.idfile.umask,
  wrapper.statusfile.umask, wrapper.java.statusfile.umask,
  wrapper.anchorfile.umask, and wrapper.logfile.umask properties.

    All of the detailed umask properties default to value of wrapper.umask.

Cheers,
Leif

Juergen Hermann wrote:

>Hi, we have set the umask to 027 before running 
>the JSW in order to have the JVM generate no 
>world readable files.
>
>The problem with this is that the files the JSW 
>generates (log, pid-file, etc.) also use that 
>umask, but we'd like to have the log-files 
>world readable.
>
>So it would be nice if you were able to set the 
>umask fpr the JVM process (and only for that) 
>in wrapper.conf, and have the wrapper itself 
>use the umask it is started with. Don't know if 
>we'll write a patch for this, but I wanted to 
>share the use-case anyway.
>
>
>
>Ciao, Jürgen
>  
>

Re: [Wrapper-user] Problem with SMTP on Windows

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

Hakan,
Could you try putting some debug information around the code trying to 
send the mail?
I have SMTP mail features in most of the applications I write to notify 
administrators of
problems and have never had any problems with it. I use the SUN Javamail 
jars.
There are some restrictions about accessing windows network drives and 
printers
when running as a service, but not about opening arbitrary sockets.
Could you post the error message and stack trace you are getting? It 
might give me
some ideas.

Cheers,
Leif

Håkan Fransson wrote:

>Hi again and thanks for the answer. First i would like to say that
>it's a nice framework, easy to understand and very configurable.
>
>The smtp settings seems to work fine, it's through a regular 
>property file. E.g mail server and port is from property file and 
>their properties come out in the stacktrace so it's probably not that.
>I've changed the user on the service to administrator as with console but
>it doesn't help. I wonder if it's some security policy in windows but i 
>have no clue.
>/Håkan
>
>
>-----Original Message-----
>From: wra...@li...
>[mailto:wra...@li...] On Behalf Of Leif
>Mortenson
>Sent: den 6 november 2005 12:38
>To: wra...@li...
>Subject: Re: [Wrapper-user] Problem with SMTP on Windows
>
>Hakan,
>How are the SMTP settings being configured in your application? There 
>shouldn't be
>anything about the Wrapper that would prevent you from connecting to 
>your mail server
>if it is being configured correctly. Try adding the wrapper.debug=true 
>property and
>verify that the command line being used to launch the JVM contains all 
>of the expected
>values.
>A common problem is problems with environment variables. Make sure that any
>variables your application needs are defined system wide and not just 
>for your user.
>
>Cheers,
>Leif
>
>
>Håkan Fransson wrote:
>
>  
>
>>Hi!
>>I’m just started to use the wrapper to make a Windows service of my java
>>application. It works perfectly when
>>i run it as a consle  but when i’m try to send an email with wrapper as a
>>windows service i get:
>>
>>javax.mail.MessagingException: Could not connect to SMTP host:
>>mail.steencon.se, port: 25;
>> nested exception is:
>>	java.net.ConnectException: Connection refused: connect
>>	at
>>com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1227)
>>	at
>>com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:322)
>>	at javax.mail.Service.connect(Service.java:236)
>>	at javax.mail.Service.connect(Service.java:137)
>>	at javax.mail.Service.connect(Service.java:86)
>>	at javax.mail.Transport.send0(Transport.java:150)
>>	at javax.mail.Transport.send(Transport.java:80)
>>	at
>>se.cesp.delivery.common.util.EmailCommunicator.send(EmailCommunicator.java:
>>    
>>
>1
>  
>
>>88)
>>	at
>>se.cesp.delivery.impl.OfferWebbEmail.execute(OfferWebbEmail.java:95)
>>	at
>>se.cesp.delivery.common.util.DeliveryInvoker.run(DeliveryInvoker.java:81)
>>	at java.lang.Thread.run(Thread.java:534)
>>
>>It doesn’t matter i run the service with system account or administrator(as
>>with console), it’s the same
>>result.
>>The java application also uses FTP and it works fine in both ways.
>>Any ideas?
>>
>>Thanks in advance Håkan
>>
>>----------------------------------------------------------------
>>Håkan Fransson	Phone: +46(0)90 - 786 74 93
>>Ladokenheten	Fax: +46(0)90 - 786 69 91
>>Umeå University	www: www.umu.se/ladokenheten
>>SE - 90187 Umeå
>>-------------------------------------------------------------
>> 
>>    
>>

RE: [Wrapper-user] Problem with SMTP on Windows

[<hak...@la...>]

Hi again and thanks for the answer. First i would like to say that
it's a nice framework, easy to understand and very configurable.

The smtp settings seems to work fine, it's through a regular=20
property file. E.g mail server and port is from property file and=20
their properties come out in the stacktrace so it's probably not that.
I've changed the user on the service to administrator as with console =
but
it doesn't help. I wonder if it's some security policy in windows but i=20
have no clue.
/H=E5kan


-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: den 6 november 2005 12:38
To: wra...@li...
Subject: Re: [Wrapper-user] Problem with SMTP on Windows

Hakan,
How are the SMTP settings being configured in your application? There=20
shouldn't be
anything about the Wrapper that would prevent you from connecting to=20
your mail server
if it is being configured correctly. Try adding the wrapper.debug=3Dtrue =

property and
verify that the command line being used to launch the JVM contains all=20
of the expected
values.
A common problem is problems with environment variables. Make sure that =
any
variables your application needs are defined system wide and not just=20
for your user.

Cheers,
Leif


H=E5kan Fransson wrote:

>Hi!
>I=92m just started to use the wrapper to make a Windows service of my =
java
>application. It works perfectly when
>i run it as a consle  but when i=92m try to send an email with wrapper =
as a
>windows service i get:
>
>javax.mail.MessagingException: Could not connect to SMTP host:
>mail.steencon.se, port: 25;
>  nested exception is:
>	java.net.ConnectException: Connection refused: connect
>	at
>com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1227)
>	at
>com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:322)
>	at javax.mail.Service.connect(Service.java:236)
>	at javax.mail.Service.connect(Service.java:137)
>	at javax.mail.Service.connect(Service.java:86)
>	at javax.mail.Transport.send0(Transport.java:150)
>	at javax.mail.Transport.send(Transport.java:80)
>	at
>se.cesp.delivery.common.util.EmailCommunicator.send(EmailCommunicator.ja=
va:
1
>88)
>	at
>se.cesp.delivery.impl.OfferWebbEmail.execute(OfferWebbEmail.java:95)
>	at
>se.cesp.delivery.common.util.DeliveryInvoker.run(DeliveryInvoker.java:81=
)
>	at java.lang.Thread.run(Thread.java:534)
>
>It doesn=92t matter i run the service with system account or =
administrator(as
>with console), it=92s the same
>result.
>The java application also uses FTP and it works fine in both ways.
>Any ideas?
>
>Thanks in advance H=E5kan
>
>----------------------------------------------------------------
>H=E5kan Fransson	Phone: +46(0)90 - 786 74 93
>Ladokenheten	Fax: +46(0)90 - 786 69 91
>Ume=E5 University	www: www.umu.se/ladokenheten
>SE - 90187 Ume=E5
>-------------------------------------------------------------
> =20
>



-------------------------------------------------------
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] Problem with SMTP on Windows

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

Hakan,
How are the SMTP settings being configured in your application? There 
shouldn't be
anything about the Wrapper that would prevent you from connecting to 
your mail server
if it is being configured correctly. Try adding the wrapper.debug=true 
property and
verify that the command line being used to launch the JVM contains all 
of the expected
values.
A common problem is problems with environment variables. Make sure that any
variables your application needs are defined system wide and not just 
for your user.

Cheers,
Leif


Håkan Fransson wrote:

>Hi!
>I’m just started to use the wrapper to make a Windows service of my java
>application. It works perfectly when
>i run it as a consle  but when i’m try to send an email with wrapper as a
>windows service i get:
>
>javax.mail.MessagingException: Could not connect to SMTP host:
>mail.steencon.se, port: 25;
>  nested exception is:
>	java.net.ConnectException: Connection refused: connect
>	at
>com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1227)
>	at
>com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:322)
>	at javax.mail.Service.connect(Service.java:236)
>	at javax.mail.Service.connect(Service.java:137)
>	at javax.mail.Service.connect(Service.java:86)
>	at javax.mail.Transport.send0(Transport.java:150)
>	at javax.mail.Transport.send(Transport.java:80)
>	at
>se.cesp.delivery.common.util.EmailCommunicator.send(EmailCommunicator.java:1
>88)
>	at
>se.cesp.delivery.impl.OfferWebbEmail.execute(OfferWebbEmail.java:95)
>	at
>se.cesp.delivery.common.util.DeliveryInvoker.run(DeliveryInvoker.java:81)
>	at java.lang.Thread.run(Thread.java:534)
>
>It doesn’t matter i run the service with system account or administrator(as
>with console), it’s the same
>result.
>The java application also uses FTP and it works fine in both ways.
>Any ideas?
>
>Thanks in advance Håkan
>
>----------------------------------------------------------------
>Håkan Fransson	Phone: +46(0)90 - 786 74 93
>Ladokenheten	Fax: +46(0)90 - 786 69 91
>Umeå University	www: www.umu.se/ladokenheten
>SE - 90187 Umeå
>-------------------------------------------------------------
>  
>

[Wrapper-user] Problem with SMTP on Windows

[<hak...@la...>]

Hi!
I=92m just started to use the wrapper to make a Windows service of my =
java
application. It works perfectly when
i run it as a consle  but when i=92m try to send an email with wrapper =
as a
windows service i get:

javax.mail.MessagingException: Could not connect to SMTP host:
mail.steencon.se, port: 25;
  nested exception is:
	java.net.ConnectException: Connection refused: connect
	at
com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1227)
	at
com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:322)
	at javax.mail.Service.connect(Service.java:236)
	at javax.mail.Service.connect(Service.java:137)
	at javax.mail.Service.connect(Service.java:86)
	at javax.mail.Transport.send0(Transport.java:150)
	at javax.mail.Transport.send(Transport.java:80)
	at
se.cesp.delivery.common.util.EmailCommunicator.send(EmailCommunicator.jav=
a:1
88)
	at
se.cesp.delivery.impl.OfferWebbEmail.execute(OfferWebbEmail.java:95)
	at
se.cesp.delivery.common.util.DeliveryInvoker.run(DeliveryInvoker.java:81)=

	at java.lang.Thread.run(Thread.java:534)

It doesn=92t matter i run the service with system account or =
administrator(as
with console), it=92s the same
result.
The java application also uses FTP and it works fine in both ways.
Any ideas?

Thanks in advance H=E5kan

----------------------------------------------------------------
H=E5kan Fransson	Phone: +46(0)90 - 786=A074 93
Ladokenheten	Fax: +46(0)90 - 786 69 91
Ume=E5 University	www: www.umu.se/ladokenheten
SE - 90187 Ume=E5
-------------------------------------------------------------

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

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

Leif Mortenson wrote:

> Richard,
>    I'll give this some more thought, but for now take a look at the 
> -Xrs Java parameter.

We currently use the -Xrs parameter on Windows.

> I think it will tell the JVM to ignore the logouts...  It has some 
> other problems when used
> for the JVM run by the Wrapper:
> http://wrapper.tanukisoftware.org/doc/english/faq.html#3
>
>    Also, you are correct.  The Wrapper can not handle more than one 
> JVM at this time.
> Be aware that by launching a child JVM, the Wrapper will not be able 
> to manage it.  If
> the top level JVM crashes and is restarted by the Wrapper, the JVM 
> that you are
> spawning could become a zombie process.
>
>    What are the settings that you are needing to change that require 
> you to launch a new
> JVM?  3.2.0 makes this easier, but what about dynamically creating a 
> second
> wrapper.conf file then using that to start a second Wrapper as a 
> second service?
> Then they would both be managed by the Wrapper directly?

We sometimes (based upon property values) load code coverage, debugging or
memory leak detection native libraries and code. We also play with various
garbage collection parameters.

To start and stop the Ant process in the conf file I have:

wrapper.app.parameter.1=org.apache.tools.ant.Main
wrapper.app.parameter.2=3
wrapper.app.parameter.3=-f
wrapper.app.parameter.4=../conf/cs.xml
wrapper.app.parameter.5=start
wrapper.app.parameter.6=org.apache.tools.ant.Main
wrapper.app.parameter.7=true
wrapper.app.parameter.8=3
wrapper.app.parameter.9=-f
wrapper.app.parameter.10=../conf/cs.xml
wrapper.app.parameter.11=stop

(cs.xml being the Ant file).  Each JBoss process always uses the same 
conf file
(except the name of the Ant file will change).
We then use Ant like a scripting language allowing us
to do a lot of dynamic tailoring and monitoring.

Dynamically creating a second conf file and then running a second 
Wrapper which
starts the JBoss process is interesting but might add more complexity for
customer IT, additional services and their meaning, etc. - but still an 
interesting
idea.

Currently, the Ant task when started by the wrapper will wait until the 
JBoss
process ends before it ends - so if the JBoss process dies for any 
reason - other
than having the user tell the wrapper to kill it (via the Ant task) - 
the the wrapper will
restart the Ant task. So, that part does work: automatic restart of 
application error.

Richard

>
> Cheers,
> Leif
>
> Richard Emberson wrote:
>
>> Lief,
>>
>> I think I partially know what the problem is and I'd like your advice 
>> on the solution
>> I am proposing.
>>
>> First, the way we use the wrapper and java process is, no doubt, not 
>> the norm.
>> The wrapper launches a Java Ant process. This Ant process then does a 
>> bunch
>> of checks and startup activities. Then the Ant task executes a 
>> "parallel" Ant task,
>> two different Ant threads within the running Ant process.
>>
>> The first thread calls the Ant "java" task launching JBoss. JBoss is 
>> launched in
>> "fork" mode, a subprocess is forked. This is required since there are 
>> a bunch of
>> arguments specific to the JBoss process that have to be passed to the 
>> JBoss process
>> and if JBoss was not forked, then only the arguments passed to the 
>> original Ant
>> process could be given to the JBoss process.
>> The second thread then monitors the log files created by the JBoss 
>> process, making
>> sure JBoss starts ok, dropping ear files after JBoss core has started 
>> and ensuring
>> that our application started ok.
>>
>> The JBoss appserver has registered as a JMX page the
>> org.tanukisoftware.wrapper.jmx.WrapperManager class.
>> If as an argument to the JBoss process I pass in the property 
>> "wrapper.debug=true"
>> then when I go to the JMX page for the first time I can see in the 
>> log that the
>> WrapperManager is loaded (its not loaded until the JMX page is hit).
>>
>> Now, the WrapperManger running in the JBoss process does NOT have a 
>> listener
>> registered and thats why the WRAPPER_CTRL_LOGOFF_EVENT is not
>> handled but rather the JBoss process calls System.exit(status).
>> This does not explain why on all of the other Windows systems running 
>> our
>> application with the exact same setup do not die when folks logout, 
>> but that
>> might be something how this particular Window system is configured.
>>
>> I could pass into the JBoss process the various wrapper properties so 
>> that when
>> the WrapperManager class is intialized it tries to communicate with the
>> wrapper process. The properties are available in the Ant task and can 
>> be passed
>> to the JBoss as Java command line arguments (wrapper.key, 
>> wrapper.version,
>> wrapper.native_library and wrapper.port). I suspect that this will 
>> not work - the
>> wrapper is not designed to communicate with more than one Java process.
>> I'm I correct that this will not work?
>>
>> Anyway, here here is my proposed solution.
>> After the Ant task knows that our application is up and running, it 
>> does an http-get
>> on the JMX console for the WrapperManager JMX page thus loading the
>> WrapperManager. The WrapperManager is not given the wrapper.key so
>> it does not try to communicate with the wrapper process. But, a 
>> Listener is
>> regisered with the WrapperManager so that the WRAPPER_CTRL_LOGOFF_EVENT
>> is ignored.
>>
>> What do you think?
>>
>> Richard
>>
>>
>> Leif Mortenson wrote:
>>
>>> Richard,
>>>    I am pretty sure the logout events are only generated by the 
>>> local user who is
>>> physically logged into the machine.  I don't think it works the same 
>>> for remote
>>> terminals.  Don't have a remote accessible system immediately 
>>> available to test
>>> with however.
>>>
>>> Cheers,
>>> Leif
>>>
>>> Richard Emberson wrote:
>>>
>>>>
>>>> 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
>


-- 
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,
    I'll give this some more thought, but for now take a look at the 
-Xrs Java parameter.
I think it will tell the JVM to ignore the logouts...  It has some other 
problems when used
for the JVM run by the Wrapper:
http://wrapper.tanukisoftware.org/doc/english/faq.html#3

    Also, you are correct.  The Wrapper can not handle more than one JVM 
at this time.
Be aware that by launching a child JVM, the Wrapper will not be able to 
manage it.  If
the top level JVM crashes and is restarted by the Wrapper, the JVM that 
you are
spawning could become a zombie process.

    What are the settings that you are needing to change that require 
you to launch a new
JVM?  3.2.0 makes this easier, but what about dynamically creating a second
wrapper.conf file then using that to start a second Wrapper as a second 
service?
Then they would both be managed by the Wrapper directly?

Cheers,
Leif

Richard Emberson wrote:

> Lief,
>
> I think I partially know what the problem is and I'd like your advice 
> on the solution
> I am proposing.
>
> First, the way we use the wrapper and java process is, no doubt, not 
> the norm.
> The wrapper launches a Java Ant process. This Ant process then does a 
> bunch
> of checks and startup activities. Then the Ant task executes a 
> "parallel" Ant task,
> two different Ant threads within the running Ant process.
>
> The first thread calls the Ant "java" task launching JBoss. JBoss is 
> launched in
> "fork" mode, a subprocess is forked. This is required since there are 
> a bunch of
> arguments specific to the JBoss process that have to be passed to the 
> JBoss process
> and if JBoss was not forked, then only the arguments passed to the 
> original Ant
> process could be given to the JBoss process.
> The second thread then monitors the log files created by the JBoss 
> process, making
> sure JBoss starts ok, dropping ear files after JBoss core has started 
> and ensuring
> that our application started ok.
>
> The JBoss appserver has registered as a JMX page the
> org.tanukisoftware.wrapper.jmx.WrapperManager class.
> If as an argument to the JBoss process I pass in the property 
> "wrapper.debug=true"
> then when I go to the JMX page for the first time I can see in the log 
> that the
> WrapperManager is loaded (its not loaded until the JMX page is hit).
>
> Now, the WrapperManger running in the JBoss process does NOT have a 
> listener
> registered and thats why the WRAPPER_CTRL_LOGOFF_EVENT is not
> handled but rather the JBoss process calls System.exit(status).
> This does not explain why on all of the other Windows systems running our
> application with the exact same setup do not die when folks logout, 
> but that
> might be something how this particular Window system is configured.
>
> I could pass into the JBoss process the various wrapper properties so 
> that when
> the WrapperManager class is intialized it tries to communicate with the
> wrapper process. The properties are available in the Ant task and can 
> be passed
> to the JBoss as Java command line arguments (wrapper.key, 
> wrapper.version,
> wrapper.native_library and wrapper.port). I suspect that this will not 
> work - the
> wrapper is not designed to communicate with more than one Java process.
> I'm I correct that this will not work?
>
> Anyway, here here is my proposed solution.
> After the Ant task knows that our application is up and running, it 
> does an http-get
> on the JMX console for the WrapperManager JMX page thus loading the
> WrapperManager. The WrapperManager is not given the wrapper.key so
> it does not try to communicate with the wrapper process. But, a 
> Listener is
> regisered with the WrapperManager so that the WRAPPER_CTRL_LOGOFF_EVENT
> is ignored.
>
> What do you think?
>
> Richard
>
>
> Leif Mortenson wrote:
>
>> Richard,
>>    I am pretty sure the logout events are only generated by the local 
>> user who is
>> physically logged into the machine.  I don't think it works the same 
>> for remote
>> terminals.  Don't have a remote accessible system immediately 
>> available to test
>> with however.
>>
>> Cheers,
>> Leif
>>
>> Richard Emberson wrote:
>>
>>>
>>> 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
>>>>>>>

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

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

Lief,

I think I partially know what the problem is and I'd like your advice on 
the solution
I am proposing.

First, the way we use the wrapper and java process is, no doubt, not the 
norm.
The wrapper launches a Java Ant process. This Ant process then does a bunch
of checks and startup activities. Then the Ant task executes a 
"parallel" Ant task,
two different Ant threads within the running Ant process.

The first thread calls the Ant "java" task launching JBoss. JBoss is 
launched in
"fork" mode, a subprocess is forked. This is required since there are a 
bunch of
arguments specific to the JBoss process that have to be passed to the 
JBoss process
and if JBoss was not forked, then only the arguments passed to the 
original Ant
process could be given to the JBoss process. 

The second thread then monitors the log files created by the JBoss 
process, making
sure JBoss starts ok, dropping ear files after JBoss core has started 
and ensuring
that our application started ok.

The JBoss appserver has registered as a JMX page the
org.tanukisoftware.wrapper.jmx.WrapperManager class.
If as an argument to the JBoss process I pass in the property 
"wrapper.debug=true"
then when I go to the JMX page for the first time I can see in the log 
that the
WrapperManager is loaded (its not loaded until the JMX page is hit).

Now, the WrapperManger running in the JBoss process does NOT have a listener
registered and thats why the WRAPPER_CTRL_LOGOFF_EVENT is not
handled but rather the JBoss process calls System.exit(status).
This does not explain why on all of the other Windows systems running our
application with the exact same setup do not die when folks logout, but that
might be something how this particular Window system is configured.

I could pass into the JBoss process the various wrapper properties so 
that when
the WrapperManager class is intialized it tries to communicate with the
wrapper process. The properties are available in the Ant task and can be 
passed
to the JBoss as Java command line arguments (wrapper.key, wrapper.version,
wrapper.native_library and wrapper.port). I suspect that this will not 
work - the
wrapper is not designed to communicate with more than one Java process.
I'm I correct that this will not work?

Anyway, here here is my proposed solution.
After the Ant task knows that our application is up and running, it does 
an http-get
on the JMX console for the WrapperManager JMX page thus loading the
WrapperManager. The WrapperManager is not given the wrapper.key so
it does not try to communicate with the wrapper process. But, a Listener is
regisered with the WrapperManager so that the WRAPPER_CTRL_LOGOFF_EVENT
is ignored.

What do you think?

Richard


Leif Mortenson wrote:

> Richard,
>    I am pretty sure the logout events are only generated by the local 
> user who is
> physically logged into the machine.  I don't think it works the same 
> for remote
> terminals.  Don't have a remote accessible system immediately 
> available to test
> with however.
>
> Cheers,
> Leif
>
> Richard Emberson wrote:
>
>>
>> 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
>>>
>>
>>
>
>
>
> -------------------------------------------------------
> 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,
I am pretty sure from what I saw that the JVM exit is being initiated by a
System.exit call.  Is there nothing in the application that might 
possibly be
doing so?  It strange that it is happening right when the user logs out
however.

Current versions of the Wrapper do not have the ability to notify the user
when it goes down.  But I am working on a way to make it possible to
execute arbitrary external programs in the event of actions like JVM exits,
restarts, starts etc.   It will be in a near term future version.

Cheers,
Leif

Richard Emberson wrote:

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

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

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

Richard,
    I am pretty sure the logout events are only generated by the local 
user who is
physically logged into the machine.  I don't think it works the same for 
remote
terminals.  Don't have a remote accessible system immediately available 
to test
with however.

Cheers,
Leif

Richard Emberson wrote:

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

[Wrapper-user] Permissions of generated files

[Juergen H. <jh...@we...>]

Hi,=20we=20have=20set=20the=20umask=20to=20027=20before=20running=20
the=20JSW=20in=20order=20to=20have=20the=20JVM=20generate=20no=20
world=20readable=20files.

The=20problem=20with=20this=20is=20that=20the=20files=20the=20JSW=20
generates=20(log,=20pid-file,=20etc.)=20also=20use=20that=20
umask,=20but=20we'd=20like=20to=20have=20the=20log-files=20
world=20readable.

So=20it=20would=20be=20nice=20if=20you=20were=20able=20to=20set=20the=20
umask=20fpr=20the=20JVM=20process=20(and=20only=20for=20that)=20
in=20wrapper.conf,=20and=20have=20the=20wrapper=20itself=20
use=20the=20umask=20it=20is=20started=20with.=20Don't=20know=20if=20
we'll=20write=20a=20patch=20for=20this,=20but=20I=20wanted=20to=20
share=20the=20use-case=20anyway.



Ciao,=20J=FCrgen