7 Replies Latest reply on Jan 22, 2018 11:54 AM by hao1st

: javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

mgacamedica Jan 6, 2018 10:52 AM

We are migrating JBOSS from 4.0.3SP1 to Wildfly 10.1.0. Our applications are bundled in separate sars which contain standard as well as Dynamic beans.

We are getting "javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository" exception caused by "java.lang.ClassNotFoundException: com.xxx.ccr.common.adapter.PEAdapterLCM". Stack Trace is added in the end. PEAdapter class is a Dynamic MBean and is present in one of the jars in the common modules under /opt/coreservices/wildfly-10.1.0.Final/modules.

We are using standalone-full.xml to start our Wildfly instance (ccr2)

[root@puiqr710dev08 CCR]# ps -eaf|grep ccr2

xxxiq 28948 7529 21 15:17 ? 00:07:10 /opt/Xxx/CCR/jre/bin/java -verbose:class -Ddss.port=31002 -DCONTAINER_UUID=14132c5860baba870160bac5d84e084a -Dlcm.host= xxx.xxxx.xxx.xxx -server -XX:NewRatio=1 -XX:+UseG1GC -XX:+UseLargePages -XX:MaxGCPauseMillis=1000 -XX:GCTimeRatio=10 -XX:+DisableExplicitGC -Dsun.nio.ch.disableSystemWideOverlappingFileLockCheck=true -Ddss.thread_pool_size=24 -Xss250k -Xms256m -Xmx4096m -DUSE_DELAY1=60000 -DUSE_DELAY2=60000 -Dlog4j.configuration=file:/opt/Xxx/CCR/appserver/jboss-boot.log4j.properties -DLOG_FILE_PREFIX=DataProcessingJBoss_puiqdevdads07 -Ddss.message_lifetime=180 -Djava.awt.headless=true -Dorg.jboss.logging.Log4jService.catchSystemErr=false -classpath /opt/Xxx/CCR/jre/lib/tools.jar -jar /opt/coreservices/wildfly-10.1.0.Final/jboss-modules.jar -mp /opt/coreservices/wildfly-10.1.0.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/opt/coreservices/wildfly-10.1.0.Final -Djboss.server.base.dir=/opt/coreservices/wildfly-10.1.0.Final/ccr2 -Djboss.bind.address=xxx.xxxx.xxx.xxx -Djboss.bind.address.management= xxx.xxxx.xxx.xxx -c standalone-full.xml

· We have four sars that are deployed in this instance. All sars are deployed successfully.

· We have packaged our sars as follows:

--lib (contains all jars)

--META-INF

|--jboss-deployment-structure.xml

|--jboss-service.xml

· Each sar contains some standard MBeans and few Dynamic MBeans.

· We have defined standard MBeans in jboss-services.xml. They are created properly and can be seen in JConsole.

· We can NOT include definition of Dynamic MBeans in jboss-service.xml as their name is constructed at runtime.

· PEAdapterLCM for which we are getting ClassNotFoundException is a dynamic bean and we are getting this error for all Dynamic MBeans.

· We have created modules for all common jars that were part of “server/lib” folder in JBOSS 4.0.3SP1.

We tried following to fix this error but no luck:

1) packaged contents of all sars in one single sar and deployed it.

2) Added a global module entry in standalone-full.xml which contents dynamic MBeans.

3) Added definition of dynamic MBean in jboss-service.xml (just to see if this makes any difference). With this change, we were able to see the MBean in JConsole.

So what should be done to fix this error. Are there any changes in how to implement and deploy Dymanic MBeans in Wildfly?

Is there any way in Wildfly we can explicitly mention the MBean server class while starting the Wildfly as it was done in JBOSS 4.0.3SP1 using "-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -Djboss.platform.mbeanserver -Dcom.sun.management.jmxremote"

Here is complete stack trace:

