PM79915: The java.lang.Illegalaccesserror error occurs when you use a secured data grid and enable tracing for security.

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

  • The problem is a bug in the Java 1.5 compiler from IBM, which
    does not generate the right byte codes for StringBuilder.append(
    
    The problem only occurs when a data grid is secured and
    ObjectGridSecurity tracing is enabled.  However, if the
    security trace is on, all access to the secured data grid
    fails on Solaris only. This error does not occur when you run
    with a JVM that IBM provides.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Administrators of WebSphere eXtreme Scale   *
    *                  8.5 on Solaris who attempt to get security  *
    *                  trace information.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: When ObjectGridSecurity tracing is      *
    *                      enabled for eXtreme Scale 8.5 on        *
    *                      Solaris, all access to the secured      *
    *                      data grid fails.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a data grid is secured and ObjectGridSecurity tracing is
    enabled, on Solaris only, all access to the secured data grid
    fails.  The specific failure is an IllegalAccessError in
    the logs for container and catalog servers, where the trace has
    been enabled.  This error occurs whenever the client accesses
    the server.
    

Problem conclusion

  • This error has been corrected with a code change. WebSphere
    eXtreme Scale deployers who experience this error should
    install the latest fix pack for WebSphere eXtreme Scale 8.5.
    For information about downloading the fix pack, see the
    following web page:
    http://www-01.ibm.com/support/docview.wss?uid=swg27018991
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM79915

  • 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-03

  • Closed date

    2013-06-21

  • Last modified date

    2013-06-21

  • 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



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere eXtreme Scale

Software version:

860

Reference #:

PM79915

Modified date:

2013-06-21

Translate my page

Machine Translation

Content navigation