Last updated on NOVEMBER 02, 2016
Applies to:
Oracle Java CAPS Enterprise Service Bus - Version R6 to R6.2 [Release 6.0]Information in this document applies to any platform.
Symptoms
After deployment, an error is shown in the logs: Could not create session javax.jms.TopicSession: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: [C4060]: Login failed" Messages are not being published or consumed.
An error is show in the logs like below:
ERROR
-----------------------
[#|2011-02-21T13:58:56.176+1100|SEVERE|sun-appserver2.1|com.stc.codegen.appconn.jms.JMSApplicationConnection|_ThreadID=30;_ThreadName=p: thread-pool-1; w: 15;_RequestID=cfddddfa-e9c6-433c-bf14-832f1ba7a59d;|javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.TopicSession: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: [C4060]: Login failed: user=admin, broker=localhost:7676(1234)
javax.jms.JMSException: JMSJCA-E034: Could not create session javax.jms.TopicSession: Error in allocating a connection. Cause: JMSJCA-E084: Failed to create session: [C4060]: Login failed: user=admin, broker=localhost:7676(1234)
at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:113)
at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:153)
at com.stc.jmsjca.core.JConnection.createTopicSession(JConnection.java:300)
at com.stc.jmsjca.core.WTopicConnection.createTopicSession(WTopicConnection.java:55)
at com.stc.codegen.appconn.jms.JMSAdapterFactory$TopicJMSAdapter.createSession(JMSAdapterFactory.java:610)
at com.stc.codegen.appconn.jms.JMSApplicationConnection.<init>(JMSApplicationConnection.java:184)
at com.stc.codegen.appconn.jms.JMSApplicationConnectionFactory.getConnection(JMSApplicationConnectionFactory.java:95)
at com.stc.codegen.JMSImpl.runtime.JMS.oldConnection(JMS.java:251)
at com.stc.codegen.JMSImpl.runtime.JMS.checkOverwrite(JMS.java:398)
at com.stc.codegen.JMSImpl.runtime.JMS.send(JMS.java:456)
at com.stc.codegen.JMSImpl.runtime.JMS.sendText(JMS.java:501
Changes
This problem is experienced with:
- A new project or environment configuration
- A change in the Java Message Queue configuration.
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms