IBM Support

PI10217: The org.omg.CORBA.BAD_PARAM exception can occur in eXtreme Scale when you use external monitoring software.

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 using a Java monitoring software that allows you to see
    the time spent in methods and exceptions thrown,
    org.omg.CORBA.BAD_PARAM exceptions are seen for ORB requests
    that are not for eXtreme Scale.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere eXtreme Scale users who           *
    *                  integrate WebSphere Application Server and  *
    *                  make ORB requests that are not for          *
    *                  eXtreme Scale; for example, EJB requests.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When an ORB request or reply does not   *
    *                      contain a requested service context,    *
    *                      an org.omg.CORBA.PARAM exception is     *
    *                      thrown.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere eXtreme Scale was designed for flexibility, which
    includes using non-IBM ORBs. As such, the ORB code in eXtreme
    Scale uses the standard CORBA APIs that throw an
    org.omg.CORBA.BAD_PARAM exception when a request or reply does
    not contain the requested eXtreme Scale service context for
    requests that are not for eXtreme Scale.  These exceptions
    are benign because eXtreme Scale catches the exception and
    does not treat the request as an eXtreme Scale request. Java
    monitoring software can show that these exceptions cause up to
    a five to ten percent performance impact on these ORB requests
    that are not for eXtreme Scale.
    The eXtreme Scale software was updated to conditionally use
    the  optimized IBM ORB function that does not throw an
    exception when we detect that the ORB is an IBM ORB. The
    optimized function of the IBM ORB is used by other WebSphere
    Application Server components that have service context that
    they attach to ORB requests.
    

Problem conclusion

  • An interim fix is available for this APAR for the V7.1.1.1,
    V8.5.0.3, and V8.6.0.4 releases.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI10217

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

  • 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

  • R711 PSY

       UP

  • 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