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 807574, 1 year ago
Could not create session javax.jms.QueueSession: Error in allocating a connection. Cause: Failed to create session: javax.jms.JMSException: Could not find JNDI object by name [corbaname:iiop:1.2@ucadtestapp:22001#weblogic.jms.XAConnectionFactory]: java.lang.NullPointerException
via JIRA by Jakub Grabowski, 2 years ago
JMSJCA-E034: Could not create session javax.jms.QueueSession: JMSJCA-E073: Could not allocate connection: JMSJCA-E084: Failed to create session: [C4003]: Error occurred on connection creation [localhost:7676]. - cause: java.net.ConnectException: Connection refused
javax.jms.JMSException: Could not create session javax.jms.QueueSession: Error in allocating a connection. Cause: Failed to create session: javax.jms.JMSException: Could not find JNDI object by name [corbaname:iiop:1.2@ucadtestapp:22001#weblogic.jms.XAConnectionFactory]: java.lang.NullPointerException at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:92) at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:139) at com.stc.jmsjca.core.JConnection.createQueueSession(JConnection.java:270) at com.stc.jmsjca.core.WQueueConnection.createQueueSession(WQueueConnection.java:58) at com.stc.codegen.appconn.jms.JMSAdapterFactory$QueueJMSAdapter.createSession(JMSAdapterFactory.java:316)