Skip Headers
Oracle® Fusion Middleware Publishing Reports to the Web with Oracle Reports Services
11g Release 1 (11.1.1)

Part Number B32121-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

24.2 Logging Enhancements

Oracle Reports 11g Release 1 (11.1.1) provides Logging enhancements in the following areas:

Table 24-2 provides a list of enhanced log messages:

Table 24-2 Example enhanced logging messages.

Enhancement Sample Output

Security

 

Start

SecurityHelper:start

JAZNSecurity

RWJAZNSecurity:jobCommandCheck Authorization check started

ReportsActionHandler

ReportsActionHandler:run Checking job command permission

JAZNSecurity

JAZNSecurity:jobCommandCheck Authorization check passed for job 1

JAZNSecurity

RWJAZNSecurity:authenticate Authenticated User weblogic successfully

Job Administration

 

ConnectionImpl

ConnectionImpl:runJob Calling findDuplicatedJob for jobid = 1

JobManager

JobManager:findDuplicatedJob Found no duplicated job for job 1

ConnectionImpl

ConnectionImpl:runJob No Duplicate jobs for jobid=1

Upgrade

 

Upgrade Framework

reports app is deployed to managed server WLS_REPORTS

Upgrade Framework

ReportsServerComponent component is configured in destination instance

Upgrade.Reports

Creating reports specific upgrade items

Upgrade.Reports

Creating reports specific upgrade items complete.

High Availability

 

JOC Caching

ReportsCacheHandler: putFile File <fileName> pushed to JOC

Font

For more information on font related log enhancements, see Section 12.2.3, "Font Diagnosis and Tracing"


24.2.1 Diagnosing Engine Crashes

This section discusses recommended settings in logging configuration to diagnose engine crashes.

Sometimes it is difficult to diagnose an engine crash as you do not find all log messages in the log file, especially when the log messages are generated just prior to an engine crash.

Due to performance reasons, the logging framework buffers the logs in memory and then flushes the logs periodically to log files. If an engine crashes suddenly, the logging framework may not get a chance to flush the logs from buffer to the file before the engine process exits. As a result, the logging information which had to be logged before an engine crash may not be available in the log file.

To diagnose an engine crash and to see all the log entries, perform the following steps:

For rwserver

  • Navigate to the Reports Server logging.xml file located at:

    ORACLE_INSTANCE/config/ReportsServerComponent/<server name>/logging.xml( For Standalone Servers)

    $DOMAIN_HOME/config/fmwconfig/servers/WLS_REPORTS/logging.xml ( For In-process Servers)

  • Set the value of autoFlushLevel for engine log handler to TRACE:32.

    For example,

    <log_handler name='rwengine_trace_handler' ....>
       <property name='autoFlushLevel' value='TRACE:32'/>
        ...
    

For rwrun

  • Navigate to the logging.xml file located at ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools/logging.xml

  • Set the value of autoFlushLevel for engine log handler to TRACE : 32.

    For example,

    <log_handler name='runtime_trace_handler' ...>
       <property name='autoFlushLevel' value='TRACE:32'/>
        ...
    

By default, NOTIFICATION :1 messages are flushed immediately. If you set the value of the autoFlushLevel parameter to TRACE : 32 for any message, the log messages are flushed to the file immediately. As continuous flushing affects performance, it is recommended that you set the autoFlushLevel for diagnostic purposes only.