Understanding WebLogic Logging Services
– WebLogic logging services provide facilities for writing, viewing, filtering, and listening for log
– These log messages are generated by WebLogic Server instances, subsystems, and Java EE
messages.
applications that run on WebLogic Server or in client JVMs.
• WebLogic Server subsystems use logging services to provide information about events
– Ex. deployment of new applications or the failure of one or more subsystems
• Each WebLogic Server instance maintains a server log
• Logging services collect messages that are generated on multiple server instances into a
single, domain-wide message log
• The domain log provides the overall status of the domain
Log Message Format
Here is an example of a message in the server log file:
####<Sept 22, 2004 10:46:51 AM EST> <Notice> <WebLogicServer> <MyComputer>
<examplesServer> <main> <<WLS Kernel>> <> <null> <1080575211904> <BEA-000360>
<Server started in RUNNING mode>
• In this example, the message attributes are:
Locale-formatted Timestamp, Severity, Subsystem, Machine Name, Server Name, Thread ID, User ID,
Transaction ID, Diagnostic Context ID, Raw Time Value, Message ID, and Message Text.
Time stamp Time and date when the message originated.
The Java Virtual Machine (JVM) that runs each WebLogic Server instance refers to the host computer
operating system for information about the local time zone and format.
Severity Indicates the degree of impact or seriousness of the event reported by the
message.
Subsystem Indicates the subsystem of WebLogic Server that was the source of the
Machine Name
Server
Name
Thread ID
message; for example, Enterprise Java Bean (EJB) container or Java
Messaging Service (JMS).
Identifies the origins of the message:
Server Name is the name of the WebLogic Server
Machine Name is the DNS name of the computer
Thread ID is the ID that the JVM assigns to the thread in which the
message originated
User ID The user ID under which the associated event was executed
Transaction ID Present only for messages logged within the context of a transaction
Diagnostic
Context ID
Raw Time Value The timestamp in milliseconds
Message ID A unique six-digit identifier
Context information to correlate messages coming from a specific request or
application
All message IDs that WebLogic Server system messages generate start with
BEA- and fall within a numerical range of 0-499999.
TechSys IT Solutions
Message Text A description of the event or condition.
– WebLogic logging services provide facilities for writing, viewing, filtering, and listening for log
– These log messages are generated by WebLogic Server instances, subsystems, and Java EE
messages.
applications that run on WebLogic Server or in client JVMs.
• WebLogic Server subsystems use logging services to provide information about events
– Ex. deployment of new applications or the failure of one or more subsystems
• Each WebLogic Server instance maintains a server log
• Logging services collect messages that are generated on multiple server instances into a
single, domain-wide message log
• The domain log provides the overall status of the domain
Log Message Format
Here is an example of a message in the server log file:
####<Sept 22, 2004 10:46:51 AM EST> <Notice> <WebLogicServer> <MyComputer>
<examplesServer> <main> <<WLS Kernel>> <> <null> <1080575211904> <BEA-000360>
<Server started in RUNNING mode>
• In this example, the message attributes are:
Locale-formatted Timestamp, Severity, Subsystem, Machine Name, Server Name, Thread ID, User ID,
Transaction ID, Diagnostic Context ID, Raw Time Value, Message ID, and Message Text.
Time stamp Time and date when the message originated.
The Java Virtual Machine (JVM) that runs each WebLogic Server instance refers to the host computer
operating system for information about the local time zone and format.
Severity Indicates the degree of impact or seriousness of the event reported by the
message.
Subsystem Indicates the subsystem of WebLogic Server that was the source of the
Machine Name
Server
Name
Thread ID
message; for example, Enterprise Java Bean (EJB) container or Java
Messaging Service (JMS).
Identifies the origins of the message:
Server Name is the name of the WebLogic Server
Machine Name is the DNS name of the computer
Thread ID is the ID that the JVM assigns to the thread in which the
message originated
User ID The user ID under which the associated event was executed
Transaction ID Present only for messages logged within the context of a transaction
Diagnostic
Context ID
Raw Time Value The timestamp in milliseconds
Message ID A unique six-digit identifier
Context information to correlate messages coming from a specific request or
application
All message IDs that WebLogic Server system messages generate start with
BEA- and fall within a numerical range of 0-499999.
TechSys IT Solutions
Message Text A description of the event or condition.
No comments:
Post a Comment