IBM Support

PI83027: Default threadpoolstats data cannot be retrieved due to InstanceNotFoundException

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Default ThreadPoolStats data can't be retrieved due to
    InstanceNotFoundException when wasJmsClient-2.0 is enabled.
    When we send the following request to retrieve the stats
    data,
    https://localhost:port/IBMJMXConnectorREST/mbeans/WebSphere%
    3Aty
    pe%3DThreadPoolStats%2Cname%3DDefault%20Executor/attributes/
    Pool
    Size
    the following exception stack will be returned to the
    client.
    "javax.management.InstanceNotFoundException:
    WebSphere:type=ThreadPoolStats,name=Default Executor
    at
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBe
    an(D
    efaultMBeanServerInterceptor.java:1107)
    at
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAtt
    ribu
    te(DefaultMBeanServerInterceptor.java:655)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Messaging Providers        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Cannot view thread pool MBean for       *
    *                      Liberty JMS features in JConsole        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The issue is observed when JMS features (wasJmsClient-2.0 and
    wasJmsServer-1.0) are enabled along with the monitor-1.0 feature
    in the Liberty server.xml. The default thread pool is overridden
    by the pool name provided by JMS features which is causing
    ThreadPoolMXBean not to be monitored as the monitor-1.0 feature
    only tracks the Default Executor thread pool.
    

Problem conclusion

  • This APAR updates the threadpool used by the JMS features from
    "LargeThreadPool" to "Default Executor"
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.3  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI83027

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-13

  • Closed date

    2017-08-10

  • Last modified date

    2017-08-10

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • RCD0 PSY

       UP



Document information

More support for: WebSphere Application Server

Software version: CD0

Reference #: PI83027

Modified date: 10 August 2017


Translate this page: