Re: [Wrapper-user] Tomcat starts and shuts down in the same few second

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

Andreas,
Another user had problems a while back with Tomcat 5.0.27.   It appears 
that Tomcat changed
its startup scripts a bit so the integration instructions on the Wrapper 
site are not quite correct.
https://sourceforge.net/tracker/index.php?func=detail&aid=998932&group_id=39428&atid=425188

Your output does not look quite the same however, so I'm not sure it is 
the same problem.
In your case, the Wrapper is shutting down because all non-daemon 
threads are shut down.
This means that the Tomcat application itself has completed.

Could you post your wrapper.conf file, along with the full contents of 
your wrapper.log file
for a single run, with wrapper.debug=true set.   I may have some ideas 
after seeing that.

Cheers,
Leif

Andreas Kapp wrote:

>Hello everybody
>
>I'm a new user of wrapper. Currently I observed a strange behavior
>using wrapper 3.1.1 with tomcat 5.0.28.
>
>If I start tomcat with catalina.sh everything works fine.
>
>But when I start Tomcat with wrapper in console mode, Tomcat starts up
>and shuts down in the same moment. I set the logging to debug. For me
>there is no sign of an error or exception shown.
>
>This is the critical part of the log:
>
>jvm 1    | Oct 8, 2004 2:22:14 PM org.apache.jk.server.JkMain start
>jvm 1    | INFO: Jk running ID=0 time=6/655
>config=/usr/local/tomcat5/conf/jk2.properties
>jvm 1    | Oct 8, 2004 2:22:14 PM org.apache.catalina.startup.Catalina start
>jvm 1    | INFO: Server startup in 31411 ms
>jvm 1    | WrapperStartStopApp: start main method completed
>wrapperp | send a packet PING : ping
>jvm 1    | Received a packet PING : ping
>jvm 1    | Send a packet PING : ok
>jvm 1    | All non-daemon threads have stopped.  Exiting.
>jvm 1    | WrapperManager.stop(0) called by thread: Wrapper-Connection
>jvm 1    | Send a packet STOP : 0
>wrapperp | read a packet PING : ok
>wrapper  | Got ping response from JVM
>wrapperp | read a packet STOP : 0
>wrapper  | JVM requested a shutdown. (0)
>wrapper  | wrapperStopProcess(0) called.
>wrapper  | Sending stop signal to JVM
>wrapperp | send a packet STOP : NULL
>jvm 1    | Thread, Wrapper-Connection, handling the shutdown process.
>jvm 1    | calling listener.stop()
>jvm 1    | WrapperStartStopApp: stop(0)
>jvm 1    | WrapperStartStopApp: invoking stop main method
>jvm 1    | Oct 8, 2004 2:22:16 PM org.apache.catalina.core.StandardService stop
>jvm 1    | INFO: Stopping service Tomcat-Standalone
>
>Has somebody an idea what the reason could be for this strange behavior?
>
>Thanks a lot for your comments.
>
>Andreas
>
>
>  
>