IBM Support

PI27374: CREATEFAILUREEXCEPTION WHEN APPLICATION IS RE-DEPLOYED

Fixes are available

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.45: Java SDK 1.6 SR16 FP60 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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The ClientDelegate cache (that is maintained by the ws390 ORB)
    allows the ORB to manage the state of the ClientDelegate across
    application restarts.  It is dropping cache entries prematurely
    and therefore fails to properly disconnect and reconnect the
    ClientDelegate to the new EJB after the app restart.
    
    The joblog shows this error:
    
    Trace: 2014/09/02 08:43:11.767 02 t=AB3690 c=UNK key=P8 tag=
    (13007004)
    SourceId: com.ibm.ejs.container.RemoteExceptionMappingStrategy
    ExtendedMessage: BBOO0220E: CNTR0019E: EJB threw an unexpected
    (non-declared) exception during invocation of method "create".
    Exception data: com.ibm.ejs.container.CreateFailureException: ;
    nested exception is:
    com.ibm.websphere.ejbcontainer.EJBStoppedException: The
    referenced version of the CommonPolicyBatchController bean in
    the customer_app application has been stopped and may no longer
    be used. If the customer_app application has been started
    again, a new reference for the new image of the
    CommonPolicyBatchController bean must be obtained. Local
    references to a bean or home are no longer valid once the
    application has been stopped.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: COM.IBM.EJS.CONTAINER.CREATEFAILURE     *
    *                      EXCEPTION WHEN APPLICATION IS RE-       *
    *                      DEPLOYED                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The ClientDelegate cache that allows the ORB to manage the state
    of the ClientDelegate across application restarts drops cache
    entries prematurely and therefore fails to properly disconnect
    and
    reconnect the ClientDelegate to the new EJB after the app
    restart.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI27374

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-09

  • Closed date

    2015-01-13

  • Last modified date

    2015-04-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PI32648

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022