|
From: Leif M. <le...@ta...> - 2004-07-21 23:55:27
|
Sean,
The Wrapper is designed to use basically the same logic as the JVM
to decide when
to exit. Once all non-daemon threads have terminated, the program is
determined to
have run to completion.
There are other reasons why the application could be exiting. I
would need to see the
debug output of the Wrapper to determine exactly why your application is
exiting.
Set the wrapper.debug=true property in your wrapper.conf file and rerun
it. Then post
back by attaching the wrapper.log for a single run of the JVM. (Attach
the file rather than
including it in the body of the message to avoid any reformatting of the
file)
Cheers,
Leif
Sean Scott wrote:
>Hi,
>
>Just wanted to know if it was common for the wrapper to stop abruply.
>I am currently using integration method 1. When i test my java applet
>using the command console, everything works fine, it goes through the
>apprpriate steps and outputs to the command. However after a second
>or two after the Java program is done doing its task the wrapper will
>stop itself.
>
>Right now my java program opens a connection to a DB, and retrieves some rows.
>
>Wanted to know if this was expected behavior.
>
>The goal is to have a webservice that will continously monitor a DB
>table every n seconds.
>
>Sean
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by BEA Weblogic Workshop
>FREE Java Enterprise J2EE developer tools!
>Get your free copy of BEA WebLogic Workshop 8.1 today.
>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
|