IBM Support

PM81123: A potential segmentation fault can occur for eXtreme Scale maps that use the HashIndex.

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

  • A trace condition exists that might lead to a segmentation
    fault for eXtreme Scale maps that use indexing. This problem
    occurs when you query an index on a map while entries are
    being removed from the map.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users who have      *
    *                  enabled eXtremeMemory (XM) and use the      *
    *                  built-in HashIndex plug-in                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Container servers can fail if you       *
    *                      query an index while removing entries   *
    *                      from the same map.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If you have enabled eXtremeMemory and use the
    built-in HashIndex plug-in, a container server might
    experience a segmentation fault.  This problem happens if you
    remove entries from a map while simultaneously running index
    queries on the map.
    You can determine when this problem occurs when a container
    disappears and leaves a Java core file in its working
    directory.  The Java core file contains a stack trace that goes
    through one of the find methods on the HashIndex class.
    

Problem conclusion

  • This issue is resolved in V8.6 Fix Pack 1. However, you can
    avoid this problem by not running index queries while removing
    entries from the same map.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM81123

  • 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

    2013-01-22

  • Closed date

    2013-01-29

  • Last modified date

    2013-01-29

  • 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

  • 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:
29 January 2013