Menu
▾
▴
[Wrapper-user] Antw: Re: Service Stops with error 143
|
From: Hubert F. <Hub...@ab...> - 2009-06-22 21:39:57
|
Hi, Silly question: Do the two services use the same configuration file? Could it be a file/resource already locked/used/registered issue? hub >>> "Leland, Robert" <rob...@io...> 22.06.09 20.42 Uhr >>> We use jdk1.6.0_12\bin\java.exe to launch our application. The wrapper.log doesn't have any interesting information. The strange thing is that we have two copies of the wrapper running for the same application on the same machine and they both terminated at the same exact time. Here is the log from one instance (they are both the same) STATUS | wrapper | 2009/06/18 04:08:54 | --> Wrapper Started as Service STATUS | wrapper | 2009/06/18 04:08:54 | Java Service Wrapper Standard Edition 3.3.2 STATUS | wrapper | 2009/06/18 04:08:54 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2009/06/18 04:08:54 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2009/06/18 04:08:54 | Licensed to Production Server STATUS | wrapper | 2009/06/18 04:08:54 | STATUS | wrapper | 2009/06/18 04:08:54 | Launching a JVM... STATUS | wrapper | 2009/06/22 10:07:12 | <-- Wrapper Stopped STATUS | wrapper | 2009/06/22 11:49:57 | --> Wrapper Started as Service ___________________________________ 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 ________________________________ From: Leif Mortenson [mailto:lei...@ta...] Sent: Mon 6/22/2009 12:39 PM To: wra...@li... Subject: Re: [Wrapper-user] Service Stops with error 143 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 ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
