PM78936: Running eXtremeIO (XIO) with a COPY_TO_BYTES map fails with an assertion error when you use maps with the -ea JVM argument.

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 incorrect assertion statement was left in the logic that
    handles the serialization for HashMap, HashSet and Hashtable
    objects.  If you have an application that stores these types
    within the data grid and you run with the Java assert JVM
    runtime argument, (-ea), then you encounter this
    AssertionError failure.  The assertion does not indicate that
    there is a problem with the code (aside from the incorrect
    assert statement). Removing the -ea option from your JVM
    runtime arguments is the way to workaround this problem.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users running with  *
    *                  XIO and copyMode=COPY_TO_BYTES maps with    *
    *                  the Java -ea argument enabled.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: An incorrect assertion was left in the  *
    *                      code that causes a failure when the     *
    *                      application runs with the -ea JVM       *
    *                      argument.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If you have an application that stores these types within the
    data grid and you run with the Java assert JVM runtime argument
    (-ea ), then you encounter this AssertionError failure.
    The assertion does not indicate that there is a problem with
    the code.
    

Problem conclusion

  • The incorrect assertion was removed from the code.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM78936

  • 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

    2012-12-11

  • Closed date

    2013-06-17

  • Last modified date

    2013-06-17

  • 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



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale

Software version:

860

Reference #:

PM78936

Modified date:

2013-06-17

Translate my page

Machine Translation

Content navigation