Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
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
WebSphere Application Server 7.0 Problem : When a newly developed Application is installed the following error is seen at application startup but application starts fine . Error seen at startup : [18.05.11 17:39:35:463 CEST] 00000008 annotations E ArchiveInputStreamData iterate unable to process input stream 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.amm.scan.util.ClassScanner.scanInputStream(ClassScann er.java: 235) at com.ibm.ws.amm.AnnotativeMetadataManagerImpl$1.applyTo(Annotativ eMetadat aManagerImpl.java:260) at com.ibm.wsspi.amm.scan.context.ArchiveInputStreamData.iterate(Ar chiveInp utStreamData.java:241) at com.ibm.ws.amm.AnnotativeMetadataManagerImpl.scan(AnnotativeMeta dataMana gerImpl.java:258) at com.ibm.ws.amm.AnnotativeMetadataManagerImpl.scan(AnnotativeMeta dataMana gerImpl.java:219) at com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(Anno tationsP rocessorImpl.java:108) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl .process Annotations(WARFileImpl.java:302) The error seen usually suggests a scenario where the ObjectWeb-provided ASM library is unable to process a Java Class file. This could be for a number of reasons, including that the .class file is corrupted.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0 deploying Java * * Enterprise Edition 5 and higher * * applications with annotations. * **************************************************************** * PROBLEM DESCRIPTION: An ArrayIndexOutOfBoundsException is * * thrown from * * AnnotativeMetadataManagerImpl during * * application installation. * **************************************************************** * RECOMMENDATION: * **************************************************************** Annotations processing, when reading class bytes, can throw a java.lang.ArrayIndexOutOfBoundsException when encountering byte values which are not valid for a class file. The exception is caught at an incorrect location during the annotations processing, leading to several problem symptoms: * Input streams are left open for too long. * The scan of some target classes is skipped. * Extra stack traces are displayed to system and trace logs. The error message will appear in wsadmin.traceout for installations via scripting. Console-based installation of the application will cause this error to appear in SystemOut.log.
Problem conclusion
An internal change was made to the annotation processing component to properly handle this failure condition. If the exception is thrown, the InputStream is properly closed and annotation scanning of the next class will continue. Logging and tracing was updated to provide additional information when this problem occurs. A work-around is to identify the classes which can not be processed and remove them from the application. The following trace specification will help with this diagnosis: com.ibm.config.annotations=finer If the classname was available to display, the following message will appear in Trace.log: Class [ CLASS_NAME ] could not be read for annotations - it will be ignored. If the classname was not available, the following will appear in Trace.log: A class could not be read for annotations. Any class that isn't readable during annotation processing may not be usable by the application and cause it to function improperly. The application deployer may need to review the application and make appropriate changes to avoid unexpected behavior. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.19 and 8.0.0.1. 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
PM40985
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-08
Closed date
2011-06-27
Last modified date
2011-06-27
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
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021