IBM Support

PI90013: 30 SECOND DELAYS FOR REMOTE EJBS WHEN RUNNING AS A COLLECTIVE MEMBER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an application is run in a collective or cluster, it is
    very slow to start. This seems to happen only on the server
    that doesn't run on the same machine as the controller. For
    every remote EJB in the application there is a 30 second
    delay.
    This delay always occurs when trying to call the EJBs, which
    leads to transaction timeouts.
    
    By enabling trace loggging on
    com.ibm.ws.ejbcontainer.osgi.internal.EJBRuntimeImpl, the
    sleep
    is inside waitForEJBRemoteRuntime.  Also, setLibertyFeature
    is
    called late, after setEJBRemoteRuntime. If setLibertyFeature
    is
    called after setEJBRemoteRuntime, the
    remoteFeatureLatch will never be counted down, so the 30
    second
    delay will always be present.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Enterprise Java Beans      *
    *                  (EJB)                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Intermittently, all calls to remote EJB *
    *                      methods may take an extra 30 seconds.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There is a timing problem during application server start such
    that the core EJB container feature does not recognize that the
    EJB remote feature has successfully started, and therefore waits
    up to 30 seconds for the remote feature to start before routing
    remote EJB method calls.
    
    Restarting the server process generally resolves the issue.
    

Problem conclusion

  • The server startup issue has been corrected. The EJB container
    will be properly notified when the EJB remote feature has
    started and the EJB remote method calls will be routed
    immediately.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.4.  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

    PI90013

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-09

  • Closed date

    2017-11-22

  • Last modified date

    2017-11-22

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 June 2020