Databases Reference
In-Depth Information
How it works...
Changing the log levels to display more information is the first common and useful task
WebLogic administrators should set in production environments.
The
PROD_Server01
logfiles are located by default at
$DOMAIN_HOME/servers/
PROD_Server01/logs/PROD_Server01.log
and
$DOMAIN_HOME/servers/
PROD_Server01/logs/PROD_Server01.out
.
This recipe raises the level of logging and enables only the transaction debug. WebLogic has
several other debug options that can be enabled, such as security, protocol, JMS, and deploy
among others. Enable the option that best suits your troubleshooting needs.
Debug and trace logging will write a lot of information to the output log,
so do not forget to disable it at the analysis end.
There's more...
The log levels can also be changed using WLST.
Changing the log levels using WLST
1. Log in as a
wls
user to shell and start WLST:
[wls@prod01]$ $WL_HOME/common/bin/wlst.sh
2. Connect to the Administration Server using
wlsadmin
as the user,
<pwd>
as the
password and
t3://adminhost.domain.local:7001
as the server URL:
wls:/offline> connect("wlsadmin","<pwd>","t3://adminhost.domain.
local:7001")
3. Run the following WLST commands to create the file stores:
edit()
startEdit()
cd('/Servers/PROD_Server01/Log/PROD_Server01')
cmo.setStacktraceDepth(-1)
cmo.setLoggerSeverity('Trace')
cmo.setStdoutSeverity('Debug')
cmo.setMemoryBufferSeverity('Debug')
cd('/Servers/PROD_Server01/ServerDebug/PROD_Server01')
Search WWH ::
Custom Search