Re: [Wrapper-user] Help with Event Logging

[Ryan C. <ry...@gm...>]

Leif:
     Thank you so much for the very detailed reply.  I finally got the
logging working and as usual it was a silly mistake on my part:  I had
neglected to call the NTEventLogAppender.setThreshold(Priority p) method.
Once I included that call, everything is working as expected.

However, it would seem that using the built-in system logging would be much
cleaner (and platform independent) so I would be interested in getting that
working instead.  Simply changing the wrapper.syslog.loglevel property value
from "none" to "info" or "debug" did not seem to work out.  Is there
anything else I would need to do besides setting increasing the log level
there?

Thanks again for the help!  I was beginning to lose hope :)
-Ryan
On Mon, Feb 22, 2010 at 4:38 AM, Leif Mortenson <le...@ta...>wrote:

> Ryan,
> The Java Service Wrapper has its own method of logging to the Windows
> Event Logs.  It sounds like you have located the configuration for
> that.
>
> Log4J is an independent implementation that does not make use of the
> Wrapper's features.
>
> Looking at the following javadoc page, it says that it requires that
> you place a NTEventLogAppender.dll native library on the PATH.
>
> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/nt/NTEventLogAppender.html
> When Java specifies a specific Library Path, as is done with the
> Wrapper, Java does NOT search the PATH by default.
> Please go in and either add the location of the NTEventLogAppender.dll
> file to the library path with the following property:
> http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-n.html
> Or tell the Wrapper to append the PATH again:
>
> http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-append-system-path.html
> I would suggest the first option.
>
> Another possibility is that your log4j properties file is not being
> found correctly when the JVM is launched.
> Please try setting the following property and rerunning your
> application to make sure that the Wrapper is generating the Java
> command line that you expect:
> wrapper.java.command.loglevel=INFO
>
> Please let me know how this works for you, or if you have more questions.
>
> Cheers,
> Leif
>
>
> On Sun, Feb 21, 2010 at 12:35 PM, Ryan Connolly <ry...@gm...> wrote:
> > Hello wrapper users!
> > I am new to the list so please take it easy on me.  I'm sorry if this has
> > been asked previously but I've had no luck finding any answers to my
> > question.  I'm hoping y'all can help me out.
> > I have a requirement to perform some logging to the Windows Event Logs
> and
> > I'm just not getting it... I've been using the log4j NTEventLogAppender
> > successfully in my unit tests however no logging occurs while running
> > from WrapperSimpleApp.  I've noticed in the logging docs a
> > "wrapper.syslog.loglevel" property so I went ahead and changed its value
> > from NONE to INFO, still no dice.  Does anyone have any additional
> > information or experience with this?  I'd really like to get this sorted
> > out!
> > Thanks to any in advance!
> > -Ryan
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>



-- 
®¥@N