IBM Support

PM48850: INTERCEPTOR CLASS ASSOCIATED WITH EJB NOT CALLED DURING EJB REQUEST.

Fixes are available

7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • An interceptor class associated with an enterprise bean is not
    called during EJB request. This is due to thread safety problem
    during handling interceptor metadata. If multiple EJBs from
    the same module are started concurrently then the interceptor
    metadata for one of the EJBs could be lost.
    
    Only StatelessSessionBean and StatefulSessionBean
    with interceptors could be effected.
    This could happen if JAR file is with multiple EJBs
    and it would not happen with the case if EAR with
    multiple JAR files, but only 1 EJB per JAR file.
    

Local fix

  • configuring the EJBs to start at application start.
    com.ibm.websphere.ejbcontainer.initializeEJBsAtStartup
    
    OR
    
    configure only individual beans to start at application start
    with ibm-ejb-jar-ext.xml file:
      <session name="[bean-name]">
          <start-at-app-start value="true"/>
      </session>
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 with Enterprise Java Bean (EJB) *
    *                  applications that use interceptors.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Intermittently, the interceptor         *
    *                      methods for an EJB may not be           *
    *                      called.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Beginning with EJB 3.0, session beans (stateless and stateful)
    may be configured to have around-invoke interceptor methods.
    These methods should be called before and after every EJB
    method request.
    Intermittently, when an application is started, one (or more)
    of the EJBs in the application may experience a problem where
    the interceptor methods are not called. This will persist
    until the application is re-started.
    The symptoms will vary, depending on what the interceptor
    method is intended to accomplish.
    

Problem conclusion

  • This problem is due to a thread safety problem during EJB
    initialization, when handling interceptor metadata. If multiple
    EJBs from the same module are started concurrently then the
    interceptor metadata for one of the EJBs can be lost.
    
    The EJB container code has been updated to correct this thread
    safety problem.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.21.  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

    PM48850

  • 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-09-27

  • Closed date

    2011-10-24

  • Last modified date

    2011-10-24

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM48850

Modified date: 24 October 2011