Fixes are available
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
The annotation scanning filter doesn't work when the filter is specified in the MANIFEST.MF of the application.
Local fix
na
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM WebSphere Application * * Server attempting to use annotation * * scanning filters for an application that * * uses CDI. * **************************************************************** * PROBLEM DESCRIPTION: The CDI component of the WebSphere * * Application Server does not respect * * annotation filter properties. * **************************************************************** * RECOMMENDATION: * **************************************************************** Filter properties allow you to specify JAR files in your application that do not contain Java EE annotations. Including a JAR in a filter causes the JAR to be skipped during annotation processing. This makes deploying your application faster. However, the WebSphere Application Server CDI component ignores these filter properties which causes the JARs to be scanned anyway. The filter properties include the following: JVM custom properties - com.ibm.ws.amm.scan.context.filter.archives - com.ibm.ws.amm.scan.context.filter.packages MANIFEST.MF properties - Ignore-Scanning-Archives - Ignore-Scanning-Packages amm.filter.properties file properties - Ignore-Scanning-Archives - Ignore-Scanning-Packages More information about these properties can be found in the "Java virtual machine custom properties" section of the IBM Knowledge Center for WebSphere Application Server traditional 9.0.0.x.
Problem conclusion
The CDI code has been updated. It now uses filter properties to avoid scanning filtered JARs for annotations. Note that JARs will be filtered regardless of whether the JAR contains a beans.xml. This means you should not filter a JAR containing a beans.xml unless you want to ignore CDI in the JAR. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.8. 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
PI89821
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-11-03
Closed date
2018-01-24
Last modified date
2018-01-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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
04 May 2022