PM63189: SCANS OF APPLICATION CLASSES FAIL WITH AN ARRAYINDEXOUTOFBOUNDS WITHOUT DISPLAYING INFORMATION ABOUT THE NON-VALID CLASS.

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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

• Title: ArrayIndexOutOfBoundsException from ClassReader does not
  display failing class information
  
  Abstract: Scans of application classes fail with an
  ArrayIndexOutOfBoundsException without displaying information
  about the non-valid class.
  
  Description: When processing an application, either for
  deployment or for startup, depending on the settings of the
  application, the classes of the application may need to be
  scanned for annotations.  When the scan encounters a non-valid
  class, an exception is thrown, but no information is displayed
  about the non-valid class.
  
  For example:
  
  java.lang.ArrayIndexOutOfBoundsException: 27682
  Caused by: java.lang.ArrayIndexOutOfBoundsException: 27682
   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
  org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.EJBModul
  eLocator.locateAnnotations(EJBModuleLocator.java:257)
  
  The failure is appropriate, however, because no class
  information is displayed, identifying the failing class is very
  difficult. Appropriate information about the class should
  include the name and location of the class in the application
  which is being scanned.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 and V8.5 using annotations      *
  *                  enabled applications                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Deployment or startup fails with        *
  *                      ArrayIndexOutOfBoundsException from     *
  *                      class org.objectweb.asm.ClassReader.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When processing an application, if the application is scanned
  for annotations, an ArrayIndexOutOfBoundsException is thrown
  when a non-valid class is processed.  The exception is logged,
  but no information identifying the non-valid class is logged.
  Processing is performed during application deployment and
  during application startup.  In either case, the exception
  causes the operation to fail.
  The exception is thrown by org.objectweb.asm.ClassReader.  For
  example:
  java.lang.ArrayIndexOutOfBoundsException: 27682
  Caused by: java.lang.ArrayIndexOutOfBoundsException: 27682
  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
  org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.EJBModul
  eLocator.locateAnnotations(EJBModuleLocator.java:257)
  That an error is thrown upon encountering a non-valid class
  file is correct.  That the exception causes a failure of the
  overall operation is incorrect.  The exception should be
  caught and displayed as a warning, and the operation should
  proceed.  In particular, the warning that is displayed should
  identify the class which is non-valid.
  

Problem conclusion

• The annotation scanning code was updated to capture the
  exception and log the exception as a warning.  The log
  messages were updated to include the name and location of the
  class which caused the exception.  The annotation scanning
  code was updated to continue processing following the failure.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.0.0.5 and 8.5.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 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

• R850 PSY

     UP