[jboss-user] [Messaging, JMS & JBossMQ] - Re: Setting up a non-server specific EAR

I was thinking that if we set the useJNDI property to "true", it would look within the application server's JNDI namespace and retrieve the object based on the JNDI name that we provide within the Destination value. <activation-config-property> | <activation-config-property-name>destination</activation-config-property-name> | <activation-config-property-value>JNDI NAME</activation-config-property-value> | </activation-config-property> | <activation-config-property> | <activation-config-property-name>destinationType</activation-config-property-name> | <activation-config-property-value>javax.jms.Queue</activation-config-property-value> | </activation-config-property> | <activation-config-property> | <activation-config-property-name>useJNDI</activation-config-property-name> | <activation-config-property-value>true</activation-config-property-value> | </activation-config-property> So I defined an Admin Object for the inbound queue, and I was thinking that by setting the useJNDI to be true, the application server would look up the admin object within the server's JNDI namespace as it would for the outbound queue, but instead I get the following error. javax.resource.spi.ResourceAdapterInternalException: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:' | at com.ibm.mq.connector.ResourceAdapterConnectionPool.allocateConnection(ResourceAdapterConnectionPool.java:297) | at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:333) | at org.jboss.resource.deployment.RARDeployment.endpointActivation(RARDeployment.java:271) | at org.jboss.resource.deployment.RARDeployment.internalInvoke(RARDeployment.java:226) | at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory.activate(JBossMessageEndpointFactory.java:484) | ... 113 more | Caused by: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:' | at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:614) | at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2480) | at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1830) | at com.ibm.mq.jms.MQConnection.<init>(MQConnection.java:811) | at com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConnectionFactory.java:4821) | at com.ibm.mq.connector.ResourceAdapterConnectionPool.initializeJMSConnection(ResourceAdapterConnectionPool.java:445) | at com.ibm.mq.connector.ResourceAdapterConnectionPool.createNewConnection(ResourceAdapterConnectionPool.java:359) | at com.ibm.mq.connector.ResourceAdapterConnectionPool.allocateConnection(ResourceAdapterConnectionPool.java:284) | ... 120 more View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098523#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...