JMS Foreign Server Connection Issue Between WebLogic 10.3.6 and WebLogic 8.1 (Doc ID 1542651.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version 10.3.4 to 10.3.6
Information in this document applies to any platform.

Symptoms

A Foreign JMS Server configured on a WLS 10.3.6 domain, connecting to WLS 8.1 domain. When attempting to connect to the remote queue the following exception is seen.

weblogic.jms.common.JMSException: could not find Server Server-1
      at weblogic.jms.common.CDSLocalProxy.getRemoteDispatcher(CDSLocalProxy.java:289)
      at weblogic.jms.common.CDSLocalProxy.access$100(CDSLocalProxy.java:32)
      at weblogic.jms.common.CDSLocalProxy$2.run(CDSLocalProxy.java:158)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
      at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
      at weblogic.jms.common.CDSLocalProxy.registerListener(CDSLocalProxy.java:152)
      at weblogic.jms.common.CDS.processDD(CDS.java:795)
      at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:387)
      at weblogic.jms.common.CDS.ddLookup(CDS.java:1419)
      at weblogic.jms.common.CDS.access$800(CDS.java:42)
      at weblogic.jms.common.CDS$DDLookupTimerListener.timerExpired(CDS.java:1294)
      at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server Server-1
      at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:189)
      at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:68)
      at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:208)
      at weblogic.jms.common.CDSLocalProxy.getRemoteDispatcher(CDSLocalProxy.java:277)
      at weblogic.jms.common.CDSLocalProxy.access$100(CDSLocalProxy.java:32)
      at weblogic.jms.common.CDSLocalProxy$2.run(CDSLocalProxy.java:158)
      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
      at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
      at weblogic.jms.common.CDSLocalProxy.registerListener(CDSLocalProxy.java:152)
      at weblogic.jms.common.CDS.processDD(CDS.java:795)
      at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:387)
      at weblogic.jms.common.CDS.ddLookup(CDS.java:1419)
      at weblogic.jms.common.CDS.access$800(CDS.java:42)
      at weblogic.jms.common.CDS$DDLookupTimerListener.timerExpired(CDS.java:1293)
      ... 4 more
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'weblogic.messaging.dispatcher.S:Server-1' didn't find subcontext 'messaging' Resolved weblogic [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'weblogic.messaging.dispatcher.S:Server-1' didn't find subcontext 'messaging' Resolved weblogic]; remaining name 'messaging/dispatcher/S:Server-1'
      at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
      at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
      at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
      at weblogic.jndi.internal.ServerNamingNode_1036_WLStub.lookup(Unknown Source)
      at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:424)
      at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
      at javax.naming.InitialContext.lookup(InitialContext.java:392)
      at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:18

 



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