StopNodeManager log is Outputted to Nodemanager.log but not to Nodemanager.log.0 when LogCount is Greater than 1
(Doc ID 2420488.1)
Last updated on DECEMBER 16, 2023
Applies to:
Oracle WebLogic Server - Version 12.2.1.2.0 and laterInformation in this document applies to any platform.
Symptoms
After setting LogCount greater than 1, the log of node manager will be outputted to nodemanager.log.0.
Notice in this case then nodemanager.log.0 becomes the new current nodemanager log file (instead of nodemanager.log).
Refer to product documentation at Reviewing nodemanager.properties
And the old log file will be rotate to nodemanager.log.1, nodemanager.log.2, etc.
However, when stop by stopNodeManager.sh (Linux) or stopNodeManager.cmd(Windows), the stop log is still outputted to nodemanager.log
The stop log-entries are as follows.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |