Menu
▾
▴
wrapper-user — User issues for Wrapper. (Support questions, etc.)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(13) |
Nov
(16) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(38) |
Feb
(51) |
Mar
(51) |
Apr
(115) |
May
(82) |
Jun
(30) |
Jul
(50) |
Aug
(68) |
Sep
(57) |
Oct
(160) |
Nov
(80) |
Dec
(78) |
| 2004 |
Jan
(71) |
Feb
(75) |
Mar
(108) |
Apr
(87) |
May
(79) |
Jun
(70) |
Jul
(69) |
Aug
(39) |
Sep
(52) |
Oct
(47) |
Nov
(50) |
Dec
(32) |
| 2005 |
Jan
(22) |
Feb
(122) |
Mar
(46) |
Apr
(76) |
May
(31) |
Jun
(51) |
Jul
(61) |
Aug
(70) |
Sep
(37) |
Oct
(46) |
Nov
(57) |
Dec
(83) |
| 2006 |
Jan
(55) |
Feb
(81) |
Mar
(51) |
Apr
(67) |
May
(77) |
Jun
(43) |
Jul
(106) |
Aug
(64) |
Sep
(47) |
Oct
(64) |
Nov
(60) |
Dec
(12) |
| 2007 |
Jan
(50) |
Feb
(93) |
Mar
(49) |
Apr
(56) |
May
(40) |
Jun
(63) |
Jul
(40) |
Aug
(47) |
Sep
(54) |
Oct
(37) |
Nov
(54) |
Dec
(37) |
| 2008 |
Jan
(35) |
Feb
(39) |
Mar
(26) |
Apr
(14) |
May
(23) |
Jun
(51) |
Jul
(43) |
Aug
(26) |
Sep
(29) |
Oct
(31) |
Nov
(24) |
Dec
(16) |
| 2009 |
Jan
(21) |
Feb
(30) |
Mar
(74) |
Apr
(26) |
May
(26) |
Jun
(43) |
Jul
(23) |
Aug
(23) |
Sep
(15) |
Oct
(27) |
Nov
(37) |
Dec
(10) |
| 2010 |
Jan
(16) |
Feb
(28) |
Mar
(16) |
Apr
(45) |
May
(8) |
Jun
(68) |
Jul
(45) |
Aug
(44) |
Sep
(51) |
Oct
(7) |
Nov
(20) |
Dec
(21) |
| 2011 |
Jan
(14) |
Feb
(17) |
Mar
(7) |
Apr
(7) |
May
(48) |
Jun
(23) |
Jul
(5) |
Aug
(33) |
Sep
(22) |
Oct
(14) |
Nov
(14) |
Dec
(5) |
| 2012 |
Jan
|
Feb
(10) |
Mar
(12) |
Apr
(51) |
May
(10) |
Jun
(8) |
Jul
(14) |
Aug
(22) |
Sep
(9) |
Oct
(24) |
Nov
(14) |
Dec
(13) |
| 2013 |
Jan
(12) |
Feb
(4) |
Mar
(14) |
Apr
(19) |
May
(2) |
Jun
(5) |
Jul
(13) |
Aug
(10) |
Sep
(4) |
Oct
(11) |
Nov
(13) |
Dec
(2) |
| 2014 |
Jan
(3) |
Feb
(14) |
Mar
(5) |
Apr
(10) |
May
(10) |
Jun
(11) |
Jul
(10) |
Aug
(3) |
Sep
(13) |
Oct
(22) |
Nov
(14) |
Dec
(32) |
| 2015 |
Jan
(8) |
Feb
(2) |
Mar
(17) |
Apr
(1) |
May
(24) |
Jun
|
Jul
(4) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(5) |
Dec
(2) |
| 2016 |
Jan
(8) |
Feb
(6) |
Mar
(6) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(7) |
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(8) |
Mar
(6) |
Apr
|
May
|
Jun
(3) |
Jul
(13) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(6) |
Dec
|
| 2018 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
(2) |
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(9) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2019 |
Jan
(9) |
Feb
|
Mar
|
Apr
(10) |
May
(3) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2021 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Philipp K. <phi...@gm...> - 2008-06-12 10:50:41
|
Nevermind, forgot to call start() on the server! :) On Thu, Jun 12, 2008 at 10:04 AM, Philipp Kursawe <phi...@gm...> wrote: > Hello all, > > I have instantiated a WrapperActionServer on port 9999 but it refuses > any connection to it from localhost. The logfile does not print any > error on debug level. > Any ideas what could be wrong? > > Thanks, > Phil > -- > The Dude Abides! > -- The Dude Abides! |
|
From: Philipp K. <phi...@gm...> - 2008-06-12 08:05:05
|
Hello all, I have instantiated a WrapperActionServer on port 9999 but it refuses any connection to it from localhost. The logfile does not print any error on debug level. Any ideas what could be wrong? Thanks, Phil -- The Dude Abides! |
|
From: pram <pra...@ya...> - 2008-06-11 23:37:41
|
Hi all, I have the following requirement: There is a Java application deployed in an application server(OC4J). I need a mechanism by which the application should be automatically started and initialized as soon as the application server is started/restarted, and the application should be terminated when the application server goes down. My question is, can this be achieved using Java Service Wrapper? Can I add some kind of application server dependency in the wrapper.config file, or something similar to that? Any inputs are highly appreciated. Thanks, pram -- View this message in context: http://www.nabble.com/Service-that-starts-automatically-when-an-application-server-is-restarted-tp17789574p17789574.html Sent from the Java Service Wrapper mailing list archive at Nabble.com. |
|
From: Philipp K. <phi...@gm...> - 2008-06-11 17:41:52
|
Hello Leif, will send you an email personally with all the requested source. On Tue, Jun 10, 2008 at 10:31 AM, Leif Mortenson <le...@ta...> wrote: > Phil, > Sorry. Could you please disable the Core events and then send me the > complete run > from Wrapper startup though JVM shutdown. Also if possible, I would > like to see > your application's main class and WrapperListener class. you can send > these to me > directly if you prefer not to post to the list. Please attach the > files as attachments > rather than posting them in line. The log file can be quite difficult > to read with all > the line wrapping. > > Looking at the log you sent, I am a bit surprised by the order of some > of the log > entries and would like to have more context to understand what is going on. > > What version of the Wrapper are you running? This does not appear to be 3.3.0. > > The event should be firing as soon as the "ServiceControlCode from > Wrapper with code 1" > log entry is output. It is the next thing that happens in the method. > But you are not > seeing that for some reason. > > Cheers, > Leif > > On Tue, Jun 10, 2008 at 4:08 PM, Philipp Kursawe <phi...@gm...> wrote: >> Thanks for responding Leif, >> >> here is the log as requested: > <snip> >> >> Thanks for your support! >> >> Phil > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > -- The Dude Abides! |
|
From: Hayes, P. <Pet...@fm...> - 2008-06-11 17:24:34
|
It looks like you need to set the wrapper.java.command to the path to the java executable itself. From your output, it looks like you set it to the bin directory. -----Original Message----- From: wra...@li... [mailto:wra...@li...] On Behalf Of Domingo, Lauren Sent: Wednesday, June 11, 2008 11:34 AM To: wra...@li... Subject: [Wrapper-user] Invoke x86 (64or32)bit wrapper with JVM service on IA 64bit (Windows) I have downloaded and configured x86 Windows wrappers, both 32 and 64 bit community version, following integration method 1 listed on wrapper.tanukisoftware.org. If I try to run the x86 64-bit, the machine recognizes that this application is for another machine and not IA. I am running into a problem when I test the x86, 32-bit wrapper that is logged as follows: STATUS | wrapper | 2008/06/09 12:30:02 | cmappserver installed. STATUS | wrapper | 2008/06/09 12:30:05 | --> Wrapper Started as Console STATUS | wrapper | 2008/06/09 12:30:05 | Java Service Wrapper Community Edition 3.3.0 STATUS | wrapper | 2008/06/09 12:30:05 | Copyright (C) 1999-2008 Tanuki Software, Inc. All Rights Reserved. STATUS | wrapper | 2008/06/09 12:30:05 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2008/06/09 12:30:05 | STATUS | wrapper | 2008/06/09 12:30:06 | Launching a JVM... FATAL | wrapper | 2008/06/09 12:30:06 | Unable to execute Java command. Access is denied. (0x5) FATAL | wrapper | 2008/06/09 12:30:06 | "C:\j2sdk1.4.2_12-x64\bin" -Djava.library.path="C:\Program Files\wrapper-windows-x86-32-3.3.0-st\lib" -classpath "C:\Program Files\wrapper-windows-x86-32-3.3.0-st\lib\wrapper.jar;C:\Program Files\wrapper-windows-x86-32-3.3.0\bin\cmappserver.jar" -Dwrapper.key="CvUNM2ivSK3iiEPu" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=3368 -Dwrapper.version="3.3.0" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp cmappserver ADVICE | wrapper | 2008/06/09 12:30:06 | ADVICE | wrapper | 2008/06/09 12:30:06 | ------------------------------------------------------------------------ ADVICE | wrapper | 2008/06/09 12:30:06 | Advice: ADVICE | wrapper | 2008/06/09 12:30:06 | Access denied errors when attempting to launch the Java process are ADVICE | wrapper | 2008/06/09 12:30:06 | usually caused by strict access permissions assigned to the directory ADVICE | wrapper | 2008/06/09 12:30:06 | in which Java is installed. ADVICE | wrapper | 2008/06/09 12:30:06 | ------------------------------------------------------------------------ ADVICE | wrapper | 2008/06/09 12:30:06 | FATAL | wrapper | 2008/06/09 12:30:06 | Critical error: wait for JVM process failed The jrockit JVM service I am using is for IA64 bit Windows. My problem is I don't know how to go about invoking a JVM service running for an IA 64 bit system with the current available tanuki releases for a Windows wrapper. Thank you for any advice you could give. ------------------------------------------------------------------------ - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Domingo, L. <lau...@hp...> - 2008-06-11 15:34:16
|
I have downloaded and configured x86 Windows wrappers, both 32 and 64 bit community version, following integration method 1 listed on wrapper.tanukisoftware.org. If I try to run the x86 64-bit, the machine recognizes that this application is for another machine and not IA. I am running into a problem when I test the x86, 32-bit wrapper that is logged as follows: STATUS | wrapper | 2008/06/09 12:30:02 | cmappserver installed. STATUS | wrapper | 2008/06/09 12:30:05 | --> Wrapper Started as Console STATUS | wrapper | 2008/06/09 12:30:05 | Java Service Wrapper Community Edition 3.3.0 STATUS | wrapper | 2008/06/09 12:30:05 | Copyright (C) 1999-2008 Tanuki Software, Inc. All Rights Reserved. STATUS | wrapper | 2008/06/09 12:30:05 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2008/06/09 12:30:05 | STATUS | wrapper | 2008/06/09 12:30:06 | Launching a JVM... FATAL | wrapper | 2008/06/09 12:30:06 | Unable to execute Java command. Access is denied. (0x5) FATAL | wrapper | 2008/06/09 12:30:06 | "C:\j2sdk1.4.2_12-x64\bin" -Djava.library.path="C:\Program Files\wrapper-windows-x86-32-3.3.0-st\lib" -classpath "C:\Program Files\wrapper-windows-x86-32-3.3.0-st\lib\wrapper.jar;C:\Program Files\wrapper-windows-x86-32-3.3.0\bin\cmappserver.jar" -Dwrapper.key="CvUNM2ivSK3iiEPu" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=3368 -Dwrapper.version="3.3.0" -Dwrapper.native_library="wrapper" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp cmappserver ADVICE | wrapper | 2008/06/09 12:30:06 | ADVICE | wrapper | 2008/06/09 12:30:06 | ------------------------------------------------------------------------ ADVICE | wrapper | 2008/06/09 12:30:06 | Advice: ADVICE | wrapper | 2008/06/09 12:30:06 | Access denied errors when attempting to launch the Java process are ADVICE | wrapper | 2008/06/09 12:30:06 | usually caused by strict access permissions assigned to the directory ADVICE | wrapper | 2008/06/09 12:30:06 | in which Java is installed. ADVICE | wrapper | 2008/06/09 12:30:06 | ------------------------------------------------------------------------ ADVICE | wrapper | 2008/06/09 12:30:06 | FATAL | wrapper | 2008/06/09 12:30:06 | Critical error: wait for JVM process failed The jrockit JVM service I am using is for IA64 bit Windows. My problem is I don't know how to go about invoking a JVM service running for an IA 64 bit system with the current available tanuki releases for a Windows wrapper. Thank you for any advice you could give. |
|
From: Leif M. <le...@ta...> - 2008-06-10 08:31:16
|
Phil, Sorry. Could you please disable the Core events and then send me the complete run from Wrapper startup though JVM shutdown. Also if possible, I would like to see your application's main class and WrapperListener class. you can send these to me directly if you prefer not to post to the list. Please attach the files as attachments rather than posting them in line. The log file can be quite difficult to read with all the line wrapping. Looking at the log you sent, I am a bit surprised by the order of some of the log entries and would like to have more context to understand what is going on. What version of the Wrapper are you running? This does not appear to be 3.3.0. The event should be firing as soon as the "ServiceControlCode from Wrapper with code 1" log entry is output. It is the next thing that happens in the method. But you are not seeing that for some reason. Cheers, Leif On Tue, Jun 10, 2008 at 4:08 PM, Philipp Kursawe <phi...@gm...> wrote: > Thanks for responding Leif, > > here is the log as requested: <snip> > > Thanks for your support! > > Phil |
|
From: Philipp K. <phi...@gm...> - 2008-06-10 07:08:38
|
Thanks for responding Leif, here is the log as requested: DEBUG | wrapperp | 2008/06/10 09:06:37 | read a packet PING : ok DEBUG | wrapper | 2008/06/10 09:06:37 | Got ping response from JVM INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,181 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482710, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,181 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482710, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,292 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482709, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,292 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482709, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,402 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482708, tickOffset=1] INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,402 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482708, tickOffset=1]) ignored INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,502 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482707, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,502 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482707, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,612 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482706, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,612 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482706, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,722 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482705, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,722 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482705, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,872 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482704, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,872 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482704, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,983 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482703, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:37 | 10.06.2008 09:06:37,983 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482703, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,083 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482702, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,083 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482702, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,183 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482701, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,183 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482701, tickOffset=0]) ignored DEBUG | wrapper | 2008/06/10 09:06:38 | ServiceControlHandler(1) DEBUG | wrapperp | 2008/06/10 09:06:38 | send a packet SERVICE_CONTROL_CODE : 1 DEBUG | wrapper | 2008/06/10 09:06:38 | SERVICE_CONTROL_STOP DEBUG | wrapper | 2008/06/10 09:06:38 | wrapperStopProcess(0) called. INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,283 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482700, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,283 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482700, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:38 | Received a packet SERVICE_CONTROL_CODE : 1 INFO | jvm 1 | 2008/06/10 09:06:38 | ServiceControlCode from Wrapper with code 1 DEBUG | wrapper | 2008/06/10 09:06:38 | Sending stop signal to JVM DEBUG | wrapperp | 2008/06/10 09:06:38 | send a packet STOP : NULL INFO | jvm 1 | 2008/06/10 09:06:38 | Received a packet STOP : INFO | jvm 1 | 2008/06/10 09:06:38 | Thread, Wrapper-Connection, handling the shutdown process. INFO | jvm 1 | 2008/06/10 09:06:38 | calling listener.stop() INFO | jvm 1 | 2008/06/10 09:06:38 | Waiting for WrapperListener.stop runner thread to complete. INFO | jvm 1 | 2008/06/10 09:06:38 | WrapperListener.stop runner thread started. INFO | jvm 1 | 2008/06/10 09:06:38 | WrapperSimpleApp: stop(0) INFO | jvm 1 | 2008/06/10 09:06:38 | WrapperListener.stop runner thread stopped. INFO | jvm 1 | 2008/06/10 09:06:38 | returned from listener.stop() -> 0 INFO | jvm 1 | 2008/06/10 09:06:38 | shutdownJVM(0) Thread:Wrapper-Connection INFO | jvm 1 | 2008/06/10 09:06:38 | Send a packet STOPPED : 0 INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,393 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482699, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,393 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482699, tickOffset=0]) ignored DEBUG | wrapperp | 2008/06/10 09:06:38 | read a packet STOPPED : 0 DEBUG | wrapper | 2008/06/10 09:06:38 | JVM signalled that it was stopped. INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,503 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482698, tickOffset=1] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,503 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482698, tickOffset=1]) ignored INFO | jvm 1 | 2008/06/10 09:06:38 | Closing socket. INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,613 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482697, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,613 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482697, tickOffset=0]) ignored DEBUG | wrapperp | 2008/06/10 09:06:38 | socket read no code (closed?). INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,724 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482696, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,724 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482696, tickOffset=0]) ignored DEBUG | wrapperp | 2008/06/10 09:06:38 | server listening on port 32001. INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,834 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482695, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,834 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482695, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,934 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482694, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:38 | 10.06.2008 09:06:38,934 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482694, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,044 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482693, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,044 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482693, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | calling System.exit(0) INFO | jvm 1 | 2008/06/10 09:06:39 | Wrapper Manager: ShutdownHook started INFO | jvm 1 | 2008/06/10 09:06:39 | WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook INFO | jvm 1 | 2008/06/10 09:06:39 | Communications runner thread started. INFO | jvm 1 | 2008/06/10 09:06:39 | Open socket to wrapper...Wrapper-Connection INFO | jvm 1 | 2008/06/10 09:06:39 | Failed attempt to bind using local port 31000 INFO | jvm 1 | 2008/06/10 09:06:39 | Opened Socket from 31001 to 32000 INFO | jvm 1 | 2008/06/10 09:06:39 | Send a packet KEY : t77VADaxERO8mnMn INFO | jvm 1 | 2008/06/10 09:06:39 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001]) INFO | jvm 1 | 2008/06/10 09:06:39 | Send a packet STOP : 0 INFO | jvm 1 | 2008/06/10 09:06:39 | Startup runner thread stopped. INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,154 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482692, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,154 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482692, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,264 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482691, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,264 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482691, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,375 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482690, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,375 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482690, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,485 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482689, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,485 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482689, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,585 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482688, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,585 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482688, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,695 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482687, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,695 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482687, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,805 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482686, tickOffset=1] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,805 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482686, tickOffset=1]) ignored INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,935 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482685, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:39 | 10.06.2008 09:06:39,935 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482685, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,046 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482684, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,046 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482684, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | Thread, Wrapper-Shutdown-Hook, handling the shutdown process. INFO | jvm 1 | 2008/06/10 09:06:40 | shutdownJVM(0) Thread:Wrapper-Shutdown-Hook INFO | jvm 1 | 2008/06/10 09:06:40 | Send a packet STOPPED : 0 INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,156 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482683, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,156 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482683, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,266 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482682, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,266 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482682, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | Closing socket. INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,376 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482681, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,376 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482681, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,486 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482680, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,486 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482680, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,596 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482679, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,596 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482679, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,706 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482678, tickOffset=1] INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,706 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482678, tickOffset=1]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,817 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - WrapperTickEvent[ticks=-2147482677, tickOffset=0] INFO | jvm 1 | 2008/06/10 09:06:40 | 10.06.2008 09:06:40,817 [DEBUG] [Wrapper-Control-Event-Monitor] extender.WrapperExtender - controlEvent(WrapperTickEvent[ticks=-2147482677, tickOffset=0]) ignored INFO | jvm 1 | 2008/06/10 09:06:40 | Server daemon shut down INFO | jvm 1 | 2008/06/10 09:06:40 | Wrapper Manager: ShutdownHook complete DEBUG | wrapper | 2008/06/10 09:06:41 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0. DEBUG | wrapper | 2008/06/10 09:06:41 | JVM exited normally. STATUS | wrapper | 2008/06/10 09:06:41 | <-- Wrapper Stopped Thanks for your support! Phil |
|
From: Dittmar G. <gr...@if...> - 2008-06-09 05:40:49
|
Dittmar Gross ist wegen Urlaub bis 23-Jun-2008 nicht per eMail zu erreichen. Bitte wenden Sie sich in dringenden Faellen an Telefon +49 (69) 7680 50, Telefax +49 (69) 7680 5333 oder eMail fi...@if... Dittmar Gross is not available via eMail until Jun-23-2008 because of vacation. In urgent cases please contact us directly by Telephone +49 (69) 7680 50, Fax +49 (69) 7680 5333 or eMail fi...@if... ---------------------------------------------------------------------------- i:FAO Group Clemensstrasse 9, 60487 Frankfurt am Main, Germany Tel +49 (69) 7680-50, Fax +49 (69) 7680-5100, eMail information at ifao.net, www.cytric.info i:FAO Group GmbH Sitz in Frankfurt am Main Eingetragen beim Amtsgericht Frankfurt am Main, HRB 73600 Geschaeftsfuehrer: Louis Arnitz, Karin Froese To view the disclaimer text, click here: www.ifao.net/disclaimer |
|
From: Leif M. <le...@ta...> - 2008-06-09 05:40:26
|
Philipp, I just went back and tested this out again and it appears to be working correctly for me. Could you please set the wrapper.debug=true property in your configuration and try this again? Stop your service by executing "net stop myapp". You should see something like the following in your log: --- DEBUG | wrapper | 2008/06/09 14:37:24 | ServiceControlHandler(1) DEBUG | wrapperp | 2008/06/09 14:37:24 | send a packet SERVICE_CONTROL_CODE : 1 DEBUG | wrapper | 2008/06/09 14:37:24 | SERVICE_CONTROL_STOP DEBUG | wrapper | 2008/06/09 14:37:24 | wrapperStopProcess(0) called. INFO | jvm 1 | 2008/06/09 14:37:24 | WrapperManager Debug: Received a packet SERVICE_CONTROL_CODE : 1 INFO | jvm 1 | 2008/06/09 14:37:24 | WrapperManager Debug: ServiceControlCode from Wrapper with code 1 INFO | jvm 1 | 2008/06/09 14:37:24 | Received event: WrapperServiceControlEvent[serviceControlCode=1] DEBUG | wrapper | 2008/06/09 14:37:24 | Sending stop signal to JVM --- The line "Received event:..." is being output by my event handler. If this is not what you are seeing, could you please post your wrapper.log file for several seconds before and after you stop the service? Thanks, Leif On Wed, Jun 4, 2008 at 4:18 AM, Philipp Kursawe <phi...@gm...> wrote: > Hello! > > I am using the WrapperSimpleApp and register in my own code a > WrapperEventListener like this: > > WrapperManager.addWrapperEventListener(this, > WrapperEventListener.EVENT_FLAG_CONTROL > | WrapperEventListener.EVENT_FLAG_SERVICE > | WrapperEventListener.EVENT_FLAG_CORE); > > it should be therefore informed about all events. However only tick > events from CORE are sent. > I guess the WrapperSimpleApp kills the event notifications by calling > WrapperManager.stop() inside its controlEvent method. > My assumption was that before WrapperSimpleApp gets the event > delivered all listeners are informed about it before-hand or otherwise > they have no possibility to react and cleanly exit in case of a > service shutdown. > Interestingly the CTRL+C event is delivered when running in console mode. > > I am currently building a Extender for this wrapper for an OSGi > environment where you need to cleanly shut down the OSGi framework and > not just System.exit(). Willing to contribute the final bundle I first > need to get this issue worked out. > Any ideas Leif? > > Thanks in advance, > Phil > -- |
|
From: Thorsten L. <kar...@ya...> - 2008-06-05 09:39:09
|
Thanks for your suggestions! Indeed, it seems to be a general Java problem - should have checked that beforehand, but I had good reason for assuming that my other apps were running fine. But in fact it appears they are not. I've had a bit more of a web search on it and it seems that this is a general Java problem on Windows 2003 Server after installing a timezone patch (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6501839). So this was obviously the wrong user list to post to, but thanks to you and Leif for your help anyways! And yes, you are right, starting the JRE with "-Duser.timezone=Europe/Berlin" solves the problem (although not in a very general way). ----- Ursprüngliche Mail ---- Von: Mikael Ståldal <mik...@un...> An: wra...@li... Gesendet: Donnerstag, den 5. Juni 2008, 10:02:45 Uhr Betreff: Re: [Wrapper-user] Wrapper starts java app with wrong time (time shift of exactly 2 hours) Thorsten Lampe skrev: > I've got some very strange behavior here. Running on a Windows 2003 Server, the service wrapper starts my java app using a domain user account. The extremely strange thing is that I'm absolutely positive that the wrapper is running at the correct system time while my java app's time is 2 hours behind that!!! > I can see this in the log files since every line logged by my app itself contains a time of, say 5:46.16 PM when the exact same line of output will appear in the wrapper's log as logged at time 7:46.16 PM, the correct system time as currently defined. Do you get the same problem when running a Java app without Wrapper? I have seen a similar problem on Linux, and it was a Java problem, not a Wrapper problem. The solution was to set the environment variable TZ to your timezone. The value "Europe/Berlin" should work for you if you are in Germany. Perhaps it will work on Windows as well. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user __________________________________________________________ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com |
|
From: Mikael S. <mik...@un...> - 2008-06-05 08:02:57
|
Thorsten Lampe skrev: > I've got some very strange behavior here. Running on a Windows 2003 Server, the service wrapper starts my java app using a domain user account. The extremely strange thing is that I'm absolutely positive that the wrapper is running at the correct system time while my java app's time is 2 hours behind that!!! > I can see this in the log files since every line logged by my app itself contains a time of, say 5:46.16 PM when the exact same line of output will appear in the wrapper's log as logged at time 7:46.16 PM, the correct system time as currently defined. Do you get the same problem when running a Java app without Wrapper? I have seen a similar problem on Linux, and it was a Java problem, not a Wrapper problem. The solution was to set the environment variable TZ to your timezone. The value "Europe/Berlin" should work for you if you are in Germany. Perhaps it will work on Windows as well. |
|
From: Leif M. <le...@ta...> - 2008-06-04 16:53:06
|
Thorsten, This is not a problem which I have heard of in the past. A few questions. 1) Are you passing any time related parameters to the JVM when it is launched? 2) What is the specific JVM version you are running? Is it the same on both machines? Depending on your wrapper configuration, you may not be running the JVM you are expecting when running as a service. I suggest setting the following property to see the resolved location of the java exe: wrapper.java.command.loglevel=INFO You can also see the Java version in the log file if you set wrapper.debug=true 3) Do you get the same behavior when running from a console as you do when running as a service? Cheers, Leif Thorsten Lampe wrote: > Sorry for replying to my own post. Just noticed that the 2 hours time shift does exactly match the difference between my local time (GMT+1, Berlin) in daylight savings time versus GMT without daylight savings time. So it seems as if my java app might be running in "plain" GMT. I only wonder why, when the wrapper starting it runs in "GMT+1+daylight savings"... > > > ----- Ursprüngliche Mail ---- > Von: Thorsten Lampe <kar...@ya...> > An: wra...@li... > Gesendet: Montag, den 2. Juni 2008, 22:22:59 Uhr > Betreff: [Wrapper-user] Wrapper starts java app with wrong time (time shift of exactly 2 hours) > > I've got some very strange behavior here. Running on a Windows 2003 Server, the service wrapper starts my java app using a domain user account. The extremely strange thing is that I'm absolutely positive that the wrapper is running at the correct system time while my java app's time is 2 hours behind that!!! > I can see this in the log files since every line logged by my app itself contains a time of, say 5:46.16 PM when the exact same line of output will appear in the wrapper's log as logged at time 7:46.16 PM, the correct system time as currently defined. > > Does anyone have a clue what might be the reason for this? I'm absolutely clueless (and kind of speechless, too... :-) > > BTW, the same app works fine when installed on another - Windows XP - machine so I guess that it must somehow be some kind of configuration problem on my server, but I can't really figure out which... > > > Thanks for any ideas! > > > Thorsten > |
|
From: Leif M. <le...@ta...> - 2008-06-04 16:44:19
|
Safraz, Just to confirm the file which is failing to be rolled is the log4j log file, and not the wrapper.log. Looking at your log4j configuration, there are two files which should be getting rolled: ../logs/ForkManager.log and ../logs/dist-message.log Are they both failing to be rolled? The Wrapper does not do anything which should be affecting log files. The Wrapper will be running as the SYSTEM account when running as a service. It may be possible that some file permissions are causing you problems. Another possibility is that the file is being locked somehow. I have seen the wrapper.log file fail to wrap because a tail program was running against in on Windows. Cheers, Leif homejob sl wrote: > > I'm using java Wrapper (32bit community edition v3.3.0) under windows > XP environment. > I wanna roll up the log file for each day & size. so i have written a > class to incorporate it. > The log file rolls when the application run from the console, > however It keep on growing when run as a service.(doesn't roll for the > criteria specified in log4j.property) > > Below you can find the Configuration files. > > Thanks, > Safraz > > > #******************************************************************** > # Wrapper License Properties (Ignored by Community Edition) > #******************************************************************** > #include ../conf/wrapper-license.conf > > #******************************************************************** > # Wrapper Java Properties > #******************************************************************** > # Java Application > wrapper.java.command=java > > # Java Main class. This class must implement the WrapperListener > interface > # or guarantee that the WrapperManager class is initialized. Helper > # classes are provided to do this for you. See the Integration section > # of the documentation for details. > wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp > > > # Java Classpath (include wrapper.jar) Add class path elements as > # needed starting from 1 > wrapper.java.classpath.1=../lib/wrapper.jar > wrapper.java.classpath.2=../FM.jar > wrapper.java.classpath.3=../lib/InfoLogger.jar > wrapper.java.classpath.4=../lib/log4j-1.2.15.jar > wrapper.java.classpath.5=../lib/ant.jar > wrapper.java.classpath.6=../lib/hibernate/antlr-2.7.6.jar > wrapper.java.classpath.7=../lib/hibernate/asm-attrs.jar > wrapper.java.classpath.8=../lib/hibernate/asm.jar > wrapper.java.classpath.9=../lib/hibernate/cglib-2.1.3.jar > wrapper.java.classpath.10=../lib/hibernate/commons-collections-2.1.1.jar > wrapper.java.classpath.11=../lib/hibernate/commons-logging-1.0.4.jar > wrapper.java.classpath.12=../lib/hibernate/dom4j-1.6.1.jar > wrapper.java.classpath.13=../lib/hibernate/hibernate3.jar > wrapper.java.classpath.14=../lib/hibernate/jta.jar > wrapper.java.classpath.15=../lib/mysql-connector-java-5.1.5-bin.jar > wrapper.java.classpath.16=../lib/RemoteProcess.jar > wrapper.java.classpath.17=../lib/jftp.jar > wrapper.java.classpath.18=../lib/jconn2.jar > wrapper.java.classpath.19=../lib/mail.jar > wrapper.java.classpath.20=../lib/activation.jar > wrapper.java.classpath.21=../lib/TestFork.jar > wrapper.java.classpath.22=../lib/ConfigurationManager.jar > wrapper.java.classpath.23=../Distributor/Distributor.jar > > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=../lib > > # Java Additional Parameters > wrapper.java.additional.1=-Dlog4j.configuration=file:../conf/log4j.properties > wrapper.java.additional.2=-DforkManager.rmi.port=1099 > wrapper.java.additional.3=-Dterminate.startedProcesses=false > wrapper.java.additional.4=-DforkManager.useSecurityManager=true > wrapper.java.additional.5=-Djava.rmi.server.codebase=file:../FM.jar > wrapper.java.additional.6=-Djava.rmi.server.hostname=192.168.11.232 > <http://192.168.11.232> > wrapper.java.additional.7=-Djava.security.policy=../server.policy > wrapper.java.additional.8=-Dprocessmanager.hibernate.configuration=file:../conf/processmanager-hibernate.cfg.xml > > > # Initial Java Heap Size (in MB) > #wrapper.java.initmemory=3 > > # Maximum Java Heap Size (in MB) > #wrapper.java.maxmemory=64 > > # Application parameters. Add parameters as needed starting from 1 > wrapper.app.parameter.1=lk.informatics.infomediation.forkmanager.ForkManager > > #******************************************************************** > # Wrapper Logging Properties > #******************************************************************** > # Format of output for the console. (See docs for formats) > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > wrapper.console.loglevel=INFO > > # Log file to use for wrapper output logging. > wrapper.logfile=../logs/wrapper.log > > # Format of output for the log file. (See docs for formats) > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > wrapper.logfile.loglevel=INFO > > # Maximum size that the log file will be allowed to grow to before > # the log is rolled. Size is specified in bytes. The default value > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > wrapper.logfile.maxsize=0 > > # Maximum number of rolled log files which will be allowed before old > # files are deleted. The default value of 0 implies no limit. > wrapper.logfile.maxfiles=0 > > # Log Level for sys/event log output. (See docs for log levels) > wrapper.syslog.loglevel=NONE > > #******************************************************************** > # Wrapper Windows Properties > #******************************************************************** > # Title to use when running as a console > wrapper.console.title=AvaBill Fork Manager > > #******************************************************************** > # Wrapper Windows NT/2000/XP Service Properties > #******************************************************************** > # WARNING - Do not modify any of these properties when an application > # using this configuration file has been installed as a service. > # Please uninstall the service before modifying this section. The > # service can then be reinstalled. > > # Name of the service > wrapper.ntservice.name <http://wrapper.ntservice.name>=AvaBill Fork > Manager > > # Display name of the service > wrapper.ntservice.displayname=AvaBill Fork Manager > > > # Description of the service > wrapper.ntservice.description=AvaBill Fork Manager > > # Service dependencies. Add dependencies as needed starting from 1 > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > wrapper.ntservice.starttype=AUTO_START > > # Allow the service to interact with the desktop. > wrapper.ntservice.interactive=false > > > ---------------------------- > log4j.property file > > > ### direct log messages to stdout ### > log4j.appender.stdout=org.apache.log4j.ConsoleAppender > log4j.appender.stdout.Target=System.out > log4j.appender.stdout.layout=org.apache.log4j.PatternLayout > log4j.appender.stdout.layout.ConversionPattern=%d %-5p [%c{2}][%t] - %m%n > > log4j.appender.forkManager=lk.informatics.logging.appender.RollingFileAppenderWithDate > log4j.appender.forkManager.File=../logs/ForkManager.log > log4j.appender.forkManager.MaxFileSize=1KB > log4j.appender.forkManager.DateFormat=ddMMyyyy_HHmmss > log4j.appender.forkManager.layout=org.apache.log4j.PatternLayout > log4j.appender.forkManager.layout.ConversionPattern=%d %-5p > [%c{2}][%t] - %m%n > > ### direct messages to file logs/message.log ### > log4j.appender.distfile=lk.informatics.logging.appender.RollingFileAppenderWithDate > log4j.appender.distfile.File=../logs/dist-message.log > log4j.appender.distfile.MaxFileSize=256KB > log4j.appender.distfile.DateFormat=ddMMyyyy_HHmmss > log4j.appender.distfile.layout=org.apache.log4j.PatternLayout > log4j.appender.distfile.layout.ConversionPattern=%d %-5p [%c{2}][%t] - > %m%n > > > log4j.rootLogger=info,stdout,distfile > log4j.logger.lk.informatics.infomediation.forkmanager=debug, forkManager > |
|
From: homejob s. <hom...@gm...> - 2008-06-04 05:57:41
|
I'm using java Wrapper (32bit community edition v3.3.0) under windows XP
environment.
I wanna roll up the log file for each day & size. so i have written a class
to incorporate it.
The log file rolls when the application run from the console,
however It keep on growing when run as a service.(doesn't roll for the
criteria specified in log4j.property)
Below you can find the Configuration files.
Thanks,
Safraz
#********************************************************************
# Wrapper License Properties (Ignored by Community Edition)
#********************************************************************
#include ../conf/wrapper-license.conf
#********************************************************************
# Wrapper Java Properties
#********************************************************************
# Java Application
wrapper.java.command=java
# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../FM.jar
wrapper.java.classpath.3=../lib/InfoLogger.jar
wrapper.java.classpath.4=../lib/log4j-1.2.15.jar
wrapper.java.classpath.5=../lib/ant.jar
wrapper.java.classpath.6=../lib/hibernate/antlr-2.7.6.jar
wrapper.java.classpath.7=../lib/hibernate/asm-attrs.jar
wrapper.java.classpath.8=../lib/hibernate/asm.jar
wrapper.java.classpath.9=../lib/hibernate/cglib-2.1.3.jar
wrapper.java.classpath.10=../lib/hibernate/commons-collections-2.1.1.jar
wrapper.java.classpath.11=../lib/hibernate/commons-logging-1.0.4.jar
wrapper.java.classpath.12=../lib/hibernate/dom4j-1.6.1.jar
wrapper.java.classpath.13=../lib/hibernate/hibernate3.jar
wrapper.java.classpath.14=../lib/hibernate/jta.jar
wrapper.java.classpath.15=../lib/mysql-connector-java-5.1.5-bin.jar
wrapper.java.classpath.16=../lib/RemoteProcess.jar
wrapper.java.classpath.17=../lib/jftp.jar
wrapper.java.classpath.18=../lib/jconn2.jar
wrapper.java.classpath.19=../lib/mail.jar
wrapper.java.classpath.20=../lib/activation.jar
wrapper.java.classpath.21=../lib/TestFork.jar
wrapper.java.classpath.22=../lib/ConfigurationManager.jar
wrapper.java.classpath.23=../Distributor/Distributor.jar
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib
# Java Additional Parameters
wrapper.java.additional.1=-Dlog4j.configuration=file:../conf/log4j.properties
wrapper.java.additional.2=-DforkManager.rmi.port=1099
wrapper.java.additional.3=-Dterminate.startedProcesses=false
wrapper.java.additional.4=-DforkManager.useSecurityManager=true
wrapper.java.additional.5=-Djava.rmi.server.codebase=file:../FM.jar
wrapper.java.additional.6=-Djava.rmi.server.hostname=192.168.11.232
wrapper.java.additional.7=-Djava.security.policy=../server.policy
wrapper.java.additional.8=-Dprocessmanager.hibernate.configuration=file:../conf/processmanager-hibernate.cfg.xml
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3
# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64
# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=lk.informatics.infomediation.forkmanager.ForkManager
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM
# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO
# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log
# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM
# Log Level for log file output. (See docs for log levels)
wrapper.logfile.loglevel=INFO
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0
# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE
#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=AvaBill Fork Manager
#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
wrapper.ntservice.name=AvaBill Fork Manager
# Display name of the service
wrapper.ntservice.displayname=AvaBill Fork Manager
# Description of the service
wrapper.ntservice.description=AvaBill Fork Manager
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
----------------------------
log4j.property file
### direct log messages to stdout ###
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d %-5p [%c{2}][%t] - %m%n
log4j.appender.forkManager=lk.informatics.logging.appender.RollingFileAppenderWithDate
log4j.appender.forkManager.File=../logs/ForkManager.log
log4j.appender.forkManager.MaxFileSize=1KB
log4j.appender.forkManager.DateFormat=ddMMyyyy_HHmmss
log4j.appender.forkManager.layout=org.apache.log4j.PatternLayout
log4j.appender.forkManager.layout.ConversionPattern=%d %-5p [%c{2}][%t] -
%m%n
### direct messages to file logs/message.log ###
log4j.appender.distfile=lk.informatics.logging.appender.RollingFileAppenderWithDate
log4j.appender.distfile.File=../logs/dist-message.log
log4j.appender.distfile.MaxFileSize=256KB
log4j.appender.distfile.DateFormat=ddMMyyyy_HHmmss
log4j.appender.distfile.layout=org.apache.log4j.PatternLayout
log4j.appender.distfile.layout.ConversionPattern=%d %-5p [%c{2}][%t] - %m%n
log4j.rootLogger=info,stdout,distfile
log4j.logger.lk.informatics.infomediation.forkmanager=debug, forkManager
|
|
From: Philipp K. <phi...@gm...> - 2008-06-03 19:19:11
|
Hello! I am using the WrapperSimpleApp and register in my own code a WrapperEventListener like this: WrapperManager.addWrapperEventListener(this, WrapperEventListener.EVENT_FLAG_CONTROL | WrapperEventListener.EVENT_FLAG_SERVICE | WrapperEventListener.EVENT_FLAG_CORE); it should be therefore informed about all events. However only tick events from CORE are sent. I guess the WrapperSimpleApp kills the event notifications by calling WrapperManager.stop() inside its controlEvent method. My assumption was that before WrapperSimpleApp gets the event delivered all listeners are informed about it before-hand or otherwise they have no possibility to react and cleanly exit in case of a service shutdown. Interestingly the CTRL+C event is delivered when running in console mode. I am currently building a Extender for this wrapper for an OSGi environment where you need to cleanly shut down the OSGi framework and not just System.exit(). Willing to contribute the final bundle I first need to get this issue worked out. Any ideas Leif? Thanks in advance, Phil -- |
|
From: haipeng d. <hai...@gm...> - 2008-06-03 03:57:21
|
"Interactive" option works. Thanks a lot. On Fri, May 30, 2008 at 11:32 PM, Leif Mortenson <le...@ta...> wrote: > Haipeng, > In the future a lot more information would be helpful. I do not have > a much experience > with Swing, but I think I figured out what you are doing. I assume > you are referring to > the FlaforListener.flavorsChanged class. Registered with the > Clipboard.addFlavorListener > method. > > As I understand it from the javadocs, it looks like this method should > be getting fired > whenever the contents of the system Clipboard changes. The problem > here is likely > because the Wrapper(JVM) and your desktop application are running as > different > users. > > By default Windows services run as the SYSTEM user. It would not > surprise me if > the SYSTEM user does not have access to the clipboard of the user > currently logged > in. I would suggest doing some investigation along these lines then > please post back > if you find anything out one way or the other. > > Does your Java service set the wrapper.ntservice.interactive=TRUE > property? If not > you might want to try that. > > Another option if you not need your application to be interactive > would be to run the > service as the same user as you are logged in as. It is not possible > to specify > a user if your service is interactive however. > > http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-account.html > > http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-interactive.html > > Cheers, > Leif > > On Sat, May 31, 2008 at 8:02 AM, haipeng du <hai...@gm...> wrote: > > If I start my application in eclipse or from command line, everything > works > > well. But if I start it as windows service, when text is copied, > > flavorsChanged event can not be fired in my application. Do I need to > modify > > some configurations? > > Thanks. > > > > -- > > Haipeng Du > > Salt Lake City > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > -- Haipeng Du Salt Lake City |
|
From: Thorsten L. <kar...@ya...> - 2008-06-02 20:40:07
|
Sorry for replying to my own post. Just noticed that the 2 hours time shift does exactly match the difference between my local time (GMT+1, Berlin) in daylight savings time versus GMT without daylight savings time. So it seems as if my java app might be running in "plain" GMT. I only wonder why, when the wrapper starting it runs in "GMT+1+daylight savings"...
----- Ursprüngliche Mail ----
Von: Thorsten Lampe <kar...@ya...>
An: wra...@li...
Gesendet: Montag, den 2. Juni 2008, 22:22:59 Uhr
Betreff: [Wrapper-user] Wrapper starts java app with wrong time (time shift of exactly 2 hours)
I've got some very strange behavior here. Running on a Windows 2003 Server, the service wrapper starts my java app using a domain user account. The extremely strange thing is that I'm absolutely positive that the wrapper is running at the correct system time while my java app's time is 2 hours behind that!!!
I can see this in the log files since every line logged by my app itself contains a time of, say 5:46.16 PM when the exact same line of output will appear in the wrapper's log as logged at time 7:46.16 PM, the correct system time as currently defined.
Does anyone have a clue what might be the reason for this? I'm absolutely clueless (and kind of speechless, too... :-)
BTW, the same app works fine when installed on another - Windows XP - machine so I guess that it must somehow be some kind of configuration problem on my server, but I can't really figure out which...
Thanks for any ideas!
Thorsten
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
|
|
From: Thorsten L. <kar...@ya...> - 2008-06-02 20:23:08
|
I've got some very strange behavior here. Running on a Windows 2003 Server, the service wrapper starts my java app using a domain user account. The extremely strange thing is that I'm absolutely positive that the wrapper is running at the correct system time while my java app's time is 2 hours behind that!!!
I can see this in the log files since every line logged by my app itself contains a time of, say 5:46.16 PM when the exact same line of output will appear in the wrapper's log as logged at time 7:46.16 PM, the correct system time as currently defined.
Does anyone have a clue what might be the reason for this? I'm absolutely clueless (and kind of speechless, too... :-)
BTW, the same app works fine when installed on another - Windows XP - machine so I guess that it must somehow be some kind of configuration problem on my server, but I can't really figure out which...
Thanks for any ideas!
Thorsten
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
|
|
From: Leif M. <le...@ta...> - 2008-05-31 05:32:49
|
Haipeng, In the future a lot more information would be helpful. I do not have a much experience with Swing, but I think I figured out what you are doing. I assume you are referring to the FlaforListener.flavorsChanged class. Registered with the Clipboard.addFlavorListener method. As I understand it from the javadocs, it looks like this method should be getting fired whenever the contents of the system Clipboard changes. The problem here is likely because the Wrapper(JVM) and your desktop application are running as different users. By default Windows services run as the SYSTEM user. It would not surprise me if the SYSTEM user does not have access to the clipboard of the user currently logged in. I would suggest doing some investigation along these lines then please post back if you find anything out one way or the other. Does your Java service set the wrapper.ntservice.interactive=TRUE property? If not you might want to try that. Another option if you not need your application to be interactive would be to run the service as the same user as you are logged in as. It is not possible to specify a user if your service is interactive however. http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-account.html http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-interactive.html Cheers, Leif On Sat, May 31, 2008 at 8:02 AM, haipeng du <hai...@gm...> wrote: > If I start my application in eclipse or from command line, everything works > well. But if I start it as windows service, when text is copied, > flavorsChanged event can not be fired in my application. Do I need to modify > some configurations? > Thanks. > > -- > Haipeng Du > Salt Lake City |
|
From: haipeng d. <hai...@gm...> - 2008-05-30 23:02:46
|
If I start my application in eclipse or from command line, everything works well. But if I start it as windows service, when text is copied, flavorsChanged event can not be fired in my application. Do I need to modify some configurations? Thanks. -- Haipeng Du Salt Lake City |
|
From: Borkholder, B. <bor...@me...> - 2008-05-30 01:20:00
|
It was indeed a permissions issue. After changing the service account to be one of the administrators on the machine, the logging worked correctly. One of the parent directories had denied SYSTEM access, so it wasn't immediately obvious. Thank you for your quick and insightful reply, Leif. Brandon ________________________________________________________________________ From: Leif Mortenson <le...@ta...> Reply-To: wra...@li... To: wra...@li... Subject: Re: [Wrapper-user] win32 service doesn't log Date: Fri, 30 May 2008 09:46:19 +0900 Brandon, For the log4j problem. This is working with this exact same configuration that works on other machines? Usually there is a reference to a log4j properties file in the wrapper.java.additional.n section. It might be in one of your application jar files however. Because both your log4j and wrapper.log files are failing to write to the disk, I am wondering if you have some kind of file permissions set on the application directory. The service is running as the SYSTEM directory which will not have the same permissions as a regular user. If the Wrapper fails to write to the configured directory, it will attempt to write to current working directory. On startup, this will be the windows system directory when running as a service. Can you please search under C:\windows for a wrapper.log file? That might give us some more clues. Your classpath declaration contains the log4j jar twice. That should matter though. wrapper.java.classpath.11=lib/log4j-1.2.15.jar wrapper.java.classpath.16=lib/log4j-1.2.15.jar Also, you can simplify your classpath declaration as follows. This makes it a lot easier to maintain and will get rid of mistakes like the one above: wrapper.java.classpath.1=lib/jaxb/*.jar wrapper.java.classpath.2=lib/*.jar wrapper.java.classpath.3=resources Cheers, Leif On Fri, May 30, 2008 at 8:04 AM, Borkholder, Brandon <bor...@me...> wrote: > I have a problem with logging under a Windows XP Pro installation using > the 32bit community edition v3.3.0. The same deployment package works > for several other machines that we've tested. But this one machine will > not log the service messages to wrapper.log nor will our software log > using the log4j package. The log4j jar is in the classpath, but > regardless of whether it is or not, that shouldn't affect the > wrapper.log that the java-service-wrapper generates. > > The problem only exists when the wrapper is run as a service. When it > is run from the console, everything logs as normal. As a service, the > software runs, but nothing logs. > > My configuration file is below. > > Thanks, > Brandon > > #******************************************************************** > # Wrapper License Properties (Ignored by Community Edition) > #******************************************************************** > #include wrapper-license.conf > > #******************************************************************** > # Wrapper Java Properties > #******************************************************************** > # Java Application > wrapper.java.command=java > > wrapper.working.dir=.. > > # Java Main class. This class must implement the WrapperListener > interface > # or guarantee that the WrapperManager class is initialized. Helper > # classes are provided to do this for you. See the Integration section > # of the documentation for details. > wrapper.java.mainclass=thread.DetectorService > > > # Java Classpath (include wrapper.jar) Add class path elements as > # needed starting from 1 > wrapper.java.classpath.1=lib/jaxb/activation.jar > wrapper.java.classpath.2=lib/jaxb/jaxb-api.jar > wrapper.java.classpath.3=lib/jaxb/jaxb-impl.jar > wrapper.java.classpath.4=lib/jaxb/jaxb-xjc.jar > wrapper.java.classpath.5=lib/jaxb/jaxb1-impl.jar > wrapper.java.classpath.6=lib/jaxb/jsr173_1.0_api.jar > wrapper.java.classpath.7=lib/jdbcappender.jar > wrapper.java.classpath.8=lib/jms.jar > wrapper.java.classpath.9=lib/jta.jar > wrapper.java.classpath.10=lib/aqapi.jar > wrapper.java.classpath.11=lib/log4j-1.2.15.jar > wrapper.java.classpath.12=lib/ojdbc14.jar > wrapper.java.classpath.13=lib/weka.jar > wrapper.java.classpath.14=lib/xalan.jar > wrapper.java.classpath.15=lib/xercesImpl.jar > wrapper.java.classpath.16=lib/log4j-1.2.15.jar > wrapper.java.classpath.17=lib/commons-dbcp-1.2.2.jar > wrapper.java.classpath.18=lib/commons-pool-1.3.jar > wrapper.java.classpath.19=lib/util.jar > wrapper.java.classpath.20=resources > wrapper.java.classpath.21=lib/service-wrapper.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=ServiceWrapper/lib > > # Java Additional Parameters > #wrapper.java.additional.1= > > # Initial Java Heap Size (in MB) > wrapper.java.initmemory=100 > > # Maximum Java Heap Size (in MB) > wrapper.java.maxmemory=1024 > > # Application parameters. Add parameters as needed starting from 1 > #wrapper.app.parameter.1= > > #******************************************************************** > # Wrapper Logging Properties > #******************************************************************** > # Format of output for the console. (See docs for formats) > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > wrapper.console.loglevel=DEBUG > > # Log file to use for wrapper output logging. > wrapper.logfile=ServiceWrapper/wrapper.log > > # Format of output for the log file. (See docs for formats) > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > wrapper.logfile.loglevel=DEBUG > > # Maximum size that the log file will be allowed to grow to before > # the log is rolled. Size is specified in bytes. The default value > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > wrapper.logfile.maxsize=1m > > # Maximum number of rolled log files which will be allowed before old > # files are deleted. The default value of 0 implies no limit. > wrapper.logfile.maxfiles=10 > > # Log Level for sys/event log output. (See docs for log levels) > wrapper.syslog.loglevel=DEBUG > > #******************************************************************** > # Wrapper Windows Properties > #******************************************************************** > # Title to use when running as a console > wrapper.console.title=Dummy > > #******************************************************************** > # Wrapper Windows NT/2000/XP Service Properties > #******************************************************************** > # WARNING - Do not modify any of these properties when an application > # using this configuration file has been installed as a service. > # Please uninstall the service before modifying this section. The > # service can then be reinstalled. > > # Name of the service > wrapper.ntservice.name=Dummy > > # Display name of the service > wrapper.ntservice.displayname=Dummy > > # Description of the service > wrapper.ntservice.description= > > # Service dependencies. Add dependencies as needed starting from 1 > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > wrapper.ntservice.starttype=DEMAND_START > > # Allow the service to interact with the desktop. > wrapper.ntservice.interactive=false > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <le...@ta...> - 2008-05-30 00:46:24
|
Brandon, For the log4j problem. This is working with this exact same configuration that works on other machines? Usually there is a reference to a log4j properties file in the wrapper.java.additional.n section. It might be in one of your application jar files however. Because both your log4j and wrapper.log files are failing to write to the disk, I am wondering if you have some kind of file permissions set on the application directory. The service is running as the SYSTEM directory which will not have the same permissions as a regular user. If the Wrapper fails to write to the configured directory, it will attempt to write to current working directory. On startup, this will be the windows system directory when running as a service. Can you please search under C:\windows for a wrapper.log file? That might give us some more clues. Your classpath declaration contains the log4j jar twice. That should matter though. wrapper.java.classpath.11=lib/log4j-1.2.15.jar wrapper.java.classpath.16=lib/log4j-1.2.15.jar Also, you can simplify your classpath declaration as follows. This makes it a lot easier to maintain and will get rid of mistakes like the one above: wrapper.java.classpath.1=lib/jaxb/*.jar wrapper.java.classpath.2=lib/*.jar wrapper.java.classpath.3=resources Cheers, Leif On Fri, May 30, 2008 at 8:04 AM, Borkholder, Brandon <bor...@me...> wrote: > I have a problem with logging under a Windows XP Pro installation using > the 32bit community edition v3.3.0. The same deployment package works > for several other machines that we've tested. But this one machine will > not log the service messages to wrapper.log nor will our software log > using the log4j package. The log4j jar is in the classpath, but > regardless of whether it is or not, that shouldn't affect the > wrapper.log that the java-service-wrapper generates. > > The problem only exists when the wrapper is run as a service. When it > is run from the console, everything logs as normal. As a service, the > software runs, but nothing logs. > > My configuration file is below. > > Thanks, > Brandon > > #******************************************************************** > # Wrapper License Properties (Ignored by Community Edition) > #******************************************************************** > #include wrapper-license.conf > > #******************************************************************** > # Wrapper Java Properties > #******************************************************************** > # Java Application > wrapper.java.command=java > > wrapper.working.dir=.. > > # Java Main class. This class must implement the WrapperListener > interface > # or guarantee that the WrapperManager class is initialized. Helper > # classes are provided to do this for you. See the Integration section > # of the documentation for details. > wrapper.java.mainclass=thread.DetectorService > > > # Java Classpath (include wrapper.jar) Add class path elements as > # needed starting from 1 > wrapper.java.classpath.1=lib/jaxb/activation.jar > wrapper.java.classpath.2=lib/jaxb/jaxb-api.jar > wrapper.java.classpath.3=lib/jaxb/jaxb-impl.jar > wrapper.java.classpath.4=lib/jaxb/jaxb-xjc.jar > wrapper.java.classpath.5=lib/jaxb/jaxb1-impl.jar > wrapper.java.classpath.6=lib/jaxb/jsr173_1.0_api.jar > wrapper.java.classpath.7=lib/jdbcappender.jar > wrapper.java.classpath.8=lib/jms.jar > wrapper.java.classpath.9=lib/jta.jar > wrapper.java.classpath.10=lib/aqapi.jar > wrapper.java.classpath.11=lib/log4j-1.2.15.jar > wrapper.java.classpath.12=lib/ojdbc14.jar > wrapper.java.classpath.13=lib/weka.jar > wrapper.java.classpath.14=lib/xalan.jar > wrapper.java.classpath.15=lib/xercesImpl.jar > wrapper.java.classpath.16=lib/log4j-1.2.15.jar > wrapper.java.classpath.17=lib/commons-dbcp-1.2.2.jar > wrapper.java.classpath.18=lib/commons-pool-1.3.jar > wrapper.java.classpath.19=lib/util.jar > wrapper.java.classpath.20=resources > wrapper.java.classpath.21=lib/service-wrapper.jar > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=ServiceWrapper/lib > > # Java Additional Parameters > #wrapper.java.additional.1= > > # Initial Java Heap Size (in MB) > wrapper.java.initmemory=100 > > # Maximum Java Heap Size (in MB) > wrapper.java.maxmemory=1024 > > # Application parameters. Add parameters as needed starting from 1 > #wrapper.app.parameter.1= > > #******************************************************************** > # Wrapper Logging Properties > #******************************************************************** > # Format of output for the console. (See docs for formats) > wrapper.console.format=PM > > # Log Level for console output. (See docs for log levels) > wrapper.console.loglevel=DEBUG > > # Log file to use for wrapper output logging. > wrapper.logfile=ServiceWrapper/wrapper.log > > # Format of output for the log file. (See docs for formats) > wrapper.logfile.format=LPTM > > # Log Level for log file output. (See docs for log levels) > wrapper.logfile.loglevel=DEBUG > > # Maximum size that the log file will be allowed to grow to before > # the log is rolled. Size is specified in bytes. The default value > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > wrapper.logfile.maxsize=1m > > # Maximum number of rolled log files which will be allowed before old > # files are deleted. The default value of 0 implies no limit. > wrapper.logfile.maxfiles=10 > > # Log Level for sys/event log output. (See docs for log levels) > wrapper.syslog.loglevel=DEBUG > > #******************************************************************** > # Wrapper Windows Properties > #******************************************************************** > # Title to use when running as a console > wrapper.console.title=Dummy > > #******************************************************************** > # Wrapper Windows NT/2000/XP Service Properties > #******************************************************************** > # WARNING - Do not modify any of these properties when an application > # using this configuration file has been installed as a service. > # Please uninstall the service before modifying this section. The > # service can then be reinstalled. > > # Name of the service > wrapper.ntservice.name=Dummy > > # Display name of the service > wrapper.ntservice.displayname=Dummy > > # Description of the service > wrapper.ntservice.description= > > # Service dependencies. Add dependencies as needed starting from 1 > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > wrapper.ntservice.starttype=DEMAND_START > > # Allow the service to interact with the desktop. > wrapper.ntservice.interactive=false > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Borkholder, B. <bor...@me...> - 2008-05-29 23:04:31
|
I have a problem with logging under a Windows XP Pro installation using the 32bit community edition v3.3.0. The same deployment package works for several other machines that we've tested. But this one machine will not log the service messages to wrapper.log nor will our software log using the log4j package. The log4j jar is in the classpath, but regardless of whether it is or not, that shouldn't affect the wrapper.log that the java-service-wrapper generates. The problem only exists when the wrapper is run as a service. When it is run from the console, everything logs as normal. As a service, the software runs, but nothing logs. My configuration file is below. Thanks, Brandon #******************************************************************** # Wrapper License Properties (Ignored by Community Edition) #******************************************************************** #include wrapper-license.conf #******************************************************************** # Wrapper Java Properties #******************************************************************** # Java Application wrapper.java.command=java wrapper.working.dir=.. # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=thread.DetectorService # Java Classpath (include wrapper.jar) Add class path elements as # needed starting from 1 wrapper.java.classpath.1=lib/jaxb/activation.jar wrapper.java.classpath.2=lib/jaxb/jaxb-api.jar wrapper.java.classpath.3=lib/jaxb/jaxb-impl.jar wrapper.java.classpath.4=lib/jaxb/jaxb-xjc.jar wrapper.java.classpath.5=lib/jaxb/jaxb1-impl.jar wrapper.java.classpath.6=lib/jaxb/jsr173_1.0_api.jar wrapper.java.classpath.7=lib/jdbcappender.jar wrapper.java.classpath.8=lib/jms.jar wrapper.java.classpath.9=lib/jta.jar wrapper.java.classpath.10=lib/aqapi.jar wrapper.java.classpath.11=lib/log4j-1.2.15.jar wrapper.java.classpath.12=lib/ojdbc14.jar wrapper.java.classpath.13=lib/weka.jar wrapper.java.classpath.14=lib/xalan.jar wrapper.java.classpath.15=lib/xercesImpl.jar wrapper.java.classpath.16=lib/log4j-1.2.15.jar wrapper.java.classpath.17=lib/commons-dbcp-1.2.2.jar wrapper.java.classpath.18=lib/commons-pool-1.3.jar wrapper.java.classpath.19=lib/util.jar wrapper.java.classpath.20=resources wrapper.java.classpath.21=lib/service-wrapper.jar # Java Library Path (location of Wrapper.DLL or libwrapper.so) wrapper.java.library.path.1=ServiceWrapper/lib # Java Additional Parameters #wrapper.java.additional.1= # Initial Java Heap Size (in MB) wrapper.java.initmemory=100 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=1024 # Application parameters. Add parameters as needed starting from 1 #wrapper.app.parameter.1= #******************************************************************** # Wrapper Logging Properties #******************************************************************** # Format of output for the console. (See docs for formats) wrapper.console.format=PM # Log Level for console output. (See docs for log levels) wrapper.console.loglevel=DEBUG # Log file to use for wrapper output logging. wrapper.logfile=ServiceWrapper/wrapper.log # Format of output for the log file. (See docs for formats) wrapper.logfile.format=LPTM # Log Level for log file output. (See docs for log levels) wrapper.logfile.loglevel=DEBUG # Maximum size that the log file will be allowed to grow to before # the log is rolled. Size is specified in bytes. The default value # of 0, disables log rolling. May abbreviate with the 'k' (kb) or # 'm' (mb) suffix. For example: 10m = 10 megabytes. wrapper.logfile.maxsize=1m # Maximum number of rolled log files which will be allowed before old # files are deleted. The default value of 0 implies no limit. wrapper.logfile.maxfiles=10 # Log Level for sys/event log output. (See docs for log levels) wrapper.syslog.loglevel=DEBUG #******************************************************************** # Wrapper Windows Properties #******************************************************************** # Title to use when running as a console wrapper.console.title=Dummy #******************************************************************** # Wrapper Windows NT/2000/XP Service Properties #******************************************************************** # WARNING - Do not modify any of these properties when an application # using this configuration file has been installed as a service. # Please uninstall the service before modifying this section. The # service can then be reinstalled. # Name of the service wrapper.ntservice.name=Dummy # Display name of the service wrapper.ntservice.displayname=Dummy # Description of the service wrapper.ntservice.description= # Service dependencies. Add dependencies as needed starting from 1 wrapper.ntservice.dependency.1= # Mode in which the service is installed. AUTO_START or DEMAND_START wrapper.ntservice.starttype=DEMAND_START # Allow the service to interact with the desktop. wrapper.ntservice.interactive=false |
|
From: Leif M. <le...@ta...> - 2008-05-28 15:00:56
|
Bastian, The restarting functionality was designed to work around port locking problems on Solaris and other UNIX platforms. If Tomcat or some similar application crashed, the ports it had locked would stay locked for up to 2 minutes. This would cause an initial restart to sometimes fail. If the restarts continue to fail repeatedly then the Wrapper assumes that the problem is permanent and gives up. Looking at your wrapper.conf, it looks like you discovered both of the required properties: http://wrapper.tanukisoftware.org/doc/english/prop-max-failed-invocations.html http://wrapper.tanukisoftware.org/doc/english/prop-successful-invocation-time.html The first, wrapper.max_failed_invocations, configures how many failed restarts in a row will be allowed before the Wrapper gives up and exits. You can leave this at the default of 5. The second, wrapper.successful_invocation_time, sets the number of seconds that the JVM must be running before it is considered a successful invocation. If the invocation is successful, the above restart count will be reset. You want to choose a wrapper.successful_invocation_time value that is short enough that the count will always be reset if your application starts successfully, but long enough that it won't loop infinitely if you have a configuration error. This is something that you will have to try be seeing how long your program takes to run. Something like this: wrapper.successful_invocation_time=10 If you want to wait a while before launching the next JVM, you can do this as follows: wrapper.restart.delay=60 The above is all supported with the Community Edition. The Professional Edition also makes it possible to schedule cron job like restarts as follows: To restart every 15 seconds: ---- wrapper.timer.1.interval=second=*/15 wrapper.timer.1.action=RESTART ---- To restart every night at 4:30am: ---- wrapper.timer.1.interval=hour=4; minute=30; wrapper.timer.1.action=RESTART ---- To restart every Monday night at 4:30am: ---- wrapper.timer.1.interval=day-of-week=1; hour=4; minute=30; wrapper.timer.1.action=RESTART ---- Hope this helps, Cheers, Leif Bastian Schurr wrote: > Hi, > i have a service which should be restarted after running every time to avoide storage problems in my JVM. So after doing its normal work WrapperManager.restart() is called and JVM should be resetted. > > But after 5 restarts I got the following output in my wrapper logfile > > ... > STATUS | wrapper | 2008/05/27 08:15:33 | JVM requested a restart. > FATAL | wrapper | 2008/05/27 08:15:35 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. > FATAL | wrapper | 2008/05/27 08:15:35 | There may be a configuration problem: please check the logs. > STATUS | wrapper | 2008/05/27 08:15:35 | <-- Wrapper Stopped > > and my wrapper doesn't restart anymore. I have to run the install.bat file to get a new wrapper. > > I know the key "wrapper.max_failed_invocations", but increasing this key will only hide the problem of failed launches. I have also tested setting the key "wrapper.restart.delay" from 5 to 10 seconds but this dosn't change anything. > > --> What can I do to get no failed launches in the wrapper or to restart my JVM as often I want? > > Here is a short view to my application: > > public class RemoteMain implements WrapperListener { > ... > public static void main(String[] args){ > try { > WrapperManager.start(new RemoteEncoMain(), args); > } catch (Exception e){e.printStrackTrace()} > } > > public Integer start(String[] args) { > //create a ServerController > serverController = new ServerController(showTrayIcon); > > //initialize the services for this ServerController > initCajoService(args); > > try { > serverController.startServer(cajoPort, iconString); > } catch (Exception e) {e.printStrackTrace()} > } > ... > } > > > public class ServerController{ > ... > > //this is my service > public AbstractService service; > > //the startServer method called from start > public void startServer(int serverPort, String iconString) throws UnknownHostException, RemoteException { > if (showTrayIcon) { > new TrayIconManager().initTrayIcon(iconString, serverPort); > } > CajoReceiver.initServer(serverPort); > > // bind services as cajo service > CajoReceiver.bindService(service, service.getServiceName()); > } > > ... > } > > This is my configuration file: > #******************************************************************** > # Service Wrapper Properties > # > #******************************************************************** > # Java Application > wrapper.java.command=C:/jre1.5.0_12/bin/java > > # Java Main class. This class must implement the WrapperListener interface > # or guarantee that the WrapperManager class is initialized. Helper > # classes are provided to do this for you. See the Integration section > # of the documentation for details. > wrapper.java.mainclass=de.server.RemoteMain > > > set.MYAPP_HOME=C:/myapp > > # Java Classpath (include wrapper.jar) Add class path elements as > # needed starting from 1 > ... > > > # Java Library Path (location of Wrapper.DLL or libwrapper.so) > wrapper.java.library.path.1=%MYAPP_HOME%/sys/win32/lib > > # Java Additional Parameters > wrapper.java.additional.1=-DPLM++WORKDIR=C:\Temp_Server\ > wrapper.java.additional.2=-DPLM++USE_FS=FALSE > wrapper.java.additional.3=-DPLM++USE_READONLY=true > wrapper.java.additional.4=-Dsystem.start.instdir=C:\myapp > wrapper.java.additional.5=-Dsystem.start.bindir=C:\myapp\sys\win32\bin > wrapper.java.additional.6=-Dsystem.start.datadir=C:\myapp\data > wrapper.java.additional.7=-Dsystem.start.tmpdir=C:\Temp_Server\ > wrapper.java.additional.8=-Dsystem.start.custpref=default.txt > wrapper.java.additional.9=-Djava.library.path=C:\myapp\sys\win32\lib > wrapper.java.additional.10=-DPLM++AUTO_START_OM=false > wrapper.java.additional.11=-Dsystem.log.console=yes > wrapper.java.additional.12=-DPLM++OML=7506 > wrapper.java.additional.13=-DPLM++LANGUAGE=DE > wrapper.java.additional.14=-Xmx512M > wrapper.java.additional.15=-Xms64M > > # Initial Java Heap Size (in MB) > wrapper.java.initmemory=64 > > # Maximum Java Heap Size (in MB) > wrapper.java.maxmemory=512 > > # Application parameters. Add parameters as needed starting from 1 > wrapper.app.parameter.1=TRAYICON > wrapper.app.parameter.2=CAJOSERVER > wrapper.app.parameter.3=1198 > wrapper.app.parameter.4=server.ico > > #******************************************************************** > # Wrapper Logging Properties > #******************************************************************** > # Format of output for the console. (default: PM) > wrapper.console.format=PM > > # Log level for console output. (default: INFO) > wrapper.console.loglevel=INFO > > # Log file to use for wrapper output logging. > wrapper.logfile=../logs/wrapper_server_ROLLNUM.log > > # Format of output for the log file. (default: LPTM) > wrapper.logfile.format=LPDTM > > # Log level for log file output. (default: INFO) > wrapper.logfile.loglevel=INFO > > # Maximum size that the log file will be allowed to grow to before > # the log is rolled. Size is specified in bytes. The default value > # of 0, disables log rolling. May abbreviate with the 'k' (kb) or > # 'm' (mb) suffix. For example: 10m = 10 megabytes. > wrapper.logfile.maxsize=10m > > # Maximum number of rolled log files which will be allowed before old > # files are deleted. The default value of 0 implies no limit. > wrapper.logfile.maxfiles=10 > > # Log level for sys/event log output. (default: NONE) > wrapper.syslog.loglevel=NONE > > > #******************************************************************** > # Wrapper Windows Properties > #******************************************************************** > # Title to use when running as a console > wrapper.console.title=MyAPP Server > > #******************************************************************** > # Wrapper Windows NT/2000/XP Service Properties > #******************************************************************** > # WARNING - Do not modify any of these properties when an application > # using this configuration file has been installed as a service. > # Please uninstall the service before modifying this section. The > # service can then be reinstalled. > > # Name of the service > wrapper.ntservice.name=myapp_server > > # Display name of the service > wrapper.ntservice.displayname=MyApp Server > > # Description of the service > wrapper.ntservice.description=MyApp Server > > # Service dependencies. Add dependencies as needed starting from 1 > wrapper.ntservice.dependency.1= > > # Mode in which the service is installed. AUTO_START or DEMAND_START > wrapper.ntservice.starttype=DEMAND_START > > # Allow the service to interact with the desktop. > wrapper.ntservice.interactive=true > > #******************************************************************** > # Wrapper Restart Properties > #******************************************************************** > > # Controls whether or not the Wrapper configuration file will be > # reloaded in the event of a JVM restart. (default: FALSE) > wrapper.restart.reload_configuration=TRUE > > # Controls the number of seconds to pause between a JVM exiting for > # any reason, and a new JVM being launched. (default: 5) > wrapper.restart.delay=10 > > # Maximum number of times that the Wrapper will attempt to restart > # the JVM if each attempted invocation exits abnormally or is > # restarted shortly after having being launched. (default: 5) > # > # If the JVM was running for a period longer than the value set in > # the wrapper.successful_invocation_time property, then the restart > # count will be reset to 0. So this count only applies to JVM > # invocations which fail on startup. > wrapper.max_failed_invocations=5 > > # Specifies the amount of time that an application must remain > # running before it will be considered to have been a successful > # invocation. (default: 300) > wrapper.successful_invocation_time=300 > > # This property makes it possible to control whether or not multiple > # invocations of a given application can be run at the same time. > # (default: FALSE) > wrapper.single_invocation=FALSE > > > #******************************************************************** > # Wrapper Debug Properties > #******************************************************************** > > # Used to quickly enable debug logging both to the console and log > # file. Disabling this flag does not disable debug logging to the > # console or log file. (default: FALSE) > wrapper.debug=TRUE > #******************************************************************** > |
165 messages has been excluded from this view by a project administrator.
