JMSException while initializing DLQHandler

[mschwarz]

Hi there,

I'm using JBoss 3.2.7 and just tried to start the server which includes a configuration for an ActiveMQ Service.
Unfortunately a JMSException is thrown during startup.

Initialization failed DLQHandler
javax.jms.JMSException: Error creating the dlq connection:
Failed to find method for hash:-790108502850547550
available={
-884175917852741154=public abstract java.lang.Object org.jnp.interfaces.Naming.lookup(javax.naming.Name)
throws javax.naming.NamingException,java.rmi.RemoteException,
-5642140585403320990=public abstract java.util.Collection org.jnp.interfaces.Naming.listBindings(javax.naming.Name)
throws javax.naming.NamingException,java.rmi.RemoteException,
7733619496521189953=public abstract java.io.Serializable org.jboss.ha.framework.interfaces.HAPartition$HAPartitionStateTransfer.getCurrentState(),
-4221607359560216057=public abstract java.util.Collection org.jnp.interfaces.Naming.list(javax.naming.Name)
throws javax.naming.NamingException,java.rmi.RemoteException,
-5717908715153450081=public abstract void org.jnp.interfaces.Naming.rebind(javax.naming.Name,java.lang.Object,java.lang.String)
throws javax.naming.NamingException,java.rmi.RemoteException,
6991977298034536864=public abstract void org.jboss.ha.framework.interfaces.HAPartition$HAPartitionStateTransfer.setCurrentState(java.io.Serializable),
-8107796390111393345=public abstract void org.jnp.interfaces.Naming.unbind(javax.naming.Name)
throws javax.naming.NamingException,java.rmi.RemoteException,
-7286638714004764603=public abstract javax.naming.Context org.jnp.interfaces.Naming.createSubcontext(javax.naming.Name)
throws javax.naming.NamingException,java.rmi.RemoteException,
-6149798079139202860=public abstract void org.jnp.interfaces.Naming.bind(javax.naming.Name,java.lang.Object,java.lang.String)
throws javax.naming.NamingException,java.rmi.RemoteException
}
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:171)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:563)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:780)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:899)
at $Proxy215.start(Unknown Source)

I deleted all of the JMS_MESSAGES which were still in my database and tried again, but I get the same error coming up.

Can anybody give me a hint what causes this problem ?

[genman]

Looks like there's some sort of issues with JNDI. How is your server configured (differences from the stock release)? I would guess there's some sort of version conflict.

[mschwarz]

Yes, I found some other discussion which led me to the conclusion, that it's got something to do with versioning, too. Still I have no idea, where the conflict could possibly occur.

Concerning the configuration: Could you be a little bit more specific ? What are you heading at ?

[mschwarz]

Got it:

Finally the problem could be solved by commenting a HAJNDI block in the server/default/deploy/jms/jms-ds.xml .

<!-- Uncomment to use HAJNDI to access JMS -->

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=localhost:1100


Since we are using ActiveMQ to archive overall messaging this block seems obsolete anyway.