Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by chiagng, 1 year ago
Failed to look up ConnectorDescriptor from JNDI
via Oracle Community by 843793, 1 year ago
Failed to look up ConnectorDescriptor from JNDI
via hivmr.com by Unknown author, 1 year ago
via nabble.com by Unknown author, 2 years ago
via Oracle Community by 843830, 1 year ago
Failed to look up ConnectorDescriptor from JNDI
via Oracle Community by emiddio, 1 year ago
Failed to look up ConnectorDescriptor from JNDI
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to look up ConnectorDescriptor from JNDI	at com.sun.enterprise.naming.factory.ConnectorObjectFactory.getObjectInstance(ConnectorObjectFactory.java:98)	at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)	at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:344)	at javax.naming.InitialContext.lookup(InitialContext.java:392)	at jmsclasses.JMSResourceAlocator.initConnFactory(JMSResourceAlocator.java:45)	at jmsclasses.JMSResourceAlocator.createQueueConnection(JMSResourceAlocator.java:55)	at jmsclasses.JMSMessageSender.sendMessage(JMSMessageSender.java:23)