|
From: Mark M. <MMo...@gl...> - 2006-08-22 12:16:34
|
Hi...
Console to your java app is just stdout, which could be anything in
reality. Log4j in your app is configured to send your logging at
various levels to various places, but your app's sense of log levels is
different from the wrapper's.
The wrapper is controlling stdout from your app. If your app writes
anything to stdout, I believe wrapper considers all of that INFO and
will send it, along with those ping messages, wherever you configure
wrapper.conf to send INFO and above.
We have the wrapper send error and above to the event log just to keep
the excess verbiage down and let the app send all of it's logging to a
file.
-Mark
=20
This e-mail message, and any attachments, is intended only for the use =
of the individual or entity identified in the alias address of this =
message and may contain information that is confidential, privileged and =
subject to legal restrictions and penalties regarding its unauthorized =
disclosure and use. Any unauthorized review, copying, disclosure, use or =
distribution is strictly prohibited. If you have received this e-mail =
message in error, please notify the sender immediately by reply e-mail =
and delete this message, and any attachments, from your system. Thank =
you.=20
-----Original Message-----
From: Jeff Lanzarotta [mailto:del...@ya...]=20
Sent: Monday, August 21, 2006 5:07 PM
To: Mark Modrall; wra...@li...
Subject: RE: [Wrapper-user] Logging question
Ok, I'm really getting confused now... which is quite easy to do by the
way...
I have wrapper.conf set to:
wrapper.console.loglevel=3DINFO
wrapper.logfile.loglevel=3DINFO
Which I believe is the default...
I guess I am not understanding how wrapper determines what to log to
it's log file...
--- Mark Modrall <MMo...@gl...> wrote:
> Ah... I'm remembering now... Our wrapper.conf is pretty minimal; it
> only sends ERROR and above and that to the Event log. If I remember
> correctly, the wrapper is watching any console output and treats all
> app
> output to CONSOLE as INFO (not even DEBUG), not matter what your app
> considers it.
>=20
> The INFO level on wrapper.conf ends ups producing those endless ping
> messages, so we thought we would keep it to the important stuff...
>=20
> -Mark
>=20
>=20
>=20
>=20
> =20
> This e-mail message, and any attachments, is intended only for the
> use of the individual or entity identified in the alias address of
> this message and may contain information that is confidential,
> privileged and subject to legal restrictions and penalties regarding
> its unauthorized disclosure and use. Any unauthorized review,
> copying, disclosure, use or distribution is strictly prohibited. If
> you have received this e-mail message in error, please notify the
> sender immediately by reply e-mail and delete this message, and any
> attachments, from your system. Thank you.=20
>=20
> -----Original Message-----
>=20
> From: Jeff Lanzarotta [mailto:del...@ya...]=20
> Sent: Monday, August 21, 2006 4:48 PM
> To: Mark Modrall; wra...@li...
> Subject: RE: [Wrapper-user] Logging question
>=20
> My log4j.properties files pretty much looks the same. Here is mine
>=20
> ----------8<----------
>=20
> log4j.rootCategory=3DDEBUG, CONSOLE, DAILY, CHAINSAW
>=20
> # CONSOLE
> log4j.appender.CONSOLE=3Dorg.apache.log4j.ConsoleAppender
> log4j.appender.CONSOLE.ImmediateFlush=3Dtrue
> log4j.appender.CONSOLE.layout=3Dorg.apache.log4j.PatternLayout
> log4j.appender.CONSOLE.layout.ConversionPattern=3D%-5p [%t][%C{1}]:
> %m%n
>=20
> # DAILY ROLLING FILE, roll the file at midnight each and every day
> log4j.appender.DAILY=3Dorg.apache.log4j.DailyRollingFileAppender
> log4j.appender.DAILY.file=3D./log/directlink.log
> log4j.appender.DAILY.Threshold=3DINFO
> log4j.appender.DAILY.DatePattern=3D'.'yyyy-MM-dd
> log4j.appender.DAILY.layout=3Dorg.apache.log4j.PatternLayout
> log4j.appender.DAILY.layout.ConversionPattern=3D%d %-5p [%t][%C{1}]:
> %m%n
>=20
> # CHAINSAW
> log4j.appender.CHAINSAW=3Dorg.apache.log4j.net.SocketAppender
> log4j.appender.CHAINSAW.Threshold=3DINFO
> log4j.appender.CHAINSAW.remoteHost=3D10.0.1.71
> log4j.appender.CHAINSAW.port=3D4445
> log4j.appender.CHAINSAW.locationInfo=3Dtrue
>=20
> ----------8<----------
>=20
> I am using CONSOLE, DAILY ROLLING and CHAINSAW. I'm still getting
> everything written to wrapper's log file though...
>=20
> Any thoughts?
>=20
>=20
>=20
> --- Mark Modrall <MMo...@gl...> wrote:
>=20
> > We're in the same boat. We have our logger.properties set like
> this:
> >=20
> > log4j.appender.LOGFILE=3Dorg.apache.log4j.FileAppender
> > log4j.appender.LOGFILE.File=3D/logs/output.log
> > log4j.appender.LOGFILE.Append=3Dtrue
> > log4j.appender.LOGFILE.Threshold=3DINFO
> > log4j.appender.LOGFILE.layout=3Dorg.apache.log4j.PatternLayout
> > log4j.appender.LOGFILE.layout.ConversionPattern=3D[%F %L] %M: %m%n
> >=20
> > # Enable INFO messages on the search handler only so it can
> announce
> > itself
> > log4j.logger.org.ourclasshierarchy=3DINFO, LOGFILE
> >=20
> > So any class we write will log to our file and anything produced by
> > the
> > wrapper will go wherever wrapper.conf sends it.
> >=20
> > Thanks
> > _Mark
> >=20
> >=20
> >=20
> > =20
> > This e-mail message, and any attachments, is intended only for the
> > use of the individual or entity identified in the alias address of
> > this message and may contain information that is confidential,
> > privileged and subject to legal restrictions and penalties
> regarding
> > its unauthorized disclosure and use. Any unauthorized review,
> > copying, disclosure, use or distribution is strictly prohibited. If
> > you have received this e-mail message in error, please notify the
> > sender immediately by reply e-mail and delete this message, and any
> > attachments, from your system. Thank you.=20
> >=20
> > -----Original Message-----
> >=20
> > From: wra...@li...
> > [mailto:wra...@li...] On Behalf Of
> Jeff
> > Lanzarotta
> > Sent: Monday, August 21, 2006 3:35 PM
> > To: Wrapper-User List
> > Subject: [Wrapper-user] Logging question
> >=20
> > Hello,
> >=20
> > I have written an application that used log4j for logging. Right
> now
> > when the application logs a message through log4j, it is written to
> > log4j's log file AND wrapper picks up the message and writes it to
> > it's
> > log... Thus, I have every single message logged twice...
> >=20
> > Is there a way to have wrapper NOT log messages from log4j? I
> really
> > only want wrapper to log information specific to 'wrapper' not my
> > application...
> >=20
> > Thoughts?
> >=20
> > Regards,
> >=20
> > -Jeff
> >=20
> > -Jeff
> >=20
> >
>
------------------------------------------------------------------------
> > -
> > Using Tomcat but need to do more? Need to support web services,
> > security?
> > Get stuff done quickly with pre-integrated technology to make your
> > job
> > easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache
> > Geronimo
> >
>
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
>
|