In SOA 12c/CS Environment UMS Is Not Working And Emails Are Not Going Out. Logs Shows The Below Exception "Unable to perform JNDI lookup of JMS Queue: OraSDPM/Queues/OraSDPMEngineSndQ1"
(Doc ID 2262065.1)
Last updated on APRIL 29, 2024
Applies to:
SOA Suite Cloud Service - Version N/A and laterOracle SOA Suite - Version 12.1.3.0.0 and later
Information in this document applies to any platform.
Symptoms
When application tries to send a notification, it fails with the below exception.
ERROR
-----------------------
[2017-04-28T01:12:34.974+00:00] [SPSOAOSB_server_1] [ERROR] [SDP-25713] [oracle.sdp.internal.messaging.jms.JMSHandle] [tid: [ACTIVE].ExecuteThread: '43' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <ECID>,0:3] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] Unable to perform JNDI lookup of JMS Queue: OraSDPM/Queues/OraSDPMEngineSndQ1.
[2017-04-28T01:12:35.022+00:00] [SPSOAOSB_server_1] [ERROR] [SDP-25505] [oracle.sdp.internal.messaging.MessagingClientImpl] [tid: [ACTIVE].ExecuteThread: '43' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <ECID>,0:3] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] Unable to enqueue outbound message.[[
java.lang.UnsupportedOperationException: [JMSClientExceptions:055080]Must provide destination to send to
at weblogic.jms.client.JMSProducer.sendWithListenerUnified(JMSProducer.java:477)
at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:461)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:450)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:1005)
at oracle.sdpinternal.messaging.jms.JMSSender$1.enqueue(JMSSender.java:302)
at oracle.sdpinternal.messaging.jms.JMSSender$1.run(JMSSender.java:260)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:70)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:266)
at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:82)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163)
at weblogic.security.Security.runAs(Security.java:62)
[2017-04-28T01:12:35.022+00:00] [SPSOAOSB_server_1] [ERROR] [SDP-25505] [oracle.sdp.internal.messaging.MessagingClientImpl] [tid: [ACTIVE].ExecuteThread: '43' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <ECID>,0:3] [APP: soa-infra] [partition-name: DOMAIN] [tenant-name: GLOBAL] Unable to enqueue outbound message.[[
java.lang.UnsupportedOperationException: [JMSClientExceptions:055080]Must provide destination to send to
at weblogic.jms.client.JMSProducer.sendWithListenerUnified(JMSProducer.java:477)
at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:461)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:450)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:1005)
at oracle.sdpinternal.messaging.jms.JMSSender$1.enqueue(JMSSender.java:302)
at oracle.sdpinternal.messaging.jms.JMSSender$1.run(JMSSender.java:260)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:70)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:266)
at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:82)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163)
at weblogic.security.Security.runAs(Security.java:62)
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Send an email notification from BPEL (For eg). to get the reported exception.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |