Re: [Wrapper-user] Wrapper stopping abruptly

[Sean S. <sea...@gm...>]

Leif,

Thanks for taking the time to look at the attachment.    My main
method did little else then check for a connection and return a
recordset.  I am now adding a thread that will continuously check the
db on an ongoing basis.  Everything seems to be working well with the
new structure and the wrapper is performing beautifully.

Hopefully the install as a service will go on smoothly.

Thanks,

Sean

On Thu, 22 Jul 2004 22:51:55 +0900, Leif Mortenson
<le...@ta...> wrote:
> Sean,
> Thanks for the log. As I thought, your application is exiting because
> all of its
> non-daemon threads have completed:
> INFO | jvm 1 | 2004/07/22 08:34:31 | All non-daemon threads have
> stopped. Exiting.
> 
> Your main method completes almost instantly about 3 seconds earlier. I
> have no way
> of knowing what your main method does. Make sure that at least one
> thread that it
> spawns off is a non daemon thread which does not complete until the
> application is
> ready to shutdown.
> 
> The program should also exit when running standalone as the JVM has the same
> logic to decide when to shutdown the JVM.
> 
> 
> 
> Cheers,
> Leif
> 
> Sean Scott wrote:
> 
> >Leif,
> >
> >Here is the attachment of the log file you requested with debugging turned on.
> >
> >Let me know if the exit was an expected result or not.
> >
> >BTW the java application being wrapper had done its job correctly.  I
> >just wanted to understand a little better how the wrapper determines
> >whether it should terminate itself or not.
> >
> >On Thu, 22 Jul 2004 08:54:15 +0900, Leif Mortenson
> ><le...@ta...> wrote:
> >
> >
> >>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
>