This discussion is archived
6 Replies Latest reply: Nov 26, 2012 10:09 PM by Akshay Koul RSS

Not able to connect to a queue under a foreign server.

945526 Newbie
Currently Being Moderated
Not able to connect to a queue under a foreign server.

I'm using WebLogic Server Version: 10.3.3.0. The foreign server is running, and can be pinged from this local server. Also the port where queue resides on foreign server, can be accessed through the my local server.
OS used is AIX 6.0 on both servers.
Tried restarting the local server but nothing helps. Same error continues.

HAS ANYBODY FACED THIS PROBLEM? WHAT IS THE CAUSE AND SOLUTION FOR THIS?

It throws following errors:

<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [Root exception is java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown']
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:247)
     at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
     at javax.naming.InitialContext.internalInit(InitialContext.java:286)
     at javax.naming.InitialContext.<init>(InitialContext.java:211)
     at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
     at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
     at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
     at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:436)
     at weblogic.jms.common.CDS$2.run(CDS.java:503)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown'
     at weblogic.common.internal.BootServicesStub.getMsg(BootServicesStub.java:34)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     at weblogic.security.acl.internal.RemoteAuthenticate.authenticate(RemoteAuthenticate.java:90)
     at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:746)
     at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:678)
     at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:239)
     ... 46 more
>
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null>
<Jun 25, 2012 12:14:45 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:03 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:25 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:35 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:43 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:20:53 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:24:16 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace

Edited by: 942523 on Jun 24, 2012 11:38 PM
  • 1. Re: Not able to connect to a queue under a foreign server.
    RenévanWijk Oracle ACE
    Currently Being Moderated
    How did you define the provider URL:

    - The Error was: Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null

    Maybe WebLogic is unable to resolve IP / hostname. Could try adding the hostname in the etc/hosts file, or maybe directly use
    the IP address in the URL.
  • 2. Re: Not able to connect to a queue under a foreign server.
    945526 Newbie
    Currently Being Moderated
    Thanks René van Wijk for the reply.

    I have a foreign server created in my local server, where i have already given the provider URL. This foreign server has the one queue and one queue connection factory under it to which I'm referring to.

    Under JNDI tree i noticed this, for the queue(NOTIFY_QUEUE) i'm trying to read from one of the EJB:

    ----
    This page displays details about this bound object.

    Failed to create InitialContext using factory specified in hashtable
    ----

    Also,etc/hosts has already these IP entries. Even after hardcoding the provider URL its throwing following:
    ----
    <Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
         at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
         at javax.naming.InitialContext.lookup(InitialContext.java:436)
         at weblogic.jms.common.CDS$2.run(CDS.java:503)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
         at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
         at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
         ... 36 more
    Caused by: java.io.EOFException
         at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338)
         at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768)
         at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:890)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
         at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:130)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    >
    <Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is t3://10.52.50.51:7002>
    ----

    Let me know if any other thing i'm missing or it can be something else like network or some other issue.
  • 3. Re: Not able to connect to a queue under a foreign server.
    Akshay Koul Explorer
    Currently Being Moderated
    Could you help to provide config.xml & XXXXX-jms.xml from both the domains.

    -Akshay
  • 4. Re: Not able to connect to a queue under a foreign server.
    945526 Newbie
    Currently Being Moderated
    HI All

    Thanks for your reply.

    This was issue with network. Even after allowing the port, due to some reason (might be firewall), the issue was coming.
    There was firewall between the app server and the other app server(Foreign server) where the MDB queue was residing. Once we moved the app server to the same zone in the network, where the path between server was without firewall, the queue got connected.

    Thanks all for you time.

    Regards

    G
  • 5. Re: Not able to connect to a queue under a foreign server.
    959882 Newbie
    Currently Being Moderated
    Hi,
    I have a similar problem

    MDB is not able to connect destination on the Foreign JMS Server. I have the bindings file for the MQ created in file:/C:/JNDI-Directory

    <Sep 4, 2012 11:38:45 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: MessageDrivenEJBBean is unable to connect to the JMS destination: jms/q.
    The Error was:
    The destination for the MDB MessageDrivenEJBBean could not be resolved at this
    time. Please ensure the destination is available at the JNDI name jms/q. T
    he EJB container will periodically attempt to resolve this MDB destination and a
    dditional warnings may be issued.>

    --------------------------------------------------------------------------------
    I followed the instructions as specified in
    Integrating WebSphere MQ6 with BEA WebLogic Server 10 using WebLogic Server's Foreign (JMS) Server feature (external blog)
    http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html

    --------------------------------------------------------------------------------
    Contents from weblogic-ejb-jar.xml

    <ejb-name>MessageDrivenEJBBean</ejb-name>
    <message-driven-descriptor>
    <destination-jndi-name>jms/q</destination-jndi-name>
    <connection-factory-jndi-name>jms/qcf</connection-factory-jndi-name>
    </message-driven-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>

    --------------------------------------------------------------------------------
    Contents from Config's descriptor file <descriptor-file-name>jms/mqintegrationtest-jms.xml</descriptor-file-name>

    <weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
    <foreign-server name="MQTestForeignServer">
    <default-targeting-enabled>true</default-targeting-enabled>
    <foreign-destination name="ForeignQueue">
    <local-jndi-name>jms/q</local-jndi-name>
    <remote-jndi-name>q</remote-jndi-name>
    </foreign-destination>
    <foreign-connection-factory name="ForeignConnectionFactoryQCF">
    <local-jndi-name>jms/qcf</local-jndi-name>
    <remote-jndi-name>qcf</remote-jndi-name>
    </foreign-connection-factory>
    <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
    <connection-url>file:/C:/JNDI-Directory</connection-url>
    </foreign-server>
    </weblogic-jms>

    Thanks
  • 6. Re: Not able to connect to a queue under a foreign server.
    Akshay Koul Explorer
    Currently Being Moderated
    First you need to make sure foreign JMS Server is created properly.

    Verify JNDI name (jms/q) is present on server JNDI Tree and also click on JNDI object to verify the classname for the same.

    -Akshay

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points