IBM Support

PK86285: MISSING REALM ATTRIBUTE CAUSES FAILURE TO REGISTER SERVERS WITH WITH THE LOCATION SERVICE.

Fixes are available

6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
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
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
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

  • When the realm attribute does not exist as part of the
    registry configuration there is the failure to register the
    servers with the location service.  This results in not being
    able to get a direct IOR from an indirect IOR.  This can
    negatively impact high availability if the location
    service cannot dynamically determine the server that a given
    object (for example, a bean's home object) resides in.
    
    org.omg.CORBA.NO_PERMISSION
    com.ibm.ws.security.auth.ContextManagerImpl.runAs 4101
    Exception = org.omg.CORBA.NO_PERMISSION
    Source = com.ibm.ws.security.auth.ContextManagerImpl.runAs
    probeid = 4101
    Stack Dump = org.omg.CORBA.NO_PERMISSION:
    >> SERVER (id=11c328fe, host=austin.ibm.com) TRACE
    START:
    >>    org.omg.CORBA.NO_PERMISSION: Failed to verify caller
    subject
    vmcid: 0x49424000  minor code: 303  completed: No
    >>  at
    com.ibm.ws.orbimpl.services.lsd.LocationServiceImpl.register_ser
    ver(Loca
    tionServiceImpl.java:177)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application Server
    ****************************************************************
    * PROBLEM DESCRIPTION: For a WebSphere Application Server, a   *
    *                      missing realm attribute in the custom   *
    *                      user registry definition in the         *
    *                      security.xml causes the a failure to    *
    *                      register the server with the location   *
    *                      service.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For WebSphere Application Server, when the realm attribute for
    a custom user registry is missing from the security.xml file,
    the registration of the server with the location service fails
    with a org.omg.CORBA.NO_PERMISSION exception. The stack trace
    in the node agent process looks like,
    
    org.omg.CORBA.NO_PERMISSION
    com.ibm.ws.security.auth.ContextManagerImpl.runAs 4101
    Exception = org.omg.CORBA.NO_PERMISSION
    Source = com.ibm.ws.security.auth.ContextManagerImpl.runAs
    probeid = 4101
    Stack Dump = org.omg.CORBA.NO_PERMISSION:
     >> SERVER (id=11c328fe, host=hostname) TRACE
    START:
     >>    org.omg.CORBA.NO_PERMISSION: Failed to verify caller
    subject
    vmcid: 0x49424000  minor code: 303  completed: No
     >>  at
    com.ibm.ws.orbimpl.services.lsd.LocationServiceImpl.register_ser
    ver(LocationServiceImpl.java:177)
    

Problem conclusion

  • The security code was modified to attempt to obtain the realm
    name from the user registry if the realm name attribute is not
    available in the security.xml file.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.29 and 7.0.0.13.  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

    PK86285

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-11

  • Closed date

    2010-04-19

  • Last modified date

    2010-04-19

  • 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 APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PK86285

Modified date: 19 April 2010