Error while starting Jboss 4.0.10sp1 cluster

[sidnim]

I am trying to start the first server instance in a cluster using JBoss 4.0.1sp1 's 'all' configuration by invoking:
run -c all -b <my ip>

I have

configured cluster-service.xml with the relevant cluster name
set recursive to true
the the hajndi-jms-ds.xml configured to point to <my ip>
all the other standard *.xml files in the deploy-hasingleton folder
ensured that all my ear's and jar's are fine and dont give any errors, as they deploy and run fine in 3.2.3.

This is the config snippet from hajndi-jms-ds.xml :

<!-- The JMS provider loader -->

DefaultJMSProvider

org.jboss.jms.jndi.JNDIProviderAdapter

<!-- The combined connection factory -->
java:/XAConnectionFactory
<!-- The queue connection factory -->
XAConnectionFactory
<!-- The topic factory -->
XAConnectionFactory
<!-- Access JMS via HAJNDI -->
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=<my ip>:1100


And this is error snippet that I receive while starting JBoss:
11:08:55,537 ERROR [DLQHandler] Initialization failed DLQHandler
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:238)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:165)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:557)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:813)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
Initialization failed DLQHandler

11:27:03,374 ERROR [DLQHandler] Initialization failed DLQHandler
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:166)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:238)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:165)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:557)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:813)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:
1323)

Why is the XAConnectionFactory is not bound? Or is there some configuration that is missing?

Please provide some solution to this problem.

Thanks in advance!

[sidnim]

To add to the above post:

'hsqldb-ds.xml' contains DefaultDS as its jndi-name and all the other config XML files contain their default values


any ideas ppl?

[sidnim]

JMS is a singleton service, and has to be deployed on only node in the cluster. If the deploy-hasingleton-service.xml doesn't have the right partition name then JMS will not be deployed properly, i.e. XAConnectionFactory will not be bound, etc.

Hence I have been able to solve this problem by supplying the right cluster name in all the places in the deploy-hasingleton-service.xml file in the '/all/deploy' folder.