IBM Support

PH27912: CNTR5104E OR CNTR5102E OCCURS AT EJB START AFTER UPGRADING WEBSPHERE TO V8.5.5.16, V9.0.5.0, V9.0.5.1, OR V9.0.5.2

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • After upgrading to WebSphere version 8.5.5.16, 9.0.5.0,
    9.0.5.1, or 9.0.5.2, an EJB version 1.x or 2.x application with
    an EJB Local interface inheriting from both EJBLocalObject and
    java.rmi.Remote failed to start with one of the following
    errors:
    
    CNTR5104E: The xxx method on the xxx.xxx.xxxxx interface must
    be defined with the java.rmi.RemoteException exception on the
    throws clause.
    
    CNTR5102E: The xxx.xxx.yyyyy application exception that is
    defined on the xxx method of the xxx.xxx.xxxxx interface must
    not be defined as a subclass of the java.rmi.RemoteException
    exception.
    

Local fix

  • There are two work arounds:
    
    1) Add the file:
        META-INF/ibm_ejbext.properties
    
      to the EJB module with one line containing:
        containsTimedObject=false
    
    2) Deploy the application using a new version of EJBDeploy, such
    as the version included in the 8.5.5.17 install image.
     Sometimes using EJBDeploy from RAD or from an older level of
    WAS results in this problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  V8.5 or V9.0 with EJB 1.x or 2.x            *
    *                  applications                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: EJB 1.x or 2.x applications may fail to *
    *                      start with CNTR5104E if an EJB local    *
    *                      interface extends java.rmi.Remote       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The just-in-time deployment support for enterprise beans
    validates the configuration of a bean before generating the
    deployment artifacts and currently prevents a component local
    interface of an EJB 1.x or 2.x from extending java.rmi.Remote.
    When an application contains such an interface, the just-in-time
    deployment verification will prevent the application from
    starting with one or both of the following errors:
    CNTR5104E: The xxx method on the xxx.xxx.xxxxx interface must
    be defined with the java.rmi.RemoteException exception on the
    throws clause.
    CNTR5102E: The xxx.xxx.yyyyy application exception that is
    defined on the xxx method of the xxx.xxx.xxxxx interface must
    not be defined as a subclass of the java.rmi.RemoteException
    exception.
    The EJB specification does not explicitly restrict this
    configuration and using a recent version of EJBDeploy instead of
    just-in-time deployment will avoid the error.
    If an older version of EJBDeploy is used, then adding the file
    META-INF/ibm_ejbext.properties to the EJB module containing the
    following one line will also avoid the just-in-time deployment
    validation :
    containsTimedObject=false
    

Problem conclusion

  • Generally it is unexpected for an enterprise bean component
    local interface to extend java.rmi.Remote, however this is not
    prohibited by the EJB specification. The just-in-time deployment
    support for enterprise beans will be updated to allow component
    local interfaces to extend java.rmi.Remote. The error will no
    longer occur and the application will start and run as expected
    and consistent with EJBDeploy behavior.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.19, 9.0.5.6, and 20.0.0.9. For more information, see
    'Recommended Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH27912

  • 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

    2020-07-27

  • Closed date

    2020-09-29

  • Last modified date

    2020-10-02

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
05 October 2020