1 Reply Latest reply on Aug 3, 2004 10:53 PM by tom.elrod

    Classloading issue when setting remoting handlers

      I get the follow deployment error when trying specify a new subsystem in the remoting-service.xml file. The mbean configuration is below.

      This is running on: JBoss 4 DR4, JDK 1.4.1, Windows 2000.

      MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
      ObjectName: jboss.remoting:transport=socket5150,type=Connector
       state: FAILED
       I Depend On:
       Depends On Me: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.aop.remoting.AOPRemotingInvocationHandler
      
      <mbean code="org.jboss.remoting.transport.Connector"
       xmbean-dd="org/jboss/remoting/transport/Connector.xml"
       name="jboss.remoting:type=Connector,transport=socket5150">
       <attribute name="InvokerLocator">socket://localhost:5150</attribute>
       <attribute name="Configuration">
       <handlers>
       <handler subsystem="AOP">org.jboss.aop.remoting.AOPRemotingInvocationHandler</handler>
       </handlers>
       </attribute>
      </mbean>
      


        • 1. Re: Classloading issue when setting remoting handlers

          In the current code base (may have changed between DR4 and now, but don't think so), the package is org.jboss.aspects.remoting. Therefore the fully qualified class name should be:

          org.jboss.aspects.remoting.AOPRemotingInvocationHandler

          Can be found in the jboss-sapects.jar in the server/default/lib dir. Let me know if you have any problems after making this change.

          -Tom