WebLogic Server 12c (12.2.1): Configuring and Using Log Files

 

Before You Begin

Purpose

This tutorial describes how WebLogic logging services provide facilities for writing, viewing, filtering, and listening for log messages. These log messages are generated by WebLogic Server instances, subsystems, and Java EE applications that run on WebLogic Server or in client JVMs.

Time to Complete

Approximately 40 minutes

Background

WebLogic Server subsystems use logging services to provide information about events such as the deployment of new applications or the failure of one or more subsystems. A server instance uses them to communicate its status and respond to specific events. For example, you can use WebLogic logging services to report error conditions or listen for log messages from a specific subsystem.

Each WebLogic Server instance maintains a server log. Because each WebLogic Server domain can run concurrent, multiple instances of WebLogic Server, the 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.

What Do You Need?

Operating System and Software Requirements
  • A Linux machine with version 6 or greater of Oracle Linux or Red Hat Linux
  • JDK 1.8 update 51 and above
  • Oracle WebLogic Server 12c (12.2.1) software
Prerequisites

You should have completed the following tutorials:

 

Locate and View Log Files on the File System

You can use a text editor to view messages in the current domain log file as well as older log files that the Administration Server creates per its domain-log file rotation scheme. A text editor displays all attributes of all messages that are in the log file.

 

Domain Log Files

To view domain-log messages from a text editor, perform the following steps:

Note: Do not open the log file that the server is using to store current messages. Instead, create a copy of the log file and open the copy in the text editor.

You do this because, depending on your text editor and operating system, you could prevent the server from logging messages while the original file is open in the text editor. Any changes to the file's timestamp can confuse log file rotation.

  1. Log on to the computer that hosts the Administration Server, open a terminal as oracle or any other user and change to the directory that contains the domain log file. 

    $ cd /scratch/u01/domains/mydomain/servers/AdminServer/logs

  2. List out the contents of the logs folder to verify the presence of domain log files.

    $ ls -l
total 3132
-rw-r-----. 1 oracle oinstall     501 May 31 02:28 access.log
-rw-r-----. 1 oracle oinstall 2748683 Jun 23 03:06 AdminServer.log
drwxr-x---. 2 oracle oinstall    4096 Feb 18 02:32 diagnostic_images
-rw-r-----. 1 oracle oinstall  438127 Jun 23 02:18 mydomain.log

  3. Create a copy of the mydomain.log log file.

    $ cp mydomain.log mydomain_bak.log

  4. Open the copy in the text editor.

    $ vi mydomain_bak.log

  5. For large file like these log files, the cursor keys are not the best choice. To move to end of file to view the latest messages, just type G (press ESC and type capital G):

    .
.
####<Jun 23, 2016 2:18:28 AM EDT> <Notice> <Server> <host01.example.com> <server2> <weblogic.socket.ServerListenThread> <<WLS Kernel>> <> <9f583e11-0de1-4240-a019-9972c6d3482d-0000000f> <1466662708418> <[severity-value: 32] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-002613> <Channel "Default[1]" is now listening on 2606:b400:2010:405a:221:f6ff:fe00:34%eth0:7005 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
 

Server Log Files

The server log records information about events such as the startup and shutdown of servers, the deployment of new applications, or the failure of one or more subsystems. The messages include information about the time and date of the event as well as the ID of the user who initiated the event.

The server log file is located on the computer that hosts the server instance. Each server instance has its own server log file. By default, the server log file is located in the logs directory below the server instance root directory. Perform the following steps to view the log files for the server1 managed server:

  1. In a terminal window, change to the following directory and list out the contents:

    $ cd /scratch/u01/domains/mydomain/servers/server1/logs
$ ls
access.log         server1.log       server1.out00002
diagnostic_images  server1.out       server1.out00003
server1_bak.out    server1.out00001  server1.out00004

  2. Open the server1.log file in a text editor.

    $ vi server1.log

In addition to writing messages to log files, a WebLogic Server instance can print a subset of its messages to standard out. Usually, standard out is the shell (command prompt) in which you are running the server instance. However, some operating systems enable you to redirect standard out to some other location. If you use the Node Manager to start a Managed Server, the Node Manager redirects a server's standard out to a file on the Node Manager's host computer.

