My Oracle Support Banner

Intermittent java.rmi.ConnectException: “No Available Router To Destination” Between MDB JMS Clients and JMS Server (Doc ID 2235271.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle WebLogic Server - Version 12.2.1.0.0 to 12.2.1.0.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

On : 12.2.1.0.0 version, WLS JMS

JMS java.rmi.ConnectException: “No available router to destination”

-- This is a WebLogic domain hosting only JMS Queues. The JMS clients producing/consuming messages to/from queue are running on another domains.

-- Every now and then there is a communication problem between MDB JMS clients and the JMS server, where the client thinks it is connected, but the server cannot establish the connection.

Exception is observed from logs:

####<2016.08.16 6:00:00.19 CEST> <Warning> <JMS> <p1-esbmsg-alsu003> <node1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <bd517ffb-a019-47d1-990d-a1b7c0469e5b-0005b3c0> <1471320000019> <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-040499> <An error occurred while pushing messages to a JMS client: weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connectionManager with -1271089603314517781S:host.domain:[-1,-1,7002,7002,-1,-1,-1]:WCMS-PUBLISH-BE002:node1, /?partitionName=DOMAIN java.rmi.ConnectException: No known valid port for: dataT3:t3(t3):host.domain:7001:null:-1; [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: No known valid port for: dataT3:t3(t3):host.domain:7001:null:-1; [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: Could not establish a connectionManager with -1271089603314517781S:host.domain:[-1,-1,7002,7002,-1,-1,-1]:WCMS-PUBLISH-BE002:node1, /?partitionName=DOMAIN java.rmi.ConnectException: No known valid port for: dataT3:t3(t3):host.domain:7001:null:-1; [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: No known valid port for: dataT3:t3(t3):host.domain:7001:null:-1; [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: [RJVM:000576]No available router to destination.
weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connectionManager with -1271089603314517781S:host.domain:[-1,-1,7002,7002,-1,-1,-1]:WCMS-PUBLISH-BE002:node1, /?partitionName=DOMAIN java.rmi.ConnectException: No known valid port for: dataT3:t3(t3):host.domain:7001:null:-1; [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: [RJVM:000576]No available router to destination.; nested exception is:
java.rmi.ConnectException: No known valid port for: dataT3:t3(t3):host.domain:7001:null:-1; [RJVM:000576]No available router to destination.; nested exception is:

 

Debug enabled Client logs shows that MDB is connected :

####<2016.05.17 14:40:04.826 CEST> <Debug> <EjbMdbConnection> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804826> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[JMSConnectionPoller] Looked up ConnectionFactory in JNDI named: jms.kuda.XAConnectionFactory, found an object of class class weblogic.jms.client.JMSXAConnectionFactory>
####<2016.05.17 14:40:04.859 CEST> <Debug> <EjbMdbConnection> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804859> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[JMSConnectionPoller] MDB RequestEJBN53ef9fd1XN620a6bdbX16X154a4af673cXN7ffb will poll asynchronously using MDBTransaction>
####<2016.05.17 14:40:04.865 CEST> <Debug> <EjbMdbConnection> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804865> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[JMSConnectionPoller] Connection class: weblogic.jms.client.XAConnectionInternalImpl>
####<2016.05.17 14:40:04.865 CEST> <Debug> <EjbMdbConnection> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804865> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[JMSConnectionPoller] JMS Provider name: oracle and/or its affiliates. all rights reserved.>
####<2016.05.17 14:40:04.865 CEST> <Debug> <EjbMdbConnection> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804865> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[JMSConnectionPoller] needsContinuousPolling :false>
####<2016.05.17 14:40:04.978 CEST> <Debug> <EjbMdbConnection> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804978> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[MDConnectionManager] MDB RequestEJBN53ef9fd1XN620a6bdbX16X154a4af673cXN7ffb: Connected to JMS Destination. State = CONNECTED>
####<2016.05.17 14:40:04.978 CEST> <Info> <EJB> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804978> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-010060> <The Message-Driven EJB RequestEJBN53ef9fd1XN620a6bdbX16X154a4af673cXN7ffb has connected or reconnected to the JMS destination jms.kuda.Out_Queue.>
####<2016.05.17 14:40:04.979 CEST> <Debug> <EjbMdbConnection> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804979> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[MDConnectionManager] MDB RequestEJBN53ef9fd1XN620a6bdbX16X154a4af673cXN7ffb: State = CONNECTED>
####<2016.05.17 14:40:04.979 CEST> <Debug> <EjbMdbConnection> <t1-esbmom4la-alsu001> <node1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e68df7bd-6bf7-42a3-b6dd-0f8c69e3494f-00033ad3> <1463488804979> <[severity-value: 128] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <[MDConnectionManager] MDB RequestEJBN53ef9fd1XN620a6bdbX16X154a4af673cXN7ffb: State = CONNECTED>

 

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


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