Log level defaults, Rollingfileappender defaults, Configuring log4j dynamically – IBM 51 User Manual
Page 54: Level, Defaults, Rollingfileappender, Configuring, Log4j, Dynamically
#log4j.appender.datacentermodel.layout=org.apache.log4j.PatternLayout
#log4j.appender.datacentermodel.layout.ConversionPattern=${output.module}
#log4j.appender.datacentermodel.append=false
Log
level
defaults
The
initial
log4j
log
level
configuration
for
each
log
file
is
set
to
info
.
As
defined
in
the
log4j.prop
file
above,
each
log
file
is
set
to
a
unique
log
level
for
Tivoli
Intelligent
Orchestrator
using
the
log4j.appender.filename.threshold=
parameter.
The
following
is
a
list
of
the
default
logging
levels
for
each
of
the
log
file
types:
console.log
info
If
you
want
more
log
information
for
troubleshooting
purposes,
set
the
log
level
to
debug
.
trace.log
error
msg.log
MSG_INFO#com.thinkdynamics.kanaha.util.logging.MessageLevel
cbe.log
error
RollingFileAppender
defaults
The
RollingFileAppender
defines
the
autoarchiving
behavior
of
the
log4j
tool.
As
defined
in
the
log4j.prop
file
above,
the
default
settings
for
each
Tivoli
Intelligent
Orchestrator
log
file
are:
console.log
v
Maximum
number
of
archived
log
files:
10
v
Maximum
log
file
size:
100MB
trace.log
v
Maximum
number
of
archived
log
files:
10
v
Maximum
log
file
size:
10MB
msg.log
v
Maximum
number
of
archived
log
files:
10
v
Maximum
log
file
size:
10MB
cbe.log
v
Maximum
number
of
archived
log
files:
10
v
Maximum
log
file
size:
10MB
Configuring
log4j
dynamically
To
modify
the
log4j.prop
or
log4j-util.prop
file:
1.
Open
the
properties
file
in
a
text
editor.
2.
Modify
settings
as
required.
3.
Save
the
file.
42
Tivoli
Intelligent
Orchestrator
Problem
Determination
and
Troubleshooting
Guide