2 Replies Latest reply on Oct 21, 2009 2:32 PM by mfishm1

    scoped classloader issue

      Hi,

      I am having an issue trying to configure a scoped classloader and I was hoping someone could point me in the right direction. I have an esb that worked fine before I tried to setup classloader scoping. However, after I added something like the following in my deployment.xml:

      <loader-repository>
      com.example:archive=unique-archive-name
      <loader-repository-config>
      java2ParentDelegation=false
      </loader-repository-config>
      </loader-repository>

      I started getting the following deployment exception related to my jbm-queue-service.xml on startup:

      Class does not expose a management interface: java.lang.Object; - nested throwable: (javax.management.NotCompliantMBeanException: Class does not expose a management interface: java.lang.Object)
      at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
      at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:226)


      I am currently running in jboss 4.4 GA.

      If anyone has any suggestions, it would be greatly appreciated.


      Thanks.

        • 1. Re: scoped classloader issue
          mimra

          Hi

          My guess is that the lib folder of your ESB archive contains some jboss system jars. Which jars do you package in your ESB archive?

          Cheers

          Michael

          • 2. Re: scoped classloader issue

            Michael,

            That is exactly what the problem was. I had a bug in my ant file that was including in some of the jboss jars into my archive instead of just using them during the build.

            Thank you so much for your help.

            -- Mark