IBM Support

PI86927: An ArrayIndexOutOfBoundsException exception can occur when using a global index.

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

  • An ArrayIndexOutOfBoundsException exception can happen
    intermittently with the following exception stack.
    
    java.lang.ArrayIndexOutOfBoundsException: Array index out of
    range: -1
     at java.util.BitSet.length(BitSet.java:860)
     at com.ibm.ws.objectgrid.index.agent.GetPartitionsAgent.getPart
    itions(GetPartitionsAgent.java:180)
     at com.ibm.ws.objectgrid.index.agent.GetPartitionsAgent.process
    (GetPartitionsAgent.java:111)
     at com.ibm.ws.objectgrid.datagrid.EntryAgentCommand.processAgen
    t(EntryAgentCommand.java:140)
     at com.ibm.ws.objectgrid.datagrid.EntryAgentCommand.executeComm
    and(EntryAgentCommand.java:286)
     at com.ibm.ws.objectgrid.AbstractDistributedCommand.run(Abstrac
    tDistributedCommand.java:73)
     at com.ibm.ws.objectgrid.thread.ThreadPoolRunnable.run(ThreadPo
    olRunnable.java:58)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of eXtreme Scale who use GlobalIndex  *
    *                  function on a map that is not using a       *
    *                  CopyMode of COPY_TO_BYTES or                *
    *                  COPY_TO_BYTES_RAW                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: An ArrayIndexOutOfBoundException        *
    *                      occurs when getting the partitions      *
    *                      that have entries for a particular      *
    *                      index value.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When update a global index due to changes to the map (entry
    deleted, map cleared, or entry added or updated), the index
    was modifying live index data instead of using a copy.  When
    that occurred, there was a race conditional when the
    application is trying to determine the partitions for a
    particular index value.  The logic was updated to make sure
    that a copy was used when updating the global index when the
    indexed map is not using a bytes based CopyMode.
    

Problem conclusion

  • An interim fix is available for this APAR upon request for
    eXtreme Scale versions 8.6.0.8 and 8.6.1.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI86927

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-06

  • Closed date

    2017-09-14

  • Last modified date

    2017-09-14

  • 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

  • R861 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:
14 September 2017