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: Leif M. <lei...@ta...> - 2010-06-10 08:38:27
|
Javier, Thank you for that information. If the wrapper.log is never being written then that most likely means that the Windows Service Manager is failing to ever launch the wrapper.exe binary as a service. This can happen if the SYSTEM user does not have access to the directory where the Wrapper.exe binary is located. Could you please check the file permissions on all of the parent directories as well and make sure that they have at least read access for the SYSTEM user? The logs directory will also need to have write access. Cheers, Leif On Thu, Jun 10, 2010 at 5:30 PM, Javier Muguruza <jav...@at...> wrote: > Replays to both of you guys inline, thanks: > > > > Hi, > > How does it fail, on what point does it fail? Windows Service cannot be > started, it is working on the same environment with a x86 jdk (and > wrapper-windows-x86-32-3.3.0) using the same config, and Path to executable > Path to executable: C:\ADAM\adam\wrapper-bin\wrapper.exe -s > C:\ADAM\adam\wrapper-conf\ManagerProcess.conf > > If launched directly through a command line like > C:\ADAM\adam\wrapper-bin\wrapper.exe > C:\ADAM\adam\wrapper-conf\ManagerProcess.conf it starts properly > > Do you have Wrapper Debug Settings enabled to generate verbose output? > > Do you use network resources like mapped drives or unc path? No, everything > is on local drive, no mapped drive > > Do you use any resource that is only available to "regular" windows > > users like printers? No > > Do you try access a regular windows users environment? We try to access a > few environment variables, but they are all available globally. > > Hubert > > > > Christian. > > > > > > you can send support requests over this mailing list as well as > > directly sending to su...@ta... > > > > Hubert already pointed you to possible problems when starting as a service. > > > > Let me add some additional questions: > > If the wrapper fails to start as service with the local system user, > > could you check if there is a log file "wrapper.log" in the folder the > > wrapper binary is located? > > No wrapper.log file is left on the bin folder. > > > > Could you also try to start the service from Console (you need to > > start the console as admin) and run the Start<App>.bat file? What > > output message from the wrapper can you see there? > > It also fails, > > C:\ADAM\adam\wrapper-bin>StartTestWrapper-NT.bat > ..\wrapper-conf\ManagerProcess. > > conf > > wrapper | Working directory set to: C:\ADAM\adam\mig-master > > wrapper | Starting the adam-ManagerProcess service... > > wrapper | Waiting to start... > > wrapper | The adam-ManagerProcess service was launched, but failed to > start. > > Press any key to continue . . . > > > > Launching directly the wrapper.exe it works > > C:\ADAM\adam\wrapper-bin>wrapper.exe ..\wrapper-conf\ManagerProcess.conf > > wrapper | Working directory set to: C:\ADAM\adam\mig-master > > wrapper | --> Wrapper Started as Console > > wrapper | Java Service Wrapper Standard Edition 3.3.0 > > wrapper | Copyright (C) 1999-2008 Tanuki Software, Inc. All Rights > Reserved. > > > > wrapper | http://wrapper.tanukisoftware.org > > wrapper | Licensed to Atempo Java Service Wrapper for ADAM Manager > > > > > > > > Sincerely, > > Christian > |
|
From: Javier M. <jav...@at...> - 2010-06-10 08:29:18
|
Replays to both of you guys inline, thanks: Hi, How does it fail, on what point does it fail? Windows Service cannot be started, it is working on the same environment with a x86 jdk (and wrapper-windows-x86-32-3.3.0) using the same config, and Path to executable Path to executable: C:\ADAM\adam\wrapper-bin\wrapper.exe -s C:\ADAM\adam\wrapper-conf\ManagerProcess.conf If launched directly through a command line like C:\ADAM\adam\wrapper-bin\wrapper.exe C:\ADAM\adam\wrapper-conf\ManagerProcess.conf it starts properly Do you have Wrapper Debug Settings enabled to generate verbose output? Do you use network resources like mapped drives or unc path? No, everything is on local drive, no mapped drive Do you use any resource that is only available to "regular" windows users like printers? No Do you try access a regular windows users environment? We try to access a few environment variables, but they are all available globally. Hubert Christian. you can send support requests over this mailing list as well as directly sending to su...@ta...<mailto:su...@ta...> Hubert already pointed you to possible problems when starting as a service. Let me add some additional questions: If the wrapper fails to start as service with the local system user, could you check if there is a log file "wrapper.log" in the folder the wrapper binary is located? No wrapper.log file is left on the bin folder. Could you also try to start the service from Console (you need to start the console as admin) and run the Start<App>.bat file? What output message from the wrapper can you see there? It also fails, C:\ADAM\adam\wrapper-bin>StartTestWrapper-NT.bat ..\wrapper-conf\ManagerProcess. conf wrapper | Working directory set to: C:\ADAM\adam\mig-master wrapper | Starting the adam-ManagerProcess service... wrapper | Waiting to start... wrapper | The adam-ManagerProcess service was launched, but failed to start. Press any key to continue . . . Launching directly the wrapper.exe it works C:\ADAM\adam\wrapper-bin>wrapper.exe ..\wrapper-conf\ManagerProcess.conf wrapper | Working directory set to: C:\ADAM\adam\mig-master wrapper | --> Wrapper Started as Console wrapper | Java Service Wrapper Standard Edition 3.3.0 wrapper | Copyright (C) 1999-2008 Tanuki Software, Inc. All Rights Reserved. wrapper | http://wrapper.tanukisoftware.org wrapper | Licensed to Atempo Java Service Wrapper for ADAM Manager Sincerely, Christian |
|
From: Leif M. <lei...@ta...> - 2010-06-10 05:49:07
|
Rob, Thank you for the feedback. I think we are set then with the implemented UDP based syslog implementation. It will be released in 3.5.0 at the end of June. The specification that we implemented to places a maximum packet size of 1024 bytes including all headers. When viewed in the syslog output on a linux server, it looks like this for a very long line. The following output was a test of a 200 byte packet length. We add "..." to the beginning and end of long wrapped lines and trim them exactly to the max packet length: --- Jun 9 04:18:26 io-2.local io testwrapper: jvm 1 : sun.boot.class.path=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsfd.jar:/System/Library/Frameworks/JavaVM.framework/Versions/... Jun 9 04:18:26 io-2.local io testwrapper: jvm 1 : ...1.5.0/Classes/classes.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar:/System/Library/Frameworks/JavaVM.framework/... Jun 9 04:18:26 io-2.local io testwrapper: jvm 1 : ...Versions/1.5.0/Classes/laf.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/sunrsasign.jar:/System/Library/Frameworks/Java... Jun 9 04:18:26 io-2.local io testwrapper: jvm 1 : ...VM.framework/Versions/1.5.0/Classes/jsse.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar:/System/Library/Framewor... Jun 9 04:18:26 io-2.local io testwrapper: jvm 1 : ...ks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar --- We are not planning on making the packet length configurable as the specification is pretty clear. Let me know what you think. It is actually easy to make it configurable. But allowing it to be so could cause problems on the log servers or relays. Cheers, Leif On Wed, Jun 9, 2010 at 5:54 AM, Leland, Robert <rob...@io...> wrote: > My experience is as a user of several SYSLOG-NG implementation not as an implementer. Unless it is a much requested feature I would stay away from a TCP client implementation, and I have experience varying incompatibilities of servers as to how they handle things. This has resulted in Dropped logs(even in TCP), truncated logs, and multiple/compound log entries in one SYSLOG database entry. > > Even though SYSLOG is over TCP the, and a message length is in the TCP header, the SYSLOG-NG v2 protocol did not have a concept of message length and still depended on message delimiters. > I believe SYSLOG-NG V3 which is based on http://tools.ietf.org/html/rfc5424, was scheduled to make use of a message length to make implementing the Client and Server more standard. > > > This is off topic but..... > My experience is that some applications misuse SYSLOG for non events, that is better served with a application auditing. The things I look for that usually rules out SYSLOG usage (TCP or UDP) are: > Large message Size > 4K (1K). > The application wants to send a complex payload such as XML. > The desire to run real time metrics against the SYSLOG server for reports over log time periods. > The SYSLOG servers I have seen store the SYSLOG into a generic database which make sense. > To produce a report each log entry has to be first filtered by time or some other generic criteria, then parsed into an intermediated database table(s) that then is sent to a reporting tool such as Crystal Reports or OBIEE. Each time a report is generated the same process is repeated. Many SYSLOG implementations do not optimize their use of memory and choke when generating reports over long time periods(several months). Just some things to consider > > -Rob > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Tuesday, June 08, 2010 4:03 PM > To: wra...@li... > Subject: Re: [Wrapper-user] wrapper with syslog host > > Robert, > Thank you for the extra info. I got a UDP based syslog target working > that is based on RFC3164 (http://www.ietf.org/rfc/rfc3164.txt) It > limits the message length to 1024 characters. Lines that are longer > than that will be wrapper into multiple packets. > > It still needs a lot of testing, but we will have this in the 3.5.0 > release due out by the end of June. > > Will this be sufficient? TCP based logging would be a bit more > difficult to handle because of the possibility that the outgoing > packets could block. > > Cheers, > Leif > > On Wed, Jun 9, 2010 at 3:37 AM, Leland, Robert <rob...@io...> wrote: >> It might be helpful to be specific as to the type of SYSLOG server >> support is desired. >> >> The UDP based SYSLOG is easiest to support since there is a standard. >> >> As far as the TCP SYSLOG it's been 18 months worked with that and then >> there was no SYSLOG standard over Connected TCP networks. The closest to >> that is a open source/commercial product that others seem to follow. >> The SYSLOG-TCP or SYSLOG-NG servers that exist all behave very >> differently. >> Since the pseudo standard was based on the UDP version 18 months ago >> most if not all still had a message size limit that varies from 1K to 4K >> depending on the implementation. They also vary on how they piece >> together messages. >> >> >> -----Original Message----- >> From: Leif Mortenson [mailto:lei...@ta...] >> Sent: Tuesday, June 08, 2010 11:51 AM >> To: wra...@li... >> Subject: Re: [Wrapper-user] wrapper with syslog host >> >> Gerald, >> Sorry for the delay on this. We were investigating what is possible >> at an OS level as well as the possibility of sending the remote syslog >> messages directly. The Wrapper does not currently support this. >> Please confirm that you are wanting to send the Wrapper's output to a >> remote syslog server directly, and not all of the syslog activity on >> the server. >> >> Cheers, >> Leif >> >> On Sat, Jun 5, 2010 at 12:09 AM, Gerald Schnabel >> <ger...@gm...> wrote: >>> hi, >>> I am using a syslog server, which is running on a separate machine. >> Most applications I use are configured with log4j >>> where I can use a syslog appender with the parameter SyslogHost. >>> But for the java service wrapper I can just find the properties >>> >>> wrapper.syslog.facility >>> wrapper.syslog.ident >>> wrapper.syslog.loglevel >>> >>> How can I configure the java service wrapper for using the syslog >> server? >>> >>> Thanks in advance, >>> Gerald |
|
From: Christian M. <chr...@ta...> - 2010-06-10 01:44:47
|
Javier, you can send support requests over this mailing list as well as directly sending to su...@ta... Hubert already pointed you to possible problems when starting as a service. Let me add some additional questions: If the wrapper fails to start as service with the local system user, could you check if there is a log file "wrapper.log" in the folder the wrapper binary is located? Could you also try to start the service from Console (you need to start the console as admin) and run the Start<App>.bat file? What output message from the wrapper can you see there? Sincerely, Christian On Thu, Jun 10, 2010 at 3:50 AM, Hubert Felber <Hub...@ab...> wrote: > Hi, > How does it fail, on what point does it fail? > Do you have Wrapper Debug Settings enabled to generate verbose output? > Do you use network resources like mapped drives or unc path? > Do you use any resource that is only available to "regular" windows > users like printers? > Do you try access a regular windows users environment? > Hubert > > >>>> Javier Muguruza <jav...@at...> 09.06.2010 20:44 >>> > Hi, > > we have an issue in this environment: > > Windows 2008R1 64bits > jdk 64b (1.6.0_21) > wrapper-windows-x86-64-3.3.0-st > > We create a service with InstallTestWrapper-NT.bat etc, it gets created > with Local System account by default. We try to start this service but > it fails stragith away, enabling debug does not show anything, in the > event viewer there is an event but without any useful information. > > If we change the Log On user for the service to Administrator, the > service starts fine. > > Does anyone know what could it be? > > Thanks > Javier > > BTW, is this the right place for support (having a license?) > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |
|
From: Hubert F. <Hub...@ab...> - 2010-06-09 19:19:27
|
Hi, How does it fail, on what point does it fail? Do you have Wrapper Debug Settings enabled to generate verbose output? Do you use network resources like mapped drives or unc path? Do you use any resource that is only available to "regular" windows users like printers? Do you try access a regular windows users environment? Hubert >>> Javier Muguruza <jav...@at...> 09.06.2010 20:44 >>> Hi, we have an issue in this environment: Windows 2008R1 64bits jdk 64b (1.6.0_21) wrapper-windows-x86-64-3.3.0-st We create a service with InstallTestWrapper-NT.bat etc, it gets created with Local System account by default. We try to start this service but it fails stragith away, enabling debug does not show anything, in the event viewer there is an event but without any useful information. If we change the Log On user for the service to Administrator, the service starts fine. Does anyone know what could it be? Thanks Javier BTW, is this the right place for support (having a license?) ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Javier M. <jav...@at...> - 2010-06-09 18:45:26
|
Hi, we have an issue in this environment: Windows 2008R1 64bits jdk 64b (1.6.0_21) wrapper-windows-x86-64-3.3.0-st We create a service with InstallTestWrapper-NT.bat etc, it gets created with Local System account by default. We try to start this service but it fails stragith away, enabling debug does not show anything, in the event viewer there is an event but without any useful information. If we change the Log On user for the service to Administrator, the service starts fine. Does anyone know what could it be? Thanks Javier BTW, is this the right place for support (having a license?) |
|
From: Leland, R. <rob...@io...> - 2010-06-08 20:54:20
|
My experience is as a user of several SYSLOG-NG implementation not as an implementer. Unless it is a much requested feature I would stay away from a TCP client implementation, and I have experience varying incompatibilities of servers as to how they handle things. This has resulted in Dropped logs(even in TCP), truncated logs, and multiple/compound log entries in one SYSLOG database entry. Even though SYSLOG is over TCP the, and a message length is in the TCP header, the SYSLOG-NG v2 protocol did not have a concept of message length and still depended on message delimiters. I believe SYSLOG-NG V3 which is based on http://tools.ietf.org/html/rfc5424, was scheduled to make use of a message length to make implementing the Client and Server more standard. This is off topic but..... My experience is that some applications misuse SYSLOG for non events, that is better served with a application auditing. The things I look for that usually rules out SYSLOG usage (TCP or UDP) are: Large message Size > 4K (1K). The application wants to send a complex payload such as XML. The desire to run real time metrics against the SYSLOG server for reports over log time periods. The SYSLOG servers I have seen store the SYSLOG into a generic database which make sense. To produce a report each log entry has to be first filtered by time or some other generic criteria, then parsed into an intermediated database table(s) that then is sent to a reporting tool such as Crystal Reports or OBIEE. Each time a report is generated the same process is repeated. Many SYSLOG implementations do not optimize their use of memory and choke when generating reports over long time periods(several months). Just some things to consider -Rob -----Original Message----- From: Leif Mortenson [mailto:lei...@ta...] Sent: Tuesday, June 08, 2010 4:03 PM To: wra...@li... Subject: Re: [Wrapper-user] wrapper with syslog host Robert, Thank you for the extra info. I got a UDP based syslog target working that is based on RFC3164 (http://www.ietf.org/rfc/rfc3164.txt) It limits the message length to 1024 characters. Lines that are longer than that will be wrapper into multiple packets. It still needs a lot of testing, but we will have this in the 3.5.0 release due out by the end of June. Will this be sufficient? TCP based logging would be a bit more difficult to handle because of the possibility that the outgoing packets could block. Cheers, Leif On Wed, Jun 9, 2010 at 3:37 AM, Leland, Robert <rob...@io...> wrote: > It might be helpful to be specific as to the type of SYSLOG server > support is desired. > > The UDP based SYSLOG is easiest to support since there is a standard. > > As far as the TCP SYSLOG it's been 18 months worked with that and then > there was no SYSLOG standard over Connected TCP networks. The closest to > that is a open source/commercial product that others seem to follow. > The SYSLOG-TCP or SYSLOG-NG servers that exist all behave very > differently. > Since the pseudo standard was based on the UDP version 18 months ago > most if not all still had a message size limit that varies from 1K to 4K > depending on the implementation. They also vary on how they piece > together messages. > > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Tuesday, June 08, 2010 11:51 AM > To: wra...@li... > Subject: Re: [Wrapper-user] wrapper with syslog host > > Gerald, > Sorry for the delay on this. We were investigating what is possible > at an OS level as well as the possibility of sending the remote syslog > messages directly. The Wrapper does not currently support this. > Please confirm that you are wanting to send the Wrapper's output to a > remote syslog server directly, and not all of the syslog activity on > the server. > > Cheers, > Leif > > On Sat, Jun 5, 2010 at 12:09 AM, Gerald Schnabel > <ger...@gm...> wrote: >> hi, >> I am using a syslog server, which is running on a separate machine. > Most applications I use are configured with log4j >> where I can use a syslog appender with the parameter SyslogHost. >> But for the java service wrapper I can just find the properties >> >> wrapper.syslog.facility >> wrapper.syslog.ident >> wrapper.syslog.loglevel >> >> How can I configure the java service wrapper for using the syslog > server? >> >> Thanks in advance, >> Gerald ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Leif M. <lei...@ta...> - 2010-06-08 20:03:38
|
Robert, Thank you for the extra info. I got a UDP based syslog target working that is based on RFC3164 (http://www.ietf.org/rfc/rfc3164.txt) It limits the message length to 1024 characters. Lines that are longer than that will be wrapper into multiple packets. It still needs a lot of testing, but we will have this in the 3.5.0 release due out by the end of June. Will this be sufficient? TCP based logging would be a bit more difficult to handle because of the possibility that the outgoing packets could block. Cheers, Leif On Wed, Jun 9, 2010 at 3:37 AM, Leland, Robert <rob...@io...> wrote: > It might be helpful to be specific as to the type of SYSLOG server > support is desired. > > The UDP based SYSLOG is easiest to support since there is a standard. > > As far as the TCP SYSLOG it's been 18 months worked with that and then > there was no SYSLOG standard over Connected TCP networks. The closest to > that is a open source/commercial product that others seem to follow. > The SYSLOG-TCP or SYSLOG-NG servers that exist all behave very > differently. > Since the pseudo standard was based on the UDP version 18 months ago > most if not all still had a message size limit that varies from 1K to 4K > depending on the implementation. They also vary on how they piece > together messages. > > > -----Original Message----- > From: Leif Mortenson [mailto:lei...@ta...] > Sent: Tuesday, June 08, 2010 11:51 AM > To: wra...@li... > Subject: Re: [Wrapper-user] wrapper with syslog host > > Gerald, > Sorry for the delay on this. We were investigating what is possible > at an OS level as well as the possibility of sending the remote syslog > messages directly. The Wrapper does not currently support this. > Please confirm that you are wanting to send the Wrapper's output to a > remote syslog server directly, and not all of the syslog activity on > the server. > > Cheers, > Leif > > On Sat, Jun 5, 2010 at 12:09 AM, Gerald Schnabel > <ger...@gm...> wrote: >> hi, >> I am using a syslog server, which is running on a separate machine. > Most applications I use are configured with log4j >> where I can use a syslog appender with the parameter SyslogHost. >> But for the java service wrapper I can just find the properties >> >> wrapper.syslog.facility >> wrapper.syslog.ident >> wrapper.syslog.loglevel >> >> How can I configure the java service wrapper for using the syslog > server? >> >> Thanks in advance, >> Gerald |
|
From: Leland, R. <rob...@io...> - 2010-06-08 18:59:36
|
It might be helpful to be specific as to the type of SYSLOG server support is desired. The UDP based SYSLOG is easiest to support since there is a standard. As far as the TCP SYSLOG it's been 18 months worked with that and then there was no SYSLOG standard over Connected TCP networks. The closest to that is a open source/commercial product that others seem to follow. The SYSLOG-TCP or SYSLOG-NG servers that exist all behave very differently. Since the pseudo standard was based on the UDP version 18 months ago most if not all still had a message size limit that varies from 1K to 4K depending on the implementation. They also vary on how they piece together messages. -----Original Message----- From: Leif Mortenson [mailto:lei...@ta...] Sent: Tuesday, June 08, 2010 11:51 AM To: wra...@li... Subject: Re: [Wrapper-user] wrapper with syslog host Gerald, Sorry for the delay on this. We were investigating what is possible at an OS level as well as the possibility of sending the remote syslog messages directly. The Wrapper does not currently support this. Please confirm that you are wanting to send the Wrapper's output to a remote syslog server directly, and not all of the syslog activity on the server. Cheers, Leif On Sat, Jun 5, 2010 at 12:09 AM, Gerald Schnabel <ger...@gm...> wrote: > hi, > I am using a syslog server, which is running on a separate machine. Most applications I use are configured with log4j > where I can use a syslog appender with the parameter SyslogHost. > But for the java service wrapper I can just find the properties > > wrapper.syslog.facility > wrapper.syslog.ident > wrapper.syslog.loglevel > > How can I configure the java service wrapper for using the syslog server? > > Thanks in advance, > Gerald ------------------------------------------------------------------------ ------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Gerald S. <ger...@gm...> - 2010-06-08 16:26:52
|
Hi Leif, thanks for the answer. > Please confirm that you are wanting to send the Wrapper's output to a > remote syslog server directly, and not all of the syslog activity on > the server. That is exactly what I want, just the output from the wrapper should be sended to a remote syslog server. I don't want to configure the syslog deamon on every server to filter the application messages and on the syslog server other developer get easy access to the logfiles. Thanks for you help. Cheers, Gerald |
|
From: Leif M. <lei...@ta...> - 2010-06-08 15:57:17
|
Gerald, Sorry for the delay on this. We were investigating what is possible at an OS level as well as the possibility of sending the remote syslog messages directly. The Wrapper does not currently support this. Please confirm that you are wanting to send the Wrapper's output to a remote syslog server directly, and not all of the syslog activity on the server. Cheers, Leif On Sat, Jun 5, 2010 at 12:09 AM, Gerald Schnabel <ger...@gm...> wrote: > hi, > I am using a syslog server, which is running on a separate machine. Most applications I use are configured with log4j > where I can use a syslog appender with the parameter SyslogHost. > But for the java service wrapper I can just find the properties > > wrapper.syslog.facility > wrapper.syslog.ident > wrapper.syslog.loglevel > > How can I configure the java service wrapper for using the syslog server? > > Thanks in advance, > Gerald |
|
From: Gerald S. <ger...@gm...> - 2010-06-04 15:09:34
|
hi, I am using a syslog server, which is running on a separate machine. Most applications I use are configured with log4j where I can use a syslog appender with the parameter SyslogHost. But for the java service wrapper I can just find the properties wrapper.syslog.facility wrapper.syslog.ident wrapper.syslog.loglevel How can I configure the java service wrapper for using the syslog server? Thanks in advance, Gerald |
|
From: Leif M. <lei...@ta...> - 2010-06-01 16:35:40
|
Justin, We have run several tests and made some modifications to make the Wrapper a bit more responsive in the event that the backend socket is ever closed externally. These changes will be in the next release. This is will not be all that helpful for you however as your application is failing to start back up and after the restart. Most likely the reason is can't be restarted is related to the reason why the backend socket was closed in the first place. The way the Wrapper is failing to send any data back to the JVM AFTER the Wrapper has been restarted once is quite odd. Is it possible that McAfee or a firewall is somehow deciding to lock down the Wrapper or Java processes? Everything else appears to be working as expected. Please take a look at McAfee on your end, and we will try to think of other possible causes. Cheers, Leif On Tue, Jun 1, 2010 at 3:02 PM, Justin Maguire <jma...@gm...> wrote: > Hello Leif, > > The successful start up was after a phyical server reboot, everything else > is before. We have disabled the virus scanner McAfee but I will double check > that the IT team disabled it or jsut disabled some parts of it :) > > I will also escalate here to development as to why that error was throwing > in the Application to help further troubleshoot this. I am all for the > upgrading to the latest and greatest I will see if we can get this done. > > The machine is a 64bit windows server with 32gb of memory, but I will double > check the resources next time the error occurs just in case. > > Thanks for the insight and explainations this has help me better understand > the problem. > > > Thanks! > Justin -- Leif Mortenson Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel/Fax: +81-3-3878-3211 http://www.tanukisoftware.com lei...@ta... |
|
From: Justin M. <jma...@gm...> - 2010-06-01 06:02:19
|
Hello Leif, The successful start up was after a phyical server reboot, everything else is before. We have disabled the virus scanner McAfee but I will double check that the IT team disabled it or jsut disabled some parts of it :) I will also escalate here to development as to why that error was throwing in the Application to help further troubleshoot this. I am all for the upgrading to the latest and greatest I will see if we can get this done. The machine is a 64bit windows server with 32gb of memory, but I will double check the resources next time the error occurs just in case. Thanks for the insight and explainations this has help me better understand the problem. Thanks! Justin |
|
From: Leif M. <lei...@ta...> - 2010-06-01 03:32:01
|
Justin, The problem starts when the backend socket gets closed somehow. It is a loopback socket so this should not be happening unless it is being closed explicitly --- INFO | jvm 1 | 2010/06/01 08:37:00 | Closed socket: java.net.SocketException: Software caused connection abort: recv failed INFO | jvm 1 | 2010/06/01 08:37:00 | Closing socket. --- Do have any ideas as to what on your system could have closed the socket? The first time, the Wrapper process was listening on port 32001, but when its connection with the JVM is lost, it is switching over and starts listening on port 32002 instead. At this point, it would be impossible for the JVM to reconnect so the JVM ends up being killed as unresponsive: --- ERROR | wrapper | 2010/06/01 08:42:04 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2010/06/01 08:42:04 | JVM did not exit on request, terminated --- The Wrapper is then restarting the JVM correctly. But the second JVM instance is failing with an application level error: --- INFO | jvm 2 | 2010/06/01 08:42:11 | Received error while starting the application. INFO | jvm 2 | 2010/06/01 08:42:11 | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'discoveryService' defined in class path resource [jps-config.xml]: Invocation of init method failed; nested exception is org.omg.CORBA.COMM_FAILURE: An exception was thrown while waiting for a reply from the peer. vmcid: 0x0 minor code: 0 completed: No INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1337) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409) INFO | jvm 2 | 2010/06/01 08:42:11 | at java.security.AccessController.doPrivileged(Native Method) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:221) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:423) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:729) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:381) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.framework.services.bootstrap.SASRemoteServices.main(SASRemoteServices.java:63) INFO | jvm 2 | 2010/06/01 08:42:11 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) INFO | jvm 2 | 2010/06/01 08:42:11 | at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) INFO | jvm 2 | 2010/06/01 08:42:11 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) INFO | jvm 2 | 2010/06/01 08:42:11 | at java.lang.reflect.Method.invoke(Unknown Source) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240) INFO | jvm 2 | 2010/06/01 08:42:11 | at java.lang.Thread.run(Unknown Source) INFO | jvm 2 | 2010/06/01 08:42:11 | Caused by: org.omg.CORBA.COMM_FAILURE: An exception was thrown while waiting for a reply from the peer. vmcid: 0x0 minor code: 0 completed: No INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.iom.orb.brg.Engine.waitForReply(Engine.java:1869) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.iom.orb.brg.Engine.sendRequest(Engine.java:805) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.iom.orb.brg.RequestImpl.invoke(RequestImpl.java:33) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.meta.SASOMI._portable_stub_IOMI.DoRequest(_portable_stub_IOMI.java:569) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.services.deployment.OMRMetadataSource.getMetadata(OMRMetadataSource.java:1091) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.services.deployment.OMRMetadataSource.getMetadataToDeployServices(OMRMetadataSource.java:1018) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.services.deployment.ServiceLoader.deployServices(ServiceLoader.java:846) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.services.deployment.PlatformServices.startLocalServices(PlatformServices.java:524) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.services.deployment.PlatformServices.startServices(PlatformServices.java:479) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.services.deployment.CorePlatformServices.startServices(CorePlatformServices.java:153) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.framework.services.PlatformDiscoveryServiceFactoryBean.afterPropertiesSet(PlatformDiscoveryServiceFactoryBean.java:100) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1368) INFO | jvm 2 | 2010/06/01 08:42:11 | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1334) INFO | jvm 2 | 2010/06/01 08:42:11 | ... 21 more INFO | jvm 2 | 2010/06/01 08:42:11 | Caused by: java.io.IOException: An established connection was aborted by the software in your host machine INFO | jvm 2 | 2010/06/01 08:42:11 | at sun.nio.ch.SocketDispatcher.read0(Native Method) INFO | jvm 2 | 2010/06/01 08:42:11 | at sun.nio.ch.SocketDispatcher.read(Unknown Source) INFO | jvm 2 | 2010/06/01 08:42:11 | at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) INFO | jvm 2 | 2010/06/01 08:42:11 | at sun.nio.ch.IOUtil.read(Unknown Source) INFO | jvm 2 | 2010/06/01 08:42:11 | at sun.nio.ch.SocketChannelImpl.read(Unknown Source) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.iom.orb.brg.Engine.readFully(Engine.java:5812) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.iom.orb.brg.Engine.readClearTextPacket(Engine.java:4486) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.iom.orb.brg.Engine.recvPacket(Engine.java:4338) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.iom.orb.brg.Engine.listen(Engine.java:2290) INFO | jvm 2 | 2010/06/01 08:42:11 | at com.sas.iom.orb.brg.Engine.waitForReply(Engine.java:1894) INFO | jvm 2 | 2010/06/01 08:42:11 | ... 33 more --- >From the final cause, it looks like the HOST that your application is connecting to is killing the connection for some reason. Possibly there is a session that needs to be reset somehow when the first JVM instance has failed. I am not able to help out directly with this as I am not familiar with what your application is doing at the point of failure. If you could explain it a bit then I might have some ideas or you. We will run some tests on the latest versions of the Wrapper to see if we can reproduce the original problem where the JVM fails to reconnect its socket. I'll post back when we have an update on the results of the tests. The version of the Wrapper you are using, 3.2.3, is over 4 years old and is no longer directly support. I would suggest upgrading to a more recent version as there have been a lot of issues fixed, and improvements made over the years. Cheers, Leif On Tue, Jun 1, 2010 at 11:30 AM, Justin Maguire <jma...@gm...> wrote: > Hello, > > I am currently having an issue with my wrapper.exe starting. I have found > that this starts okay first time around and can be restarted when needed, > but if the JVM ping timeout is hit and is killed all attempts to start the > wrapper service fail. > > I have made sure there are no java processes running but have ended up > needing to restart the server to get teh wrapper service to start back up. I > have attached a debug log but are at a loss as to why this is happening. > > I am okay with the wrapper restarting due to the JVM being unresponsive but > I am concerned over the inability for it to recover without a server reboot. > > > Any help or hints with this issue will be greatly appreciated! > > > > Thanks, > Justin |
|
From: Leif M. <lei...@ta...> - 2010-06-01 03:26:16
|
Justin, One more question. Do you have any AntiVirus SW installed on this server? I found the following post which points to McAfee as the cause: http://forums.sun.com/thread.jspa?threadID=430179&start=0 (Post at Nov 2, 2006 2:13 AM) This next post talks about it being a possible memory problem. What is the memory situation on your server? I don' see anything else that points to a memory issue however. http://stackoverflow.com/questions/1461460 I was also looking farther down into your logs. When you manually restart the Wrapper at 2010/06/01 10:25:18 it is then starting up normally, opening a connection back to the Wrapper, and successfully sending data. But then the first packet that the Wrapper tries to send to the JVM fails. This process repeats 5 times until the Wrapper gives up on starting the JVM. Could you please confirm whether or not this wrapper start was before or after you restarted your server? You get the same problem again when starting the Wrapper at 2010/06/01 10:26:47, 2010/06/01 10:27:41, 2010/06/01 10:37:04, and 2010/06/01 10:40:04. When you start it up at 2010/06/01 10:51:50, however, it works fine. Was this after you restarted your physical server? Cheers, Leif On Tue, Jun 1, 2010 at 12:00 PM, Leif Mortenson <lei...@ta...> wrote: > Justin, > The problem starts when the backend socket gets closed somehow. It is > a loopback socket so this should not be happening unless it is being > closed explicitly > --- > INFO | jvm 1 | 2010/06/01 08:37:00 | Closed socket: > java.net.SocketException: Software caused connection abort: recv > failed > INFO | jvm 1 | 2010/06/01 08:37:00 | Closing socket. > --- > Do have any ideas as to what on your system could have closed the socket? > > The first time, the Wrapper process was listening on port 32001, but > when its connection with the JVM is lost, it is switching over and > starts listening on port 32002 instead. At this point, it would be > impossible for the JVM to reconnect so the JVM ends up being killed as > unresponsive: > --- > ERROR | wrapper | 2010/06/01 08:42:04 | JVM appears hung: Timed out > waiting for signal from JVM. > ERROR | wrapper | 2010/06/01 08:42:04 | JVM did not exit on request, > terminated > --- > > The Wrapper is then restarting the JVM correctly. But the second JVM > instance is failing with an application level error: > --- > INFO | jvm 2 | 2010/06/01 08:42:11 | Received error while > starting the application. > INFO | jvm 2 | 2010/06/01 08:42:11 | > org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'discoveryService' defined in class path > resource [jps-config.xml]: Invocation of init method failed; nested > exception is org.omg.CORBA.COMM_FAILURE: An exception was thrown while > waiting for a reply from the peer. vmcid: 0x0 minor code: 0 > completed: No > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1337) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > java.security.AccessController.doPrivileged(Native Method) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:221) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:423) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:729) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:381) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.framework.services.bootstrap.SASRemoteServices.main(SASRemoteServices.java:63) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > java.lang.reflect.Method.invoke(Unknown Source) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > java.lang.Thread.run(Unknown Source) > INFO | jvm 2 | 2010/06/01 08:42:11 | Caused by: > org.omg.CORBA.COMM_FAILURE: An exception was thrown while waiting for > a reply from the peer. vmcid: 0x0 minor code: 0 completed: No > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.iom.orb.brg.Engine.waitForReply(Engine.java:1869) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.iom.orb.brg.Engine.sendRequest(Engine.java:805) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.iom.orb.brg.RequestImpl.invoke(RequestImpl.java:33) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.meta.SASOMI._portable_stub_IOMI.DoRequest(_portable_stub_IOMI.java:569) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.services.deployment.OMRMetadataSource.getMetadata(OMRMetadataSource.java:1091) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.services.deployment.OMRMetadataSource.getMetadataToDeployServices(OMRMetadataSource.java:1018) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.services.deployment.ServiceLoader.deployServices(ServiceLoader.java:846) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.services.deployment.PlatformServices.startLocalServices(PlatformServices.java:524) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.services.deployment.PlatformServices.startServices(PlatformServices.java:479) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.services.deployment.CorePlatformServices.startServices(CorePlatformServices.java:153) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.framework.services.PlatformDiscoveryServiceFactoryBean.afterPropertiesSet(PlatformDiscoveryServiceFactoryBean.java:100) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1368) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1334) > INFO | jvm 2 | 2010/06/01 08:42:11 | ... 21 more > INFO | jvm 2 | 2010/06/01 08:42:11 | Caused by: > java.io.IOException: An established connection was aborted by the > software in your host machine > INFO | jvm 2 | 2010/06/01 08:42:11 | at > sun.nio.ch.SocketDispatcher.read0(Native Method) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > sun.nio.ch.SocketDispatcher.read(Unknown Source) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > sun.nio.ch.IOUtil.read(Unknown Source) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > sun.nio.ch.SocketChannelImpl.read(Unknown Source) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.iom.orb.brg.Engine.readFully(Engine.java:5812) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.iom.orb.brg.Engine.readClearTextPacket(Engine.java:4486) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.iom.orb.brg.Engine.recvPacket(Engine.java:4338) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.iom.orb.brg.Engine.listen(Engine.java:2290) > INFO | jvm 2 | 2010/06/01 08:42:11 | at > com.sas.iom.orb.brg.Engine.waitForReply(Engine.java:1894) > INFO | jvm 2 | 2010/06/01 08:42:11 | ... 33 more > --- > > From the final cause, it looks like the HOST that your application is > connecting to is killing the connection for some reason. Possibly > there is a session that needs to be reset somehow when the first JVM > instance has failed. I am not able to help out directly with this > as I am not familiar with what your application is doing at the point > of failure. If you could explain it a bit then I might have some > ideas or you. > > We will run some tests on the latest versions of the Wrapper to see if > we can reproduce the original problem where the JVM fails to reconnect > its socket. I'll post back when we have an update on the results of > the tests. The version of the Wrapper you are using, 3.2.3, is over 4 > years old and is no longer directly support. I would suggest > upgrading to a more recent version as there have been a lot of issues > fixed, and improvements made over the years. > > Cheers, > Leif > > On Tue, Jun 1, 2010 at 11:30 AM, Justin Maguire <jma...@gm...> wrote: >> Hello, >> >> I am currently having an issue with my wrapper.exe starting. I have found >> that this starts okay first time around and can be restarted when needed, >> but if the JVM ping timeout is hit and is killed all attempts to start the >> wrapper service fail. >> >> I have made sure there are no java processes running but have ended up >> needing to restart the server to get teh wrapper service to start back up. I >> have attached a debug log but are at a loss as to why this is happening. >> >> I am okay with the wrapper restarting due to the JVM being unresponsive but >> I am concerned over the inability for it to recover without a server reboot. >> >> >> Any help or hints with this issue will be greatly appreciated! >> >> >> >> Thanks, >> Justin |
|
From: Justin M. <jma...@gm...> - 2010-06-01 02:48:44
|
This email contained a .zip file attachment. Raytheon does not allow email attachments that are considered likely to contain malicious code. For your protection this attachment has been removed. If this email is from an unknown source, please simply delete this email. If this email was expected, and it is from a known sender, you may follow the below suggested instructions to obtain these types of attachments. + Instruct the sender to enclose the file(s) in a ".zip" compressed file, and rename the ".zip" compressed file with a different extension, such as, ".rtnzip". Password protecting the renamed ".zip" compressed file adds an additional layer of protection. When you receive the file, please rename it with the extension ".zip". Additional instructions and options on how to receive these attachments can be found at: http://security.it.ray.com/antivirus/extensions.html http://security.it.ray.com/news/2007/zipfiles.html Should you have any questions or difficulty with these instructions, please contact the Help Desk at 877.844.4712 --- Hello, I am currently having an issue with my wrapper.exe starting. I have found that this starts okay first time around and can be restarted when needed, but if the JVM ping timeout is hit and is killed all attempts to start the wrapper service fail. I have made sure there are no java processes running but have ended up needing to restart the server to get teh wrapper service to start back up. I have attached a debug log but are at a loss as to why this is happening. I am okay with the wrapper restarting due to the JVM being unresponsive but I am concerned over the inability for it to recover without a server reboot. Any help or hints with this issue will be greatly appreciated! Thanks, Justin |
|
From: Joey G. <jo...@su...> - 2010-05-27 16:31:36
|
I'm using the Java Service Wrapper to create a service in Linux. This Java Application has no main GUI, but if certain error message occur then it displays a warning box allowing the user to know. If I log into root and install the application everything works fine. But, if I log into a none root user graphically and then do a su - to get to root the service will not start. This is the command I'm using inside the service (/etc/init.d/rc.d/backup) to start the application export DISPLAY=:0.0 /home/pulse/backups/bin/backup start -Djava.awt.headless=true If I take out the "export DISPLAY=:0.0" the service will start fine, but when an error occurs the warning box doesn't pop up. |
|
From: Leif M. <lei...@ta...> - 2010-05-18 06:10:21
|
Hi all,
I would like to announce the release of 3.4.1 (a few days ago).
This version includes a couple new useful features as well as
resolving some important issues.
New Features include:
* The ability to launch the JVM without including a Classpath on
the JVM. This was needed by some 3rd party process administration
tools.
* (Professional Edition) Better control over child processes
executed in response to an event.
Please see the release notes for a full list of changes:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html#3.4.1
We have also once again resumed making the Community Editions of the
Wrapper from the Source Forge download page:
https://sourceforge.net/projects/wrapper/files/
The Community Edition, as well as the Standard and Professional
Editions will continue to be available from the Wrapper site as well:
http://wrapper.tanukisoftware.org/doc/english/download.jsp
As always, please let us know how we can continue to improve the
Wrapper to meet your needs.
Sincerely,
Leif Mortenson
Tanuki Software, Ltd.
http://www.tanukisoftware.com
|
|
From: Christian M. <chr...@ta...> - 2010-05-14 01:47:01
|
Glenn, I think svc tries to start your applications twice because of this: ln -s /etc/init.d/myapp /etc/rc0.d/K20myapp ln -s /etc/init.d/myapp /etc/rc1.d/K20myapp ln -s /etc/init.d/myapp /etc/rc2.d/S20myapp ln -s /etc/init.d/myapp /etc/rc3.d/S20myapp (see http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-solaris.html) As you can see, there is a S20myapp in the rc2.d & rc3.d folder. this means, when the systems changes to init level 2, it will try to 'S'tart myapp at sequence 20. and it will try to start myapp at init level 3. At boot solaris starts at init 0 and will traverse all init levels until init level 3. So when getting into init level 3 the myapp application was already started at init 2. As you see in the logfile the script will notice that your app has already been started and quit, so it's not harmful to your system to leave the file there, but on the other side I think it would also be safe to remove rc2.d/S20myapp if you want. Cheers, Christian On Fri, May 14, 2010 at 12:29 AM, <gle...@ag...> wrote: > > Thanks Christian, that worked. My service is starting on system start now, > but it looks like it is getting started twice for some reason? > /var/svc/log/milestone-multi-user-server:default.log now contains: > Executing legacy init script “/etc/rc3.d/S20myapp.sh”. > Starting MyApp... > MyApp is already running. > Legacy init script “/etc/rc3.d/S20myapp.sh” exited with return code 1. > > Kind Regards, > * > Glenn Potter | **Agfa HealthCare* > Strategic Site Research Engineer | HE/Radiology PACS Solutions > M +1 414 208 8997 > gle...@ag... > Milwaukee, WI USA (Central Time: GMT-06:00) > > Agfa HealthCare Corporation, 100 Challenger Road, Ridgefield Park, NJ, > 07660-2199, United States > http://www.agfa.com/healthcare/ > ------------------------------ > Click on link to read important disclaimer: > http://www.agfa.com/healthcare/maildisclaimer > > > *Christian <chr...@ta...>* > > 05/13/2010 01:16 AM > Please respond to > wra...@li... > > To > wra...@li... > cc > Subject > Re: [Wrapper-user] Not starting service on Solaris > > > > > > Glenn, > > We are sorry for the confusion. > > Due to the parsing routines/naming conventions of SVC, you can not use > capital letters for a command launched at rc level. > > Please try renaming the rc*.d/*MyApp.sh files to rc*.d/*myapp.sh > > Hope this works out for you. > > Cheers, > Christian > > On Wed, 2010-05-12 at 23:54 -0500, gle...@ag... wrote: > > > > Hello, > > > > I deployed my wrapped application to Solaris 10 and installed > > following the instructions on: > > > http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-solaris.html > > > > I can start and stop as a console app and background process from the > > command line in /etc/init.d. > > > > When I reboot the service is not started and I get this > > in /var/svc/log/milestone-multi-user-server:default.log: > > > > Executing legacy init script “/etc/rc3.d/S20MyApp.sh”. > > Usage: /etc/rc3.d/S20MyApp.sh { console | start | stop | restart | > > condrestart | status | dump } > > Legacy init script “/etc/rc3.d/S20MyApp.sh” exited with return code > > 1. > > > > Why is the service control manager not passing the 'start' command to > > my startup script? > > > > Thanks for you help, > > Glenn > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > |
|
From: <gle...@ag...> - 2010-05-13 15:29:40
|
Thanks Christian, that worked. My service is starting on system start now, but it looks like it is getting started twice for some reason? /var/svc/log/milestone-multi-user-server:default.log now contains: Executing legacy init script ?/etc/rc3.d/S20myapp.sh?. Starting MyApp... MyApp is already running. Legacy init script ?/etc/rc3.d/S20myapp.sh? exited with return code 1. Kind Regards, Glenn Potter | Agfa HealthCare Strategic Site Research Engineer | HE/Radiology PACS Solutions M +1 414 208 8997 gle...@ag... Milwaukee, WI USA (Central Time: GMT-06:00) Agfa HealthCare Corporation, 100 Challenger Road, Ridgefield Park, NJ, 07660-2199, United States http://www.agfa.com/healthcare/ Click on link to read important disclaimer: http://www.agfa.com/healthcare/maildisclaimer Christian <chr...@ta...> 05/13/2010 01:16 AM Please respond to wra...@li... To wra...@li... cc Subject Re: [Wrapper-user] Not starting service on Solaris Glenn, We are sorry for the confusion. Due to the parsing routines/naming conventions of SVC, you can not use capital letters for a command launched at rc level. Please try renaming the rc*.d/*MyApp.sh files to rc*.d/*myapp.sh Hope this works out for you. Cheers, Christian On Wed, 2010-05-12 at 23:54 -0500, gle...@ag... wrote: > > Hello, > > I deployed my wrapped application to Solaris 10 and installed > following the instructions on: > http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-solaris.html > > I can start and stop as a console app and background process from the > command line in /etc/init.d. > > When I reboot the service is not started and I get this > in /var/svc/log/milestone-multi-user-server:default.log: > > Executing legacy init script ?/etc/rc3.d/S20MyApp.sh?. > Usage: /etc/rc3.d/S20MyApp.sh { console | start | stop | restart | > condrestart | status | dump } > Legacy init script ?/etc/rc3.d/S20MyApp.sh? exited with return code > 1. > > Why is the service control manager not passing the 'start' command to > my startup script? > > Thanks for you help, > Glenn > ------------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user ------------------------------------------------------------------------------ _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: Christian <chr...@ta...> - 2010-05-13 07:09:06
|
Glenn, We are sorry for the confusion. Due to the parsing routines/naming conventions of SVC, you can not use capital letters for a command launched at rc level. Please try renaming the rc*.d/*MyApp.sh files to rc*.d/*myapp.sh Hope this works out for you. Cheers, Christian On Wed, 2010-05-12 at 23:54 -0500, gle...@ag... wrote: > > Hello, > > I deployed my wrapped application to Solaris 10 and installed > following the instructions on: > http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-solaris.html > > I can start and stop as a console app and background process from the > command line in /etc/init.d. > > When I reboot the service is not started and I get this > in /var/svc/log/milestone-multi-user-server:default.log: > > Executing legacy init script “/etc/rc3.d/S20MyApp.sh”. > Usage: /etc/rc3.d/S20MyApp.sh { console | start | stop | restart | > condrestart | status | dump } > Legacy init script “/etc/rc3.d/S20MyApp.sh” exited with return code > 1. > > Why is the service control manager not passing the 'start' command to > my startup script? > > Thanks for you help, > Glenn > ------------------------------------------------------------------------------ > > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: <gle...@ag...> - 2010-05-13 04:54:39
|
Hello, I deployed my wrapped application to Solaris 10 and installed following the instructions on: http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-solaris.html I can start and stop as a console app and background process from the command line in /etc/init.d. When I reboot the service is not started and I get this in /var/svc/log/milestone-multi-user-server:default.log: Executing legacy init script ?/etc/rc3.d/S20MyApp.sh?. Usage: /etc/rc3.d/S20MyApp.sh { console | start | stop | restart | condrestart | status | dump } Legacy init script ?/etc/rc3.d/S20MyApp.sh? exited with return code 1. Why is the service control manager not passing the 'start' command to my startup script? Thanks for you help, Glenn |
|
From: Leif M. <lei...@ta...> - 2010-05-04 17:06:58
|
Joey, To make this work, you will need to make the service "interactive". This can be done by setting the wrapper.ntservice.interactive property and then reinstalling your service: http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-interactive.html Please note that starting with Windows 2008 and Vista, it is no longer possible to make a service interactive. Microsoft decided to start forcing all output from a service to display on a Session 0 desktop. We have been looking into ways of working around this new behavior with Windows 2008/Vista. It will involve spawning a second process to manage the GUI and is still a little ways off. Cheers, Leif On Wed, May 5, 2010 at 1:05 AM, Joey Garza <jo...@su...> wrote: > I have a jar that has no GUI what so ever. I am running this as a service > with JSW and it works great. My question is. I would like to pop up a > JOptionPane if certain errors occur. I tried using this: > > JOptionPane.showMessageDialog(new JFrame(), > > "Please check log", > "Error", JOptionPane.ERROR_MESSAGE); > > Running my jar file from a command line the box pops up. But, running it > with JSW it doesn't > > popup. Thanks to everyone that helps. |
|
From: Joey G. <jo...@su...> - 2010-05-04 16:28:54
|
I have a jar that has no GUI what so ever. I am running this as a service with JSW and it works great. My question is. I would like to pop up a JOptionPane if certain errors occur. I tried using this: JOptionPane.showMessageDialog(new JFrame(), "Please check log", "Error", JOptionPane.ERROR_MESSAGE); Running my jar file from a command line the box pops up. But, running it with JSW it doesn't popup. Thanks to everyone that helps. |