Fixes are available
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
Different layers of WebSphere Application Server code handle the property differently. One layer filters files based on the relative path, while another layer filters based on the file name.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server who set the custom property * * com.ibm.ws.amm.scan.context.filter.archives * * or who create an "amm.filter.properties" * * file to filter JAR files from annotation * * scanning. * **************************************************************** * PROBLEM DESCRIPTION: JAR files specified by the * * com.ibm.ws.amm.scan.context.filter.arch * * ives custom property or in the * * amm.filter.properties file are * * not filtered from all * * annotation scanning as expected. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Annotations Metadata Manager (AMM) code layer filters JAR files from annotation scanning based on the JAR file name only. This is working as intended. When you specify JAR files that are to be filtered, you specify only the JAR file name, not the path to the JAR file. However, the Extensible Class Scanner (ECS) layer incorrectly compares JAR file names (from the list of JAR file names to be filtered) against the path to the JAR from the root of the archive containing the JAR. Thus, the JAR files are not filtered correctly by the ECS layer. The result is the full performance benefit of filtering certain JAR files from scanning is not attained.
Problem conclusion
The ECS code layer has been updated to filter based on the simple JAR file name. A custom property is provided to disable this fix. If you want the prior behavior where the AMM layer properly filters JAR files from annotation scanning, but the ECS layer does not, then set the new property com.ibm.ws.amm.scan.context.filter.disable.unify=true to revert back to the mismatched filtering. To set the property, open the Administration Console, click Servers > Server Types > WebSphere application servers > server_name, and then, under Server Infrastructure, click Java and process management > Process definition > Java virtual machine > Custom properties. If the custom property is not present in the list of already defined custom properties, create a new property, and enter the property name in the Name field and a valid value in the Value field. Restart the server to complete your changes. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.7, and the fix pack following 8.5.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
PM80038
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-07
Closed date
2013-03-12
Last modified date
2013-03-12
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
R800 PSY
UP
R850 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 November 2021