WebLogic Server Node Manager Log File Redirection Doesn't Work After Crash Recovery
(Doc ID 1340087.1)
Last updated on MARCH 12, 2021
Applies to:Oracle WebLogic Server - Version 10.3.3 and later
Information in this document applies to any platform.
WebLogic Server Node Manager is not able to redirect JVM stdout and stderr output channels to files after a crash recovery. Logfile names and directories are configured in the server's startup.properties file via weblogic.Stdout and weblogic.Stderr properties. This works fine with normal server start. However, the properties are not honored by Node Manager after a crash recovery procedure. The stdout/sterr logfile (both channels in one file) is always created in the domain/servers/server_name/logs directory instead.
Steps to replicate:
- Edit the startup.properties of admin server to log the stdout and stderr in some files.
- Start Node Manager using startNodeManager.cmd with weblogic.Stdout and weblogic.Stderr specified, like the following:
- Reboot the physical machine.
The server is running, but the logs will be generated under the default location /servers/AdminServer/logs. Nothing will be logged in the location specified in the startup.properties.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document