|
From: Leif M. <le...@ta...> - 2002-09-27 13:17:35
|
Ralf, The wrapper is designed to exit cleanly when all non-daemon threads have quit. Most likely, your application is launching one or more threads with their daemon flag set and then all other threads are exiting. Daemon threads are designed to be running in the background until the JVM is ready to shut down. They are designed so that your application does not need to worry about shutting them all down before the JVM will exit. The Swing event handler thread is an example of a daemon thread. Running java without the wrapper should behave in the same way. That is what the following line is telling you. jvm 1 | All non-daemon threads have stopped. Exiting. Is this an application you wrote yourself? How does it behave when not using the Wrapper? Leif Ralf weber wrote: >i use the WrapperSimpleApp for my application but after the >main method completed the wrapper stopped, can you maybe tell >me what bullshit i done. i have no idea, here is a screenshot. > >ciao, ralf > >jvm 1 | WrapperSimpleApp: main method completed >wrapperp | sent 6 bytes >jvm 1 | Received a packet 103 : ping >jvm 1 | Send a packet 103 : ok >jvm 1 | All non-daemon threads have stopped. Exiting. >jvm 1 | Send a packet 101 : 0 >wrapperp | read a packet 103 : ok >wrapper | Got ping response from JVM >wrapperp | read a packet 101 : 0 >wrapper | JVM requested a shutdown. (0) >wrapper | wrapperStopProcess(0) called. >wrapper | Sending stop signal to JVM >wrapperp | sent 2 bytes >jvm 1 | Thread, Wrapper-Connection, handling the shutdown >process. >jvm 1 | calling listener.stop() >jvm 1 | WrapperSimpleApp: stop(0) >jvm 1 | returned from listener.stop() >jvm 1 | Send a packet 107 : 0 >jvm 1 | Closing socket. >wrapperp | read a packet 107 : 0 >wrapper | JVM signalled that it was stopped. >wrapperp | socket read no code (closed?). >jvm 1 | calling System.exit(0) >wrapper | JVM exited normally. >wrapper | <-- Wrapper Stopped > > > |