^[[0m^[[31m15:01:30,324 ERROR [com.xxx.coreservice.lifecycle.jmx.PEController] (MSC service thread 1-6) Exception in PEController:PEControllerJmxJBossService start for peID 14132c58609742440160974fe69307e0: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

at com.sun.jmx.mbeanserver.MBeanInstantiator.findClassWithDefaultLoaderRepository(MBeanInstantiator.java:104)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.createMBean(DefaultMBeanServerInterceptor.java:268)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.createMBean(DefaultMBeanServerInterceptor.java:206)

at com.sun.jmx.mbeanserver.JmxMBeanServer.createMBean(JmxMBeanServer.java:326)

at com.avaya.lifecycle.jmx.agent.PEControllerJmx._start(PEControllerJmx.java:55)

at com.xxx.coreservice.lifecycle.jmx.PEController.start(PEController.java:397)

at com.xxx.coreservice.lifecycle.jmx.PEController.startAll(PEController.java:314)

at com.xxx.coreservice.lifecycle.jmx.PEController.startup(PEController.java:238)

at com.xxx.coreservice.lifecycle.jmx.PEController.postRegister(PEController.java:700)

at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSupport.java:182)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegister(DefaultMBeanServerInterceptor.java:1024)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:974)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)

at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)

at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.java:1527)

at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:871)

at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:101)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.ClassNotFoundException: com.xxx.ccr.common.adapter.PEAdapterLCM

at com.sun.jmx.mbeanserver.ClassLoaderRepositorySupport.loadClass(ClassLoaderRepositorySupport.java:232)

Thanks for help in advance.

https://developer.jboss.org/discussion/create!input.jspa?containerType=14&containerID=2303&draftID=430843

1. Re: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

jaikiran Jan 9, 2018 12:35 AM (in response to mgacamedica)

What does the code look like which registers these dynamic MBeans and when is it being called? Is it during application deployment?
Actions
2. Re: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

mgacamedica Jan 9, 2018 12:57 AM (in response to jaikiran)

This is how the Dynamic MBeans are created by another standard MBean.

mbeanServer.createMBean(element.getMbeanClassName(), objectName);

mbeanServer is a instance variable of this standard MBean and is set with MBean server instance when preRegister(MBeanServer server, ObjectName name) is called.
Actions
3. Re: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

jaikiran Jan 9, 2018 1:21 AM (in response to mgacamedica)

mbeanServer.createMBean(element.getMbeanClassName(), objectName);
When are where, within your standard MBean, does this invocation happen? During the start of that standard MBean? Or during some invocation of an operation on that standard MBean?
Actions
4. Re: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

mgacamedica Jan 11, 2018 12:20 AM (in response to mgacamedica)

these dynamic MBeans are not registered explicitly. Above createMbean call is responsilble for creating and registerting them during deployment.

We have modfied our code to first create object of each dynamic mbean using reflection and then calling mbeanServer.registerMBean with this object and the objectName (which is generated at runtime). This solved the isssue and now we are not getting above exception "javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository". Also these dynamic mbeans are now visible in JConsole.
Actions
5. Re: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

hao1st Jan 19, 2018 2:27 AM (in response to mgacamedica)

Hi Manjusha,

First glad to know you find a solution for dyncamic mbeans.

1. Do you have to define standard MBeans in jboss-services.xml? And could you give you an example how you do it?

2. When you implement standard MBean, do you use new to instantiate the bean before it is registered in your code? Or you use @Singleton & @Startup in MBean class?

thanks in advance,

Hao
Actions
6. Re: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

mgacamedica Jan 22, 2018 1:22 AM (in response to hao1st)

Hi Hao,

1) We had to define the standard mbeans in jboss-services.xml in wildfly. Here is how we have defined. You can add more than one mbean in the jboss-services.xml be repeating <mbean> element.

<?xml version="1.0" encoding="UTF-8"?>

<server xmlns="urn:jboss:service:7.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="urn:jboss:service:7.0 http://www.jboss.org/schema/jbossas/jboss-service_7_0.xsd">

<mbean code="com.xxx.ccr.eventmgt.eventprocessor.PEEventProcessorFactory" name="XXX:type=Factory,name=PEEventProcessorFactory">

</mbean>

</server>

You can google for format of jboss-services.xml and should get lots of information.
2) We did not have to instantiate Standard MBeans. They were getting registered automatically . We had to instantiate Dynamic MBeans with new() and then register them with MBean server.
Actions
7. Re: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository

hao1st Jan 22, 2018 11:54 AM (in response to mgacamedica)

Hi Manjusha,

thanks for your input!

Cheers,
Hao
Actions

Go to original post