Jay,
The Wrapper will exit if all non-daemon threads have completed. This is
how standalone Java works as well.
Could you please set the wrapper.debug=true property and then reply with
the resulting wrapper.log attached. I only need to see a single Wrapper
invocation so delete the old wrapper.log file first. The log should
allow me to say what your exact problem is.
Cheers,
Leif
Jay...@sc... wrote:
> Hi,
>
> I'm playing around with the service wrapper and trying to get an example
> running using integration method 3. I'm running on the Mac OS X.
>
> Everything appears to work. The service starts up when I use the start
> script (sh.script.ln) except that after a few seconds the infrastructure
> appears to call a stop on my service.
>
> Does anyone know the reasons why the stop would be called? I've
> returned null from my start method. I spun up my logic in a thread
> although I did the thread start in a wierd way. (what if the thread
> exited (that's not necessarily happening but I'm trying to learn)?).
>
> My service is a very simple loop where I'm just printing a message to
> std out every second.
>
> Thanks for any help!
>
|
