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 3004, 1 year ago
via Google Groups by Smitha, 2 years ago
via Oracle Community by 3004, 1 year ago
javax.naming.NameNotFoundException: PSN10_QCF	at com.sun.jndi.fscontext.RefFSContext.getObjectFromBindings(RefFSContext.java:400)	at com.sun.jndi.fscontext.RefFSContext.lookupObject(RefFSContext.java:327)	at com.sun.jndi.fscontext.RefFSContext.lookup(RefFSContext.java:146)	at com.sun.jndi.fscontext.FSContext.lookup(FSContext.java:127)	at javax.naming.InitialContext.lookup(InitialContext.java:345)	at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:244)	at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:229)	at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)	at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:1002)	at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1769)	at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:191)	at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)	at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:97)	at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:725)	at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:930)	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)