Abstract
All middleware environments eventually face circumstances that affect the availability of their subsystems and of the applications running on them. Oracle WebLogic Server administrators must anticipate these events by closely monitoring the behavior of the JVM and reviewing the information available in log files, which can assist before and after these events occur.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
WebLogic Server provides support for applications to produce messages and send them to the server log without using its standard catalog.
- 2.
The Java logging API URL is https://docs.oracle.com/javase/7/docs/api/java/util/logging/package-summary.html .
- 3.
The Apache Log4J open source project URL is http://logging.apache.org/log4j/ .
- 4.
In production systems, use the Debug and Trace logging levels with caution, keeping in mind that the server will need to use much more resources than usual to process such levels of verbosity.
- 5.
The JVM will resort to the OS configuration to determine the locale and format to use to display the log message timestamp.
- 6.
Node Manager also keeps its own log file named nodemanager.log, located in the nodemanager directory in the domain root. This file contains its own server startup and status messages
- 7.
It is also possible to also store transaction logs in a database instead of in the file system. Either option is configurable using the Administration Console, in the Default Store section of the Services page under the General tab of the corresponding server.
- 8.
Changing log file name and location, log rotation type, and directory, and whether or not to rotate the log file at startup will require a server restart to become active.
- 9.
In production mode, WebLogic Server will by default rotate the file when it reaches 5MB in size and will not rotate the log file upon server start.
- 10.
Java Directory Naming Interface or JNDI is an API that maintains a type of directory service for software components and allows Java software clients to discover objects by name.
- 11.
These states are defined in the weblogic.health.HealthState class from the WebLogic API.
- 12.
From this page JVM garbage collection can be forced and thread stacks can be dumped.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2018 Gustavo Garnica
About this chapter
Cite this chapter
Garnica, G. (2018). Logging and Monitoring. In: Oracle WebLogic Server 12c Administration I Exam 1Z0-133. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2562-2_7
Download citation
DOI: https://doi.org/10.1007/978-1-4842-2562-2_7
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-2561-5
Online ISBN: 978-1-4842-2562-2
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books