My Oracle Support Banner

Error "Failed to post request on JMS queue" Is Observed When OBDX Application Is Deployed in Cluster (Doc ID 2786661.1)

Last updated on JUNE 28, 2021

Applies to:

Oracle Banking Digital Experience - Version 20.1.0.0.0 to 20.1.0.0.0 [Release 20]
Information in this document applies to any platform.

Symptoms

When attempting to access the OBDX application in a cluster setup where Managed server 1 is Shutdown and only Managed server 2 is Running,
the following error occurs.

ERROR
-----------------------
<Jun 11, 2021 11:11:17,308 AM AST> <Error> <com.ofss.digx.app.audit.handler.AsyncJMSAPIAuditHandler> <BEA-000000> <
Failed to send request>
<Jun 11, 2021 11:11:17,309 AM AST> <Error> <com.ofss.digx.app.audit.handler.AsyncJMSAPIAuditHandler> <BEA-000000> <
Failed to post request on JMS queue.>
<Jun 11, 2021 11:11:20,847 AM AST> <Warning> <com.ofss.digx.infra.util.JMSUtility> <BEA-000000> <Exception in initializeQueue
javax.naming.NameNotFoundException: Unable to resolve 'API_AUDIT_QUEUE'. Resolved ''; remaining name 'API_AUDIT_QUEUE'
               at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
               at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:354)
               at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:227)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to the Weblogic console
2. Navigate to Servers
3. Shutdown the Managed server1 from the cluster, access the OBDX application

Changes

 

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
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.