PM10844: SECURITY IS ENABLED BUT THERE IS NO SUBJECTSOURCE PLUGIN SET ON OBJECTGRID INSTANCE, WHEN ANOTHER CONTAINER JOINS THE GRID.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • ObjectGridException exception is thrown with message "Security
    is enabled but there is no SubjectSource plugin set on the
    ObjectGrid instance", when another container joins the grid.
    
    Customer was experiencing a
    ReplicationVotedToRollbackTransactionException when a client
    attempts to update an entry in a grid where the shards have been
    re-placed. If they change the grid.xml file to specify
    securityEnabled=false, they cannot recreate the issue.  When
    security is enabled, start a third container, causing the shards
    to be re-balanced results in an FFDC entry.
    key = com.ibm.websphere.objectgrid.ObjectGridException
    com.ibm.ws.objectgrid.
    replication.PrimaryShardImpl.seizeLeadership 260
    Exception = com.ibm.websphere.objectgrid.ObjectGridException
    Source =
    com.ibm.ws.objectgrid.replication.PrimaryShardImpl.seizeLeadersh
    ip
    probeid = 260
    Stack Dump = com.ibm.websphere.objectgrid.ObjectGridException:
    Security is enabled but there is no SubjectSource plugin set on
    the ObjectGrid instance.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere eXtreme Scale        *
    *                  Version 6.1.0.5 who have enabled            *
    *                  authorization in eXtreme Scale.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: An ObjectGridException exception        *
    *                      or                                      *
    *                      ReplicationVotedToRollbackTransactionEx *
    *                      ception is thrown.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    eXtreme Scale did not have the correct authorization
    credentials
    when getting an internal session. When another container was
    started, some shards are automatically moved to the newly
    started container. During this rebalancing, the
    incorrect authorization credentials were being used, which
    resulted in the exceptions.
    

Problem conclusion

  • An interim fix will be made available for this APAR. A future
    cumulative fix will correct the problem for WebSphere eXtreme
    Scale Version 7.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM10844

  • Reported component name

    XD EXTREME SCAL

  • Reported component ID

    5724J3402

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-25

  • Closed date

    2010-04-20

  • Last modified date

    2010-04-20

  • 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

    XD EXTREME SCAL

  • Fixed component ID

    5724J3402

Applicable component levels

  • R610 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale
General

Software version:

6.1

Reference #:

PM10844

Modified date:

2010-04-20

Translate my page

Machine Translation

Content navigation