Fixes are available
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
During the deployment of an application on servers with WebService and/or Enterprise JavaBeans 3.0 Feature Packs, the AnnotationException error was received: ADMA5006E: An error occurred configuring <xyz> in WebSphere Application Server repository: com.ibm.ws.metadata.annotations.AnnotationException: Annotation processing failed for class: processing failed for class: COM/ibm/db2os390/sqlj/custom/DB2SQLJCustomizer.class . Further detailed errors were displayed in the log: . ?7/15/08 9:03:06:949 CEST? 00000043 SystemErr R Annotation com.ibm.ws.metadata.annotations.AnnotationException: Annotation processing failed for class: COM/ibm/db2os390/sqlj/custom/DB2SQLJCustomizer.class . ?7/15/08 9:03:06:949 CEST? 00000043 SystemErr R Caused by: java.lang.ArrayIndexOutOfBoundsException at org.objectweb.asm.ClassReader.readClass(Unknown Source) at org.objectweb.asm.ClassReader.accept(Unknown Source) at org.objectweb.asm.ClassReader.accept(Unknown Source) at com.ibm.ws.metadata.annotations.AnnotationConfigReader.getAnno tationData(AnnotationConfigReader.java:439)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM WebSphere Application * * Server V6.1 Feature Pack for Web Services * * or the IBM WebSphere Application Server * * V6.1 Feature Pack for EJB 3.0 * **************************************************************** * PROBLEM DESCRIPTION: 'AnnotationException' caused when a * * corrupt Java class is scanned for * * annotations. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the WebSphere Application Server scans classes in an application, and if the application contains a corrupt Java class, the scan will result in an 'AnnotationException' when the corrupt class is scanned. For example, in this APAR the following exception is caused: com.ibm.ws.metadata.annotations.AnnotationException: Annotation processing failed for class: COM/ibm/db2os390/sqlj/custom/DB2SQLJCustomizer.class For a very brief amount of time, a db2jcc.jar was shipped on zOS where the 'DB2SQLJCustomizer.class' it contained was corrupt. This has since been corrected by IBM. However, if a user still has a copy of this corrupt class contained in the db2jcc.jar, and the user places this jar in their application, every class in that jar will be scanned for annotations when the application is started. When the 'DB2SQLJCustomizer.class' is scanned, the 'AnnotationsException' will be thrown. This exception is not expected by the WebSphere Application Server and results in the application's failure to start. It is worth noting that for the particular 'AnnotationException' resulting from the 'DB2SQLJCustomizer.class', a user should consult IBM support in order to obtain the corrected db2jcc.jar. This is just one example of a corrupt class causing an 'AnnotationException' and this APAR is not limited to just the corrupt 'DB2SQLJCustomizer.class' class; any corrupt class which is attempted to be scanned will result in the same exception.
Problem conclusion
This APAR will provided code to catch, and handle, the 'AnnotationException' when the exception is caused by an attempt to scan a corrupt Java class for annotations. The user will ultimately need to address and fix the corrupt class. However, the 'AnnotationException' should be gracefully handled by WebSphere Application Server and allow the application to start. This APAR will add code to gracefully handle the 'AnnotationException' by logging a warning message in the system logs and allowing the application to start. APAR PK69454is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.23 of WebSphere Application Server V6.1 for z/OS. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PK69454
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-07-23
Closed date
2008-11-12
Last modified date
2009-04-02
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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R610 PSY UK44403
UP09/03/21 P F903
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
28 December 2021