IBM Support

PI49157: App Server Classic to Liberty profile remote EJB lookup is not w orking when CSIv2 uses LTPA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For a remote EJB lookup from WebSphere Application Server
    Classic to WebSphere Application Server Liberty profile, the
    lookup fails with a NamingException  containing an
    org.omg.CORBA.NO_MEMORY in the trace.log similar to the
    following,
    
    Exception: javax.ejb.EJBException: Injection failure; nested
    exception is: javax.naming.NamingException: The JNDI
    operation "lookupExt" on the context "" with the name
    "ejb/global/AppName/EjbName/Bean!your.bean.RemoteInterface"
    failed. Please get the root cause Throwable contained in
    this NamingException for more information. [Root exception
    is org.omg.CORBA.NO_MEMORY: vmcid: 0x41534000 minor code: 1
    completed: Maybe]
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile - Security           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application Server classic to Liberty   *
    *                      profile remote EJB lookup is not        *
    *                      working when CSIv2 uses LTPA            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For a remote EJB lookup from WebSphere Application Server
    Classic to WebSphere Application Server Liberty profile, the
    lookup fails with a NamingException  containing an
    org.omg.CORBA.NO_MEMORY in the trace.log similar to the
    following,
    
    Exception: javax.ejb.EJBException: Injection failure; nested
    exception is: javax.naming.NamingException: The JNDI operation
    "lookupExt" on the context "" with the name
    "ejb/global/AppName/EjbName/Bean!your.bean.RemoteInterface"
    failed. Please get the root cause Throwable contained in this
    NamingException for more information. [Root exception is
    org.omg.CORBA.NO_MEMORY: vmcid: 0x41534000 minor code: 1
    completed: Maybe]
    

Problem conclusion

  • The code was modified to properly decode and encode the LTPA
    token in the format used by WebSphere Application Server Classic
    when communicating with a WebSphere Application Server classic
    server.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.8.  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

    PI49157

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-09-22

  • Closed date

    2015-09-24

  • Last modified date

    2015-09-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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

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

Document Information

Modified date:
17 October 2021