Re: [Wrapper-user] Service Stops with error 143

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

Robert,
Could you please post the last 30 seconds or so of your wrapper.log?
It should provide a little more information about where this exit code
originated.

Are you by any chance running the javaw.exe version of java rather
than java.exe?  We had another user recently report the same exit code
and the problem was tracked back to that.  When using the Wrapper,
there is no reason to ever make use of the javaw.exe binary because
the Wrapper is handling all console output.

javaw does not behave reliably when run as a Windows service.  It is
able to receive signals both as a console application and as a Windows
application.  The problems arise because the order in which the
signals are received by javaw is not consistent.

Starting with the 3.3.6 release, we will be warning against the use of
javaw when running as a service until a way can be found to reliably
trap all signals received from the system.

Cheers,
Leif


On Tue, Jun 23, 2009 at 1:16 AM, Leland, Robert<rob...@io...> wrote:
> The Windows System log indicated that the wrapper sent an application specific error 143.
> What does error 143 mean ?
> Is there a complete list errors that can be issued by the wrapper ?
>
> ___________________________________
> Robert Leland               INTEGRITYOne  Partners
> P: (703) 581-6522                     1900 Campus Commons Drive, Suite 150
> F: (703) 476-7405                      Reston, VA 20191
> rob...@io...
>
> BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D