IBM Support

PI41076: JMX CLIENT FAILS TO CONNECT WITH CLASSNOTFOUNDEXCEPTION: COM.IBM.WS.MANAGEMENT.PLATFORMMBEANSERVERBUILDER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using a JMX client to monitor WebSphere internals,
    an intermittent ClassNotFoundException might occur when
    connecting to the JVM.
    JMX client fails when loading the
    management-agent library
    "getConnectorAddressUsingLoadAgentLibrary".
    The errors seen in the server logs (systemErr.log files)
    
    Exception thrown by the agent :
    javax.management.JMRuntimeException:
    Failed to load MBeanServerBuilder class
    com.ibm.ws.management.PlatformMBeanServerBuilder:
    java.lang.ClassNotFoundException:
    com.ibm.ws.management.PlatformMBeanServerBuilder
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke
    (NativeMethodAccessor Impl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke
    (DelegatingMethod AccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at sun.instrument.InstrumentationImpl.loadClassAndStartAgent
    (Instru mentationImpl.java:337)
    at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain
    (Ins trumentationImpl.java:360)
    at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibraryImpl
    (Nati ve Method)
    at com.ibm.tools.attach.javaSE.Attachment.loadAgentLibrary
    (Attachme nt.java:252)
    at com.ibm.tools.attach.javaSE.Attachment.parseLoadAgent
    (Attachment .java:230)
    at com.ibm.tools.attach.javaSE.Attachment.doCommand
    (Attachment.java :140)
    at com.ibm.tools.attach.javaSE.Attachment.run
    (Attachment.java:101)
    Caused by: java.lang.RuntimeException:
    javax.management.JMRuntimeException: Failed to load
    MBeanServerBuilder
    class com.ibm.ws.management.PlatformMBeanServerBuilder:
    java.lang.ClassNotFoundException:
    com.ibm.ws.management.PlatformMBeanServerBuilder
    at sun.management.Agent.error(Agent.java:337)
    at sun.management.Agent.startAgent(Agent.java:173)
    at sun.management.Agent.agentmain(Agent.java:108)
    ... 11 more
    Caused by: javax.management.JMRuntimeException: Failed to load
    MBeanServerBuilder class
    com.ibm.ws.management.PlatformMBeanServerBuilder:
    java.lang.ClassNotFoundException:
    com.ibm.ws.management.PlatformMBeanServerBuilder
    at javax.management.MBeanServerFactory.checkMBeanServerBuilder
    (MBea nServerFactory.java:492)
    at javax.management.MBeanServerFactory.getNewMBeanServerBuilder
    (MBe anServerFactory.java:523)
    at javax.management.MBeanServerFactory.newMBeanServer
    (MBeanServerFa ctory.java:310)
    ... 17 more
    Caused by: java.lang.ClassNotFoundException:
    com.ibm.ws.management.PlatformMBeanServerBuilder
    at java.net.URLClassLoader.findClass(URLClassLoader.java:434)
    at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:703)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:682)
    at sun.misc.Launcher$AppClassLoader.loadClass
    (Launcher.java:358)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:665)
    at javax.management.MBeanServerFactory.loadBuilderClass
    (MBeanServer Factory.java:435)
    at javax.management.MBeanServerFactory.checkMBeanServerBuilder
    (MBea nServerFactory.java:477)
    ... 19 more
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using monitoring agents that use     *
    *                  JVM "Attach" APIs.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: An intermittent                         *
    *                      ClassNotFoundException might occur      *
    *                      during attach.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An intermittent ClassNotFoundException might occur during
    attach.
    

Problem conclusion

  • The "missing" class has restricted visibility under OSGI so
    the attach agent cannot load it directly.  Code is adjusted to
    load the class during server startup so it is available for
    attach operations.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.11 and 8.5.5.7.  Please refer to the
    Recommended Updatespage for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI41076

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-13

  • Closed date

    2015-05-22

  • Last modified date

    2015-05-22

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022