|
From: Asawari P. <ass...@gm...> - 2011-11-30 07:43:07
|
Thanks Leif! I will try upgrading to version 3.5.13 I will get back to you if I have any issues. Thanks, Asawari On Wed, Nov 30, 2011 at 12:37 PM, Leif Mortenson < lei...@ta...> wrote: > Asawari, > I am sorry for the trouble. There is a known buffer overflow problem > in 3.5.11 and 3.5.12 where log lines from the JVM that are over 3072 > characters in length. This issue was well understood and has been > resolved in the 3.5.13 release. Please try upgrading and it should fix > this for you. > > Anyone who is using either of these versions should upgrade their > servers immediately if there is a chance that their JVM applications > could output long log lines. The buffer overflow is likely to result > in a crash which will cause the Wrapper process to terminate, and the > JVM to shut itself down immediately. When the Wrapper fails like > this, it will not restart the JVM so the application will be down. > > Cheers, > Leif > > On Wed, Nov 30, 2011 at 3:58 PM, Asawari Pawar <ass...@gm...> > wrote: > > Hi, > > > > I am using wrapper version 3.5.11 on Windows XP and Windows 2003 systems. > > Wrapper servic is crashing with Event ID 1000 Faulting Application > > wraaper.exe, faulting module wrapper.exe version 3.5.11.0 fault address > > 0x0003c129 I see the above error message in windows event log. Can anyone > > help me with the above issue? > > > > I have attached the screenshot. > > > > Thanks! > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |