JMS Messaging Bridge Issue with Custom configured Messaging bridge Adapter. (Doc ID 2233442.1)

Last updated on MARCH 29, 2017

Applies to:

Oracle WebLogic Server - Version 12.2.1.1.0 and later
Information in this document applies to any platform.

Symptoms

 

From Weblogic 12.2.1 onwards, a messaging bridge can use a custom configured adapter. When a messaging bridge needs to use a custom configured adapter, explicit deployment of an adapter is required. In this case, the adapter must be configured with a non-default or custom adapter JNDI name, and the messaging bridge needs to be configured to reference the custom adapter JNDI name.

Refer the Oracle doc link : https://docs.oracle.com/middleware/1221/wls/BRDGE/basics.htm#BRDGE120

Customer is facing issue with custom configured messaging bridge adapter. A messaging bridge configured to use custom configured adapter with a non-default or custom adapter JNDI name eg. customJNDI. For this, changed the JNDI name to the customJNDI in config.xml ,since there is no option in weblogic console to provide the custom jndi name except the drop down shows only default JNDI name (eis.jms.WLSConnectionFactoryJNDINoTX or eis.jms.WLSConnectionFactoryJNDIXA).

Config snippet:

 

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