|
From: Ryan C. <ry...@gm...> - 2010-02-26 14:16:27
|
Thanks for all of the great info, Leif. This really helps me understand why I was unable to use the logging property. As I am wrapping a project that already has log4j as a dependency I think ill keep it that way for now I instead of introducing an additional dependency on the wrapper API. Ill keep this in mind for future development, however. Thanks again! -Ryan On Feb 22, 2010 6:38 PM, "Leif Mortenson" <lei...@ta...> wrote: Ryan, The Wrapper's Event Log / syslog target is used to output the Wrapper's log output to the event log in addition to the wrapper.log and console. By default it is disabled. We do not recommend setting the Event Log's loglevel to DEBUG or INFO as it will very quickly fill up the event log. It is mainly useful for logging warnings and error messages. Normally, all output to the JVMs console will be logged by the Wrapper at the INFO log level. You can log to a higher level like ERROR or FATAL, but using the following API: import org.tanukisoftware.wrapper.WrapperManager; WrapperManager.log(WrapperManager.WRAPPER_LOG_LEVEL_ERROR, "This is a test Error"); See the Javadocs here: http://wrapper.tanukisoftware.org/doc/english/javadocs.html?org/tanukisoftware/wrapper/WrapperManager.html This output will then show up everywhere that the ERROR log output is enabled. On UNIX platforms it could go to the syslog. http://wrapper.tanukisoftware.org/doc/english/prop-syslog-loglevel.html http://wrapper.tanukisoftware.org/doc/english/prop-logfile-loglevel.html http://wrapper.tanukisoftware.org/doc/english/prop-console-loglevel.html http://wrapper.tanukisoftware.org/doc/english/props-logging.html What is an example of what you are trying to do? I may have some suggestions. Cheers, Leif On Mon, Feb 22, 2010 at 10:38 PM, Ryan Connolly <ry...@gm...> wrote: > Leif: > Thank you ... |