Business Service Logging Also Written to WebLogic Managed Server stdout in Addition to the Usual Logfile - Leads to Growing Weblogic Server Domain Logfile "eSeries-01.out"
Last updated on JULY 11, 2016
Applies to:Oracle Agile Engineering Data Management - Version 18.104.22.168 to 22.214.171.124 [Release 6.1.0]
Information in this document applies to any platform.
***Checked for relevance on 20-Jun-2014***
Find advanced Business Service logging output written into two log files
- in Business Service log file .../Middleware/user_projects/domains/eSeries_domain_<app-name>/<hostname>-<app-name>.log
- in Server "eSeries-01" out file .../Middleware/user_projects/domains/eSeries_domain_<app-name>/servers/eSeries-01/logs/eSeries-01.out
Business Service log file <hostname>-<app-name>.log "rotates" as defined in related log4j.properties file
but Server "eSeries-01" out file - eSeries-01.out - DOES NOT rotate and grows in size ... might lead to partition running out of space ...
How to avoid writing Business Service logging into file "eSeries-01.out" ?
Steps to Reproduce:
1.) Activate advanced Business Service logging (e.g. SQL-Trace) via modifications in file
as follows - activate (or add) lines:
2.) Redeploy Business Service
3.) Find advanced Business Service logging - SQL-Trace - output written into two log files
- in Business Service log file .../.../<hostname>-<app-name>.log
- in Server "eSeries-01" out file .../.../servers/eSeries-01/logs/eSeries-01.out
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms