My Oracle Support Banner

JMS Bridges State Inactive - WARN: Failed To Connect To The Source. (Doc ID 3018789.1)

Last updated on APRIL 29, 2024

Applies to:

Oracle Service Bus - Version and later
Information in this document applies to any platform.


 Unable to connect the target JMS destination and observed the below error in logs.

####<Mar 23, 2024 11:05:23,828 AM CST> <Warning> <EJB> <XXXXXXXXX> <osb_server1> <[STANDBY] ExecuteThread: '41' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <4993e8cb-3712-4da2-96be-01a498acfacd-000000eb> <1711213523828> <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-010061> <The Message-Driven EJB RequestEJBN53eae1edX4d5ea4c9X0X18e39d6944dXN7ff5 is unable to connect to the JMS destination jms.XXXXXXXXfsError. The Error was:
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3:// Destination XX.XX.xx.XX, 7192 unreachable.; nested exception is:


 Establishing JMS bridge connectivity from OSB environment  to weblogic environment.


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

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