run.sh failed because ServiceBindingManager not found

vmdd_tech May 30, 2003 2:43 PM

I am trying to start jboss-3.2.1_tomcat-4.1.24 using
different http ports. I modified jboss-service.xml to use ServiceBindingManager. I modified a sample jboss-bindings.xml to use port 9080.

The problem is when I start jboss (run.sh), it aborts with the following error:

...
13:00:43,882 DEBUG [ServiceCreator] About to create bean: jboss.system:service=S
erviceBindingManager with code: org.jboss.services.binding.ServiceBindingManager
13:00:43,889 DEBUG [ServiceCreator] Class not found for mbean: jboss.system:serv
ice=ServiceBindingManager
13:00:43,896 WARN [ServiceConfigurator] Failed to complete install
java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.services.
binding.ServiceBindingManager
at org.jboss.mx.loading.LoadMgr.beginLoadTask(LoadMgr.java:161)
at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader
3.java:175)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:
822)
@
...

1. Re: run.sh failed because ServiceBindingManager not found

mfrost Jul 8, 2003 11:07 AM (in response to vmdd_tech)

yep - i'm getting the exact same problem in jboss-3.2.1_tomcat-4.1.24

I resolved in by downloading a previous version (3.0.7) and extracting the file bindingservice-plugin.jar and placing it in the /server/*/lib folder(s)

hope this helps

(Alternatively its in the source so I guess you could build the classes yourself -but I'm lazy!)

In any case I'm struggling to get it to work. I think the sample-bindings.xml that I found in the 3.0.7 is out of date - but I'll keep trying

cheers

mark
Actions