-
1. Re: JBoss4 & 5 messaging
agohar Mar 15, 2010 9:43 AM (in response to agohar)It looks like the problem is only when my Message driven beans are deployed. I get exceptions as following
javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.client.JBossConnectionFactory (no security manager: RMI class loader disabled)]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:151)
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:597)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:922)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1492)
at java.lang.Thread.run(Thread.java:534)Seems, message driven bean is trying to lookup queue in jboss 5 container and it fails because jboss 4 doesn't have jms client in its classpath. Any idea why jboss 4's mdbs are trying to lookup queues from jboss5?
Thanks
-
2. Re: JBoss4 & 5 messaging
agohar Mar 15, 2010 2:05 PM (in response to agohar)Looks like this error is occuring only for DLQ Handlers. I've different queues with have DLQ configured for them and there are listeners to those DLQs. When JBoss starts up and it tries to deploy first Message driven bean listening on a DLQ, it fails and it sebsequently complains about other DLQs. And it says error Initializing DLQHandler.
2010-03-15 17:27:48,402 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed DLQHandler
javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.client.JBossConnectionFactory (no security manager: RMI class loader disabled)]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:151)
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:597)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:922)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvoker.java:1492)
at java.lang.Thread.run(Thread.java:534)Any idea why it is trying to use jboss messaging client and not mq client? Can anybody please direct me how jboss internally lookup jms queues? is it using jndi.properties file? but that doesn't list the jnp url? does it use localhost:1099 to lookup?
Thanks