By default, all messages of WARNING severity or higher are printed to standard out and messages of the DEBUG severity are not printed to standard out.

To view domain-log messages from a text editor, perform the following steps:

  1. In a terminal window, change to the following directory if required and list out the contents:

    $ cd /scratch/u01/domains/mydomain/servers/server1/logs
$ ls -l
total 3116
-rw-r-----. 1 oracle oinstall    1791 May 31 02:28 access.log
drwxr-x---. 2 oracle oinstall    4096 Mar  3 03:05 diagnostic_images
-rw-r-----. 1 oracle oinstall 2972983 Jun 23 06:01 server1.log
-rw-r-----. 1 oracle oinstall   18405 May 30 07:32 server1.out
-rw-r-----. 1 oracle oinstall  138841 Mar 11 00:25 server1.out00001
-rw-r-----. 1 oracle oinstall   18133 May 23 05:10 server1.out00002
-rw-r-----. 1 oracle oinstall   18133 May 23 07:48 server1.out00003

    Note: The server1.out file is the active server out file. Files with the name server1.out0000x (where x is a number) are archived log files. You can configure the max file size and max directory size of archived log files.

  2. Create a copy of the server1.out log file.

    $ cp server1.out server1_bak.out

  3. Open the copy in the vi text editor.

    $ vi server1_bak.out
.
.
.
<Jun 23, 2016 6:24:57 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
<Jun 23, 2016 6:24:58 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>

    Note: The above messages are the Node Manager messages while starting a Managed Server server1, the Node Manager redirects to a file on the Node Manager's host computer all messages that the server instance and its JVM would normally print to the shell (including verbosegc output).

The server log messages and log file communicate events and conditions that affect the operation of the server or the application. Some subsystems maintain additional log files to provide an audit of the subsystem's interactions under normal operating conditions.

The HTTP subsystem keeps a log of all HTTP transactions in a text file. The default location and rotation policy for HTTP access logs is the same as the server log. You can set the attributes that define the behavior of HTTP access logs for each server or for each virtual host that you define.

To locate and view HTTP, the access log file, perform the following steps:

  1. In a terminal window, change to the following directory if required and list out the contents:

    $ cd /scratch/u01/domains/mydomain/servers/server1/logs
$ ls -l
total 3116
-rw-r-----. 1 oracle oinstall    1791 May 31 02:28 access.log
drwxr-x---. 2 oracle oinstall    4096 Mar  3 03:05 diagnostic_images
-rw-r-----. 1 oracle oinstall 2972983 Jun 23 06:01 server1.log
-rw-r-----. 1 oracle oinstall   18405 May 30 07:32 server1.out
-rw-r-----. 1 oracle oinstall  138841 Mar 11 00:25 server1.out00001
-rw-r-----. 1 oracle oinstall   18133 May 23 05:10 server1.out00002
-rw-r-----. 1 oracle oinstall   18133 May 23 07:48 server1.out00003

  2. Open the access.log file in the vi text editor.

    $ vi access.log
.
.
10.240.220.252 - - [30/May/2016:07:37:43 -0400] "POST /testds/testdatasource.jsp HTTP/1.1" 200 1077
10.240.220.252 - - [30/May/2016:07:37:59 -0400] "POST /testds/testdatasource.jsp HTTP/1.1" 200 1077
10.240.220.252 - - [30/May/2016:07:41:21 -0400] "POST /testds/testdatasource.jsp HTTP/1.1" 200 1102
10.240.220.252 - - [30/May/2016:07:41:38 -0400] "POST /testds/testdatasource.jsp HTTP/1.1" 200 8498
 

Locate and View Log Files in the Administration Console

You can use the Administration Console to view the log file for any server in the domain, regardless of whether the server is located on a remote computer for which you might not have login privileges. In addition, the Administration Console's log file viewer provides filtering tools that you can use to limit the set of messages that it displays. For example, you can use the filtering tools to view only the messages that the JDBC subsystem has generated.

To view a server's log messages from the Administration Console:

  1. Using a web browser, open the following URL:

    http://host01.example.com:7001/console

  2. When the login page appears, enter the user name weblogic and password welcome1 you used to start the Administration Server.

  3. In the left pane of the Console, expand Diagnostics and select Log Files.

  4. In the Log Files table, select the radio button next to the domain log file.

  5. Click View.

    The Server Log page displays up to 500 messages in reverse chronological order. The messages at the top of the window are the most recent messages that the server has generated.

  6. Select the radio button next to the log record you want to view.

    Domain Log
    Description of this image

  7. Click View.

    Domain Log Entry
    Description of this image

  8. Similarly you can view log messages specific to any server.

 

