Fixes are available
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
The restrictive list will not be applied if the logger is not a patterend logger (patterned logger contains an asterisk at the end). For example, when updating the ras.rawtracelist.properties file available in the cell configuration with: com.abc.logger=FINE When the sensitive filter is enabled (for disabling of sensitve data), logging events from the logger com.abc.logger with a level of FINER should not appear in the log files, even if the tracespec is set to *=FINEST. However, since the messages with the level FINER are still appearing in the trace output, it means the sensitive filtering did not go into effect for this logger.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: A list of restricted loggers and * * their levels of restriction can be * * listed in ras.rawtracelist.properties * * file. * * Example patterns are: * * com.abc.logger = FINEST * * com.xyz.def.logger.*=FINEST * * When the logger ends in an asterisk * * (to indicate a pattern), * * its restriction is applied correctly. * * The problem occurs when the logger * * does not contain an asterisk (to * * indicate an exact match logger) such * * as com.abc.logger=FINEST. * * Non-patterned loggers and its * * restriction do not get applied. * **************************************************************** * RECOMMENDATION: * **************************************************************** Fix has been added to include non-patterned loggers listed in the restrict list when applying sensitive data filtering.
Problem conclusion
The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.2. 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
PM49430
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-10-05
Closed date
2011-10-24
Last modified date
2011-10-24
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
28 October 2021