We are trying to do a JNDI lookup to an ActiveMQ queue in tomcat. We have specified the resource in META-INF/context.xml
<Context> <Resource name="jms/esbConnectionFactory" type="org.apache.activemq.ActiveMQConnectionFactory" description="Esb JMS Connection Factory" factory="org.apache.activemq.jndi.JNDIReferenceFactory" brokerURL="tcp://devserver.imd.local:61616" brokerName="LocalActiveMQBroker"/> <Resource name="jms/ ws_proxy" type="org.apache.activemq.command.ActiveMQQueue" factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="ws_proxy" auth="Container"/> </Context> This is working in a local windows dev tomcat 5.5.26, but when moving to our staging environment (Suse tomcat 5.5.26), this file is not being picked up (this is confirmed by making it invalid xml, with no exception thrown). Placing resources in GlobalNamingResources in sevrer.xml Returning a binding list for java:comp/env returns nothing. Server.xml does not have useNaming=false. Is there anything else that could disable JNDI or the reading of this file? This transmission is confidential and intended solely for the person or organization to whom it is addressed. It may contain privileged and confidential information. If you are not the intended recipient, you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error, please notify the sender. This e-mail has been scanned for all viruses by Star Internet for IMD Plc. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk
