I've got a stand-alone WAR using JSF, where I have a backing bean use some
helper objects that will send a JMS message. When this WAR is running from
inside of Glassfish, it fails to do the lookup of the ConnectionFactory.
The application pulls the Queue JNDI and the Provider URL from a database,
and uses a env Hashtable to do the JNDI InitialContext (which succeeds.)
Using this Context, the ConnectionFactory lookup fails.
The remote server in this instance is WebLogic 9.2 (the JNDI is publically
available with no user authentication, verified with a JMS developer tool we
use internally.)
Here's the stacktrace...
2007-10-15 19:48:04,514 ERROR
[net.acadiasoft.shared.jms.util.JMSSenderHelper:130] NamingException:
messageFactory not found
javax.naming.NameNotFoundException: messageFactory not found
at
com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
at
com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
at
com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:74)
at
com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:111)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:339)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
net.acadiasoft.shared.jms.util.JMSSenderHelper.getConnectionFactory(JMSSenderHelper.java:128)
at
net.acadiasoft.shared.jms.util.JMSSenderHelper.init(JMSSenderHelper.java:58)
at
net.acadiasoft.shared.jms.util.JMSSenderHelper.<init>(JMSSenderHelper.java:36)
at
net.acadiasoft.web.shared.jms.util.AdminJmsHelper.<init>(AdminJmsHelper.java:19)
at
net.acadiasoft.web.server.pages.SchedulerBackingBean.deleteJobs(SchedulerBackingBean.java:75)
--
View this message in context: http://www.nabble.com/JNDI-Lookup-of-ConnectionFactory-fails-from-inside-Glassfish-application-tf4631296.html#a13224765
Sent from the java.net - glassfish users mailing list archive at Nabble.com.