Deploy a Sample Application for Logging

  1. Download the benefitslog.war file to the machine where your domain's administration server is located. This is a sample Java web application archive to deploy.

  2. Log in to the WebLogic Administration Console if you have logged out of a previous session.

  3. Deploying an application is a change to the domain's configuration, so you must first lock it. In the Change Center, click Lock & Edit.

  4. Under Domain Structure, click Deployments.

  5. On the right, above the Deployments table, click Install.

  6. Locate the downloaded archive file.

    1. To the right of Current Location, click the links to browse to the location where you placed the downloaded benefitslog.war file. In this tutorial, the file is in the /home/oracle/Downloads directory.
    2. Select the benefitslog.war option that is displayed after you click the link and locate the benefitslog.war file. The console fills in the Path field for you. Alternatively, you can manually enter the path and the file name in the Path field.
    3. Click Next.

  7. On the next screen, ensure that Install this deployment as an application is selected, and then click Next.

  8. On the targets screen, select server1 and server2, and then click Next.

  9. On the next screen, keep all the default values and click Next.

  10. On the review screen, select No, I will review the configuration later, and then click Finish.

  11. To activate the changes, click Activate Changes in the Change Center.

  12. Under Summary of Deployments, select Control tab.

  13. In the Deployments table, select the check box to the left of the benefits application, and then select Servicing all requests in the Start list.

  14. Click Yes to continue.

    A message indicates that a start request was sent. Momentarily, the state of the benefits application becomes "Active." This means that the application is available to those who have access to the server.

 

View the Log Messages created by the Sample Application

  1. Open a SSH terminal as the oracle user.

  2. Monitor the server1 log file.

    $ cd /scratch/u01/domains/mydomain/servers/server1/logs
$ tail -f server1.log

  3. Access the benefits application using the following URL:

    http://host01.example.com:7003/benefitslog

  4. Select all the options on application welcome page and click Get Information.

  5. Back in the terminal, view the log messages:

    ####<Jun 29, 2016 4:53:57 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190437248> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - benefits servlet> 
####<Jun 29, 2016 4:53:57 AM EDT> <Info> <HTTP> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190437342> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-101295> <Recompiling JSP [ServletContext@539025667[app:benefitslog module:benefitslog.war path:null spec-version:3.1]], resource [/company.jsp], because it is stale. It was previously compiled using a different version of WebLogic Server.
 JSP build version: 12.1.1.0
 WebLogic Server build version: 12.2.1.0.0.> 
####<Jun 29, 2016 4:54:01 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190441211> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - company> 
####<Jun 29, 2016 4:54:01 AM EDT> <Info> <HTTP> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190441213> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-101295> <Recompiling JSP [ServletContext@539025667[app:benefitslog module:benefitslog.war path:null spec-version:3.1]], resource [/health.jsp], because it is stale. It was previously compiled using a different version of WebLogic Server.
 JSP build version: 12.1.1.0
 WebLogic Server build version: 12.2.1.0.0.> 
####<Jun 29, 2016 4:54:01 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190441432> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - health> 
####<Jun 29, 2016 4:54:01 AM EDT> <Info> <HTTP> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190441437> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-101295> <Recompiling JSP [ServletContext@539025667[app:benefitslog module:benefitslog.war path:null spec-version:3.1]], resource [/vision.jsp], because it is stale. It was previously compiled using a different version of WebLogic Server.
 JSP build version: 12.1.1.0
 WebLogic Server build version: 12.2.1.0.0.> 
####<Jun 29, 2016 4:54:01 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190441724> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - vision> 
####<Jun 29, 2016 4:54:01 AM EDT> <Info> <HTTP> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190441727> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-101295> <Recompiling JSP [ServletContext@539025667[app:benefitslog module:benefitslog.war path:null spec-version:3.1]], resource [/dental.jsp], because it is stale. It was previously compiled using a different version of WebLogic Server.
 JSP build version: 12.1.1.0
 WebLogic Server build version: 12.2.1.0.0.> 
####<Jun 29, 2016 4:54:02 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000017> <1467190442013> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - dental>

  6. The application does have debug messages but you don't see them in the log. In the next section you will increase the Log Severity to view the debug messages.

 

Increase the Log Severity

Increase the Log Severity to view the 'DEBUG' messages by performing the following steps:

  1. In the WebLogic administration console, click servers under Environment in the Domain Structure.

  2. Click on the server1 link in the Servers table.

  3. In the Change Center, click Lock & Edit.

  4. On the Settings for server1 page, select the Logging tab in the first row of tabs.

  5. Scroll down the Logging > General tabbed page and click on Advanced to expand it.

  6. Select Debug from the Minimum severity to log drop down field.

    Settings for server1
    Description of this image

  7. Click Save.

  8. In the Change Center, click Activate Changes.

  9. Access the benefits application using the following URL:

    http://host01.example.com:7003/benefitslog

  10. Select all the options on application welcome page and click Get Information.

  11. Back in the terminal, view the log messages:

    ####<Jun 29, 2016 6:02:30 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550979> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - benefits servlet> 
####<Jun 29, 2016 6:02:30 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550979> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - benefits servlet> 
####<Jun 29, 2016 6:02:30 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550980> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - company> 
####<Jun 29, 2016 6:02:30 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550980> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - company> 
####<Jun 29, 2016 6:02:30 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550980> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - health> 
####<Jun 29, 2016 6:02:30 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550980> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - health> 
####<Jun 29, 2016 6:02:30 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550980> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - vision> 
####<Jun 29, 2016 6:02:30 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550980> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - vision> 
####<Jun 29, 2016 6:02:30 AM EDT> <Info> <ServletContext-/benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550981> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - dental> 
####<Jun 29, 2016 6:02:30 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000018> <1467194550981> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - dental>

  12. Good, now you can see the 'Debug' messages along with the 'Info' messages. However, you want to view only 'Debug' messages. In the next section you will create a Log Filter to view only the 'Debug' messages.

 

Creating a Log Filter

To create a Log Filter, perform the following steps:

  1. In the WebLogic administration console, click mydomain in the Domain Structure.

  2. In the Change Center, click Lock & Edit.

  3. Select Configuration > Log Filters tab on the Settings for mydomain page.

  4. Click the New button in the Log Filters section.

  5. On the Create a New Log Filter page, enter DebugLogFilter in the Name field and click OK.

  6. Back on the Settings for mydomain page, click on the newly created DebugLogFilter Log Filter link under the Log Filters section of the page.

  7. On the Settings for DebugLogFilter page, enter (SEVERITY = 'Debug') in the Current Log Filter Expressions field and click Save.

  8. In the Change Center, click Activate Changes.

 

Apply the Log Filter to a Managed Server

  1. In the WebLogic administration console, click servers under Environment in the Domain Structure.

  2. Click on the server1 link in the Servers table.

  3. In the Change Center, click Lock & Edit.

  4. On the Settings for server1 page, select the Logging tab in the first row of tabs.

  5. Scroll down the Logging > General tabbed page and click on Advanced to expand it.

  6. In the Advanced section, under Message destination(s), select DebugLogFilter from the Log file > Filter drop down and click Save.

    Settings for server1
    Description of this image

  7. In the Change Center, click Activate Changes.

  8. Access the benefits application using the following URL:

    http://host01.example.com:7003/benefitslog

  9. Select all the options on application welcome page and click Get Information.

  10. Back in the terminal, view the log messages:

    ####<Jun 29, 2016 6:48:27 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000019> <1467197307931> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - benefits servlet>
####<Jun 29, 2016 6:48:27 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000019> <1467197307931> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - company> 
####<Jun 29, 2016 6:48:27 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000019> <1467197307932> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - health> 
####<Jun 29, 2016 6:48:27 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000019> <1467197307932> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - vision> 
####<Jun 29, 2016 6:48:27 AM EDT> <Debug> <benefitslog> <host01.example.com> <server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0cdec41d-0238-4ce1-92a6-b2610311edba-00000019> <1467197307932> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <benefits log - dental>
 

Want to Learn More?

 

Credits

  • Lead Curriculum Developers: Tom Eliason, Veerabhadra Rao Putrevu