Overhead in weblogic logging

Question

Does anyone have an info on the performance overhead of logging within
weblogic (6.1 sp2). There doesn't seem to be a way to turn down the
logging to weblogic.log from info to something like error or warning
level. I thought the StdoutSeverityLevel parameter would do that but it
only controls what is written to standard out not the weblogic.log.
Also, should the access log be enabled in production systems? Since it
writes a line to the log for every http hit, I was wondering what kind
of performance overhead that might make.
Kirk

Answer 1

FYI: The LogToStdOut option only applies to the console output, not the
weblogic.log file.
Nils
Pamal wrote:
>
Hi,
You can turn off complete logging by unchecking the Log to Stdout in WebLogic
administration console. Or the same can be achieved by giving the following in
config.xml
<WebServer DefaultWebApp=""
LogFileName="./config/petstore/logs/access.log"
LoggingEnabled="false" Name=""/>
You can also set the level of logging to Info, Debug etc
Regards,
Pamal
Rob Woollen <[email protected]> wrote:
I don't believe there's any current way to limit what gets written to
the
weblogic.log.
Writes to the access.log are buffered internally in the server so their
performance impact shouldn't be too big.
FWIW, I'd recommend that you run performance tests on your application
first and
then consider turning off logging only if it has a significant impact.
-- Rob
Kirk Everett wrote:
I totally agree and was only thinking about doing this in a productionenv. I
just wanted to know if you could (or should) turn off the access.logand the
weblogic.log. Is there even a way to turn down what gets put in the
weblogic.log?
Kirk
Cameron Purdy wrote:
Logging can be expensive, but only consider this once you have a
stable
application. Usually the application-level (not server-level) loggingis the
prime culprit, and you can reduce this with clever use of the deletekey in
source code files. You can also redirect stdout and stderr to nuland you
can turn off logging options once you are sure that things are stable.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you shouldbe!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Kirk Everett" <[email protected]> wrote in message
news:[email protected]...
Does anyone have an info on the performance overhead of logging
within
weblogic (6.1 sp2). There doesn't seem to be a way to turn downthe
logging to weblogic.log from info to something like error or warning
level. I thought the StdoutSeverityLevel parameter would do thatbut it
only controls what is written to standard out not the weblogic.log.
Also, should the access log be enabled in production systems? Sinceit
writes a line to the log for every http hit, I was wondering whatkind
of performance overhead that might make.
Kirk
============================
[email protected]