Fixes are available
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The customer has an application that will frequently log a FileNotFoundException in the SystemOut.log which fills the logs over time. They are aware of the file that is missing and would like to suppress the FileNotFoundException from being logged at all.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server version * * 7.0 users. * **************************************************************** * PROBLEM DESCRIPTION: FileNotFoundException is logged * * several times in the SystemOut.log * **************************************************************** * RECOMMENDATION: * **************************************************************** FileNotFoundException stack is logged in the system log when dispatching an include to a non-existent static resource. Some applications are designed to deliberately include a dynamic static resource which might not exist at the dispatching time. This can cause the exceptions to be thrown, accumulate in the log, and eventually increase the log files over time. Also if a filter is used, the exception might not be thrown back to the caller for handling.
Problem conclusion
The WebContainer code was modified to suppress the FileNotFoundException in the system log. The exception will be logged in the server trace if it is enabled. The exception is also conveyed back to the caller for handling. New WebContainer customer properties need to be set to enable the behavior provided by this APAR: To suppress the FileNotFoundException in the SystemOut.log: com.ibm.ws.webcontainer.suppressLoggingFileNotFoundExceptions = true (default is false) To re-throw the FileNotFoundException to the caller: com.ibm.ws.webcontainer.rethrowExceptionFromFilter = true (default is false) Please refer to the following technote for instructions on enabling WebContainer custom properties: http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395 The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.29. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM74342
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-04
Closed date
2012-12-05
Last modified date
2012-12-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
29 October 2021