IBM Support

PI61176: Using the IBM JMX REST client from Liberty requires setting too many properties

Fixes are available

16.0.0.2: WebSphere Application Server Liberty 16.0.0.2
16.0.0.3: WebSphere Application Server Liberty 16.0.0.3
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In order to  use the IBM JMX REST connector client from
    Liberty, you need to explicitly set the
    jmx.remote.protocol.provider.pkgs property to include our
    package either as a system or environment property.  For an
    OSGI application you also need to arrange that the bundle
    using the connector imports this package.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the IBM JMX REST client from IBM   *
    *                  WebSphere Application Server Liberty        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Using the IBM JMX REST client from      *
    *                      Liberty requires setting too many       *
    *                      properties                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In order to  use the IBM JMX REST connector client from Liberty,
    you need to explicitly set the jmx.remote.protocol.provider.pkgs
    property to include our package either as a system or
    environment property.  For an OSGI application you also need to
    arrange that the bundle using the connector imports this
    package.
    

Problem conclusion

  • JavaEE applications now have access by default to the IBM JMX
    Rest connector whenever it is installed.  Similarly OSGI web
    applications have access by default. This is arranged by
    adjusting the jmx.remote.protocol.provider.pkgs system property
    to include "com.ibm.ws.jmx.connector.client" and including the
    com.ibm.ws.jmx.connector.client.rest package in the thread
    context class loader.  Other OSGI applications need to arrange
    that the bundle using the connector explicitly import the
    com.ibm.ws.jmx.connector.client.rest package.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 16.0.0.2.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Set the jmx.remote.protocol.provider.pkgs to include
    "com.ibm.ws.jmx.connector.client" and, for an OSGI application,
    import the com.ibm.ws.jmx.connector.client.rest package.
    

Comments

APAR Information

  • APAR number

    PI61176

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-20

  • Closed date

    2016-04-26

  • Last modified date

    2016-06-13

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 October 2021