Application logging in weblogic 7.0

Question

Just wanted to put a question out there as to how everyone else is doing application
logging. I want to provide a standardized error level logging capability to my
application developers, and I DO NOT want to use the weblogic logging as it appears
that it only can write to the server log - I worry about apps filling this filespace.
I tried ServletContext logging, and contrary to other implementations, it also
goes to the server log. According to the specs, it should go to a file that matches
up with the context name.
Is log4j the way to go?

Answer 1

Thanks for the feedback, anyone else that ones to chime in on log4j shoot.
Were looking now at how to leverage/intergate/avaliablate log4j within WLS.
Cheers
mbg
"Jon Mountjoy" <[email protected]> wrote in message
news:[email protected]..
Hi Mark,
I am curious about how log4j didn't work in a cluster, and what about
weblogic's logging was superior to log4j?Well, I didn't exactly say that it didn't work in a cluster ;-) I
implied that it didn't work beautifully in a cluster :-)
These are the advantages that I see to WebLogic's logging:
a) Distributed logging is a no-brainer
b) Integration with WebLogic's own notifications
WL:If you want to log in a cluster, then using WebLogic's logging is
simple and effective - it all works out of the box. You get a nice
domain log and all the underlying distribution is done for you.
Log4J: If you want to log in a cluster using Log4J, then as far as I
know you have to do some work (not much, just some) - which you don't
have to do using WL. AFAIK, to get the same functionality you have to
use SocketAppenders, and then have your administration server (or
whichever server you want to hold the domain log) run a socketnode.
Advantages: You have lots of nifty log4j features, more portable.
Disadvantages: More setup, more administration, no integration with WL
notifications.
To me the greatest advantage is the integration with WebLogic's own
notifications. Logging is not just about debugging info, but also
manageability. I want to see all important information consolidated.
Of course, I can write code to get this - perhaps writinng a
notification listener for WL messages and converting them to Log4J
messages. Hmm, perhaps if WL let me write my own 'appender' instead of
their default 'send a JMX event' I could get nice clean integration.
The nice thing about Log4J is that it's feature set is far richer, and
its more 'portable' if you are willing to do the integration work with
each app server.
Regards,
Jon