PK90943: ABSTRACTMETHODERROR IS GENERATED WHEN AN APPLICATION SERVER IS STARTED IN PROFILING MODE

6.1.0.29: Java SDK 1.5 SR11 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.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.47: WebSphere Application Server V6.1 Fix Pack 47
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: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• When an application server is started normally, the preInvoke
  method is called on com.ibm.ws.runtime.component.TxEEComponentIm
  pl.  However, when an application server is started in profiling
  mode, the preInvoke method is called on com.ibm.etools.pd.sd.run
  time.EjbCollaborator.  This results in an AbstractMethodError.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server v6.1 with the Feature Pack for EJB   *
  *                  3.0 installed                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: AbstractMethodError is generated when   *
  *                      an application is started.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an application server is started in profiling mode, there
  is an AbstractMethodError seen in the logs when the Feature
  Pack for EJB 3.0 is applied on V6.1. However when the server
  is started normally, there will not be any problem.
  

Problem conclusion

• The problem occurs due to a difference in the code path of an
  EJB method, when it is run in profiling mode. The code is
  changed in such a way that that this method is compatible
  to the arguments the caller is passing to it.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.29.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP