IBM Support

PI09787: The xscmd routetable command incorrectly shows more than one sync replica.

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

  • When you run the routetable command, the output incorrectly
    includes more than one synchronous replica.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users running with  *
    *                  synchronous replicas enabled and using      *
    *                  template or dynamic maps or configurations  *
    *                  that use template maps such as dynamic      *
    *                  caching.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The route table output from the xscmd   *
    *                      routetable command shows extra          *
    *                      synchronous replicas.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A synchronous replica was incorrectly processed twice during
    its creation and a duplicate route entry was added to the
    table. In the SystemOut JVM log for the container running the
    synchronous replica, the following CWOBJ1533E message also
    occurs:
    SynchronousRe W   CWOBJ1533E:
    grid:mapSet1:0:[xsastats_mapSet1_grid, xsastats_mapSet1_map,
    payroll, templateMap286, templateMap287, templateMap288,
    templateMap289, templateMap290] is already in peer mode.
    

Problem conclusion

  • No immediate action is required, clients
    can still route correctly. To refresh the route table, run the
    xscmd command, triggerPlacement. Then, apply the fix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI09787

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-17

  • Closed date

    2014-02-05

  • Last modified date

    2014-02-05

  • 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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R850 PSY

       UP

  • R860 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
05 February 2014