PH54978: SLOWNESS CAUSED BY UNNECESSARY SCANNING FOR EJB CONTENT

APAR status

• Closed as program error.

Error description

• Adding a dynamic cluster member failed with
  "Message: ADMG9212E: Exception caught executing
  createClusterMember command: java.lang.NullPointerException"
  It runed out to be a problem with annotation scanning.
  
  Annotation scanning of application JAR files occurs during
  application start.  Recording of whether a JAR contains EJB
  content is recorded during application deployment, and it is
  therefore unnecessary to rescan for EJB content during
  application start.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server adding dynamic cluster members       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unnecessary delay caused by scanning    *
  *                      applications for EJB content when       *
  *                      adding a dynamic cluster member.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Application Server traditional scans applications
  during deployment and records information about them in an
  application deployment.xml file.  One piece of information
  that is recorded is whether the application contains EJB
  content. The application server fails to use this information
  during the process of adding a dynamic cluster member.
  When adding a dynamic cluster member, the application server
  needs to determine if the new node supports all of the
  applications in the cluster.  Part of this process is to
  determine if each application contains EJB content.  The
  application server is failing to use the information that it
  recorded in the deployment.xml during deployment, and instead
  it re-scans all applications looking for EJB content.   This
  causes an unnecessary delay when adding a dynamic cluster
  member.
  

Problem conclusion

• WebSphere Application Server traditional has been updated to
  use the EJB content information in deployment.xml, which
  avoids unnecessary scanning of applications.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.17. For more information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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