Foreign Server Redeployment

After creating a foreign server (using the Admin Console) on server 'A',
can I package the newly created foreign server and deploy to server 'B'?

I think you can do this by editing config.xml and restarting admin server and manage server B.
Edited by: alpyanar on 10.Kas.2011 22:37

Similar Messages

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

    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

    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.

  • JMS Module, Foreign Server: Destination unreachable

    Hi,
    In our OSB setup we have 2 weblogic domains (on RHEL5), one for hosting the OSB services and one that is used solely for the purpose of JMS messsaging.
    Therefore we have configured a Foreign Server in our JMS Module on the OSB Domain with following config:
    * JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
    * JNDI Connection URL: t3://fsb-jms1-dev:7901,fsb-jms2-dev:7901
    After deploying an EJB that makes use of this module we see following error in our log files every time when starting a Managed Server:
    ####<Jun 8, 2011 11:36:48 AM CEST> <Warning> <EJB> <esddev148> <osbms1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <11d1def534ea1be0:-27013fcb:1306e9a12ac:-8000-0000000000000016> <13075
    25808959> <BEA-010061> <The Message-Driven EJB: MessageLogWriter is unable to connect to the JMS destination: fsb.jms.MessageLoggingQueue. The Error was:
    javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java
    .rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:64)
    at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
    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.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.jms.common.CDS$2.run(CDS.java:486)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
    at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
    at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
    at weblogic.jms.common.CDS.access$100(CDS.java:41)
    at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java.rmi.ConnectException: Destination unreachab
    le; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination
    at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:352)
    at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:612)
    at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:563)
    at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:789)
    at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:159)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:341)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
    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.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.jms.common.CDS$2.run(CDS.java:486)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
    at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
    at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
    at weblogic.jms.common.CDS.access$100(CDS.java:41)
    at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:194)
    ... 4 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:402)
    at weblogic.rjvm.RJVMImpl.ensureConnectionEstablished(RJVMImpl.java:306)
    at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:350)
    at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:613)
    ... 30 more
    >
    I've allready ensured that the managed servers of the jms cluster are reachable by issuing a connect command from WLST (although making the connection can be time consuming)
    wls:/offline> connect('weblogic','******','t3://fsb-jms1-dev:7901')
    Connecting to t3://fsb-jms1-dev:7901 with userid weblogic ...
    Successfully connected to managed Server 'jmsms1' that belongs to domain 'jmsdevdomain'.
    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.
    wls:/jmsdevdomain/serverConfig> disconnect()
    Disconnected from weblogic server: jmsms1
    wls:/offline> connect('weblogic','******','t3://fsb-jms2-dev:7901')
    Connecting to t3://fsb-jms2-dev:7901 with userid weblogic ...
    Successfully connected to managed Server 'jmsms2' that belongs to domain 'jmsdevdomain'.
    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.
    In my search for a solution I've also read that this could be caused by a bad configured DNS server. Therefore I configured my /etc/nsswitch.conf file to contain only the property files under the parameter hosts.
    Following is an extraction of my /etc/hosts file:
    10.16.85.50 fsb-jms1-dev.localdomain fsb-jms1-dev
    10.16.85.51 fsb-jms2-dev.localdomain fsb-jms2-dev
    10.16.85.52 fsb-osb1-dev.localdomain fsb-osb1-dev
    10.16.85.53 fsb-osb2-dev.localdomain fsb-osb2-dev
    Does anybody have an idea how I can further debug this problem?
    Kind Regards,
    Davy

    Maybe this is of some help: http://www.bea-weblogic.com/namenotfoundexception-when-configuring-foreign-jms-server.html

  • How to access local connection factory created within Foreign Server in OSB

    Hi All
    I am facing an issue in my config plan. We have a RIB Foreign server with the following local connection factory:
    jms/RibAqJmsXATopicConnectionFactory
    I am using the below in my configuration plan:
    <cus:envValueAssignments>
    <xt:envValueType>Service URI</xt:envValueType>
    <xt:location xsi:nil="true"/>
    <xt:owner>
    <xt:type>ProxyService</xt:type>
    <xt:path>RLTPReturnToWarehouse/ProxyServices/ConsumeRIBRTWMessages</xt:path>
    </xt:owner>
    <xt:value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">jms://localhost:7001/jms.RibAqJmsXATopicConnectionFactory/jms.etASNInFromRIBToWH1</xt:value>
    </cus:envValueAssignments>
    and i am getting the below error:
    [java]
    [java] Loading customization File ./dev/OSBCustomizationFile.xml
    [java] Customization applied to the created resources only []
    [java] com.bea.wli.config.customization.EnvValueCustomization@553c13
    [java] Unexpected error: com.bea.wli.sb.transports.TransportException
    [java] Problem invoking WLST - Traceback (innermost last):
    [java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 200, in ?
    [java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 122, in importToALSBDomain
    [java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
    what am i missing here?

    [java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
    Looks like the JNDI that you created for the ConnectionFactory is not reflected in the server.
    Login to WLS Console> Summary of Servers > server_name > View JNDI Tree
    Browse to the JNDI tree and see if your JNDI is visible there. If it is not then, please restart the server and recheck.
    Once you are able to find it in the JNDI tree, then execute the customization file.
    If you have modified the existing JNDI properties (that have a small exclamatory symbol) then any changes to those are not reflected till all the servers in the cluster are restarted.
    If it still does not work, then recreate a new Connection with a different name and then retry. It should work then.
    Thanks,
    Patrick

  • RJVM has already been shutdown error while looking upto Foreign Server

    Hi,
    I am trying to set up 2 new servers in a clustered environment. In this I have configured a Foreign Server which is looking up to queues in different server.
    The structure is like this: 1 Foreign Server with 2 Queues and 1 Connection factory with exactly same name as they present on the host server.
    While starting the server, I am getting an exception:
    <Nov 5, 2012 7:39:58 PM EET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ClonedQueueAnonymousWaiter is unable to connect to the JMS destination: MDB_QUEUE_RESPONSE. The Error was:
    javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: RJVM has already been shutdown; nested exception is:
         java.io.IOException: RJVM has already been shutdown]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
         at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
         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:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.jms.common.CDS$2.run(CDS.java:486)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
         at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
         at weblogic.jms.common.CDS.access$100(CDS.java:41)
         at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: java.rmi.UnmarshalException: RJVM has already been shutdown; nested exception is:
         java.io.IOException: RJVM has already been shutdown
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:360)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
         ... 21 more
    Caused by: java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         ... 24 more
    Caused by: java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:513)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:900)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:404)
         at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
         ... 24 more
    >
    Weblogic is installed in Solaris machine and welogic's version is 10.3.4.0 with Java version 1.6.0 update 33. I have checked the firewall, /etc/hosts but there are no issues with that.
    The JNDI Connection URL is configure like: t3://xx.xxx.x.xx,xx.xxx.x.xx:7001/
    I have tried giving like this also: t3://xx.xxx.x.xx:7001,xx.xxx.x.xx:7001/ or t3://hostname1,hostname2:7001/ or t3://hostname1:7001,hostname2:7001/
    but nothing worked.
    The foreign servers are accessible from my Application Server when I do the telnet on the port. There is no cross domain security required. Funny thing is I have a same set-up in two other application server (in cluster again) and there on configuring the Foreign server to same IPs, I am not facing any issues at all.
    Can anyone please help me with this. Searched all over the place but have no clue regarding this. Many forums mentioned about firewall and etc/hosts but that is also not case it seems.
    Regards,
    Priyam

    809364 wrote:
    You can apply the below debug flags to check t he RJVM Communication in detail and figure out what's going wrong and do apply it at both the side
    -Dweblogic.kernel.debug=true
    -Dweblogic.debug.DebugConnection=true
    -Dweblogic.StdoutDebugEnabled=true
    -Dweblogic.log.LogSeverity=Debug
    -Dweblogic.log.LoggerSeverity=DebugI added the debug as you mentioned and I get the below information there:
    <Nov 6, 2012 11:41:16 AM EET> <Debug> <RJVM> <BEA-000500> <RJVMFinder trying to find rjvm for t3://moon1,moon2:7001->moon1,moon2:[7001, -1, -1, -1, -1, -1, -1]->[]
    Active RJVMs:
    {-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer on [10.160.1.115:7001]=weblogic.rjvm.RJVMImpl@4320d68d - id: '-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer' connect time: 'Tue Nov 06 11:40:26 EET 2012'}
    Synonyms:
    {}>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Bootstrapping connection to: 'moon1/10.160.1.40:7001' using: 't3'>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Looking for a new connection for channel Default[t3]:t3(t3):venus1:7001:null:-1 to remote server 0B:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1,-1,-1] active connections: {}>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <New connection for protocol t3, remote address moon1/10.160.1.40, remote port 7001, over channel Default[t3]>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Added: 'Default[t3]:t3(t3):venus1:7001:null:-1' connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'. Connections list size 1>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Bootstrapping using a: 't3', connection to: 'moon1/10.160.1.40' on port: '7001'>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Created RJVM for: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1 on [10.160.1.40:7001]', Active RJVMs:
    {-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer on [10.160.1.115:7001]=weblogic.rjvm.RJVMImpl@4320d68d - id: '-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer' connect time: 'Tue Nov 06 11:40:26 EET 2012', -3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1 on [10.160.1.40:7001]=weblogic.rjvm.RJVMImpl@7bb8a8c6 - id: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' connect time: 'Tue Nov 06 11:41:17 EET 2012'}
    Synonyms:
    {}>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Remote heartbeat: '60000', local heartbeat: '60000'>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Setting heartbeat for RJVM: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' to: '60000' milliseconds>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Added: 'Default[t3]:t3(t3):venus1:7001:null:-1' connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'. Connections list size 1>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000517> <Error on connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'
    java.io.EOFException
    java.io.EOFException
         at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:345)
         at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:826)
         at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:760)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:941)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:898)
         at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:126)
         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)
    >
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Signaling peer: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' gone - weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Closed and removed: 't3' connection to: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1'. Connections list size 0>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Closing: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1'>
    <Nov 6, 2012 11:41:17 AM EET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ClonedQueueAnonymousWaiter is unable to connect to the JMS destination: MDB_QUEUE_RESPONSE. 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:470)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
         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:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.jms.common.CDS$2.run(CDS.java:486)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
         at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
         at weblogic.jms.common.CDS.access$100(CDS.java:41)
         at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    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_1034_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
         ... 21 more
    Caused by: java.io.EOFException
         at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:345)
         at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:826)
         at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:760)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:941)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:898)
         at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:126)
         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)
    >
    Seems like Peer gone exception is the root cause of this. Any idea for this ?
    Regards,
    Priyam
    Edited by: Priyam Srivastava on Nov 6, 2012 2:49 AM

  • Issue with osb + weblogic foreign server AQ configuration

    Hi ,
    I am trying out a scenario wherein, OSB publishes a message onto an Oracle AQ JMS Topic.
    I have created the Foreign Server and have used the Local JNDIs of the connection factory and the destination within my OSB business service. But then, my business service fails to publish the message onto the AQ giving below exception in the server logs:
    "<BEA-169807>There was an error while making the initial connection to the JMS resource named ALSB_JMS_SessionPool_-541341947 from within an EJB or a servlet. The server will attempt the connection again later. The error was oracle.jms.AQjmsException: Error creating the db_connection"
    Below are the configurations that I have used for configuring the foreign server
    Connection Factory - LocalCF | Local JNDI - LocalCF | Remote JNDI - XATopicConnectionFactory
    Destination - ETASNIN | Local JNDI - ETASNIN | Remote JNDI - Topics/ETASNIN
    The Business Service URL: jms://xxxxhost:7011/LocalCF/ETASNIN
    **P.S:** I have tried out the same scenario of interfacing OSB with AQ JMS on a Windows box it works fine... But the above is the case on a UNIX box. Also, I am using PS3 of OSB with 10.3.4 of weblogic server.
    Any Suggestions on this would really help and is much appreciated...
    Thanks,
    Manoj Nair

    Hi Manoj,
    how it was solved?

  • Monitor JMS Foreign Server

    Hi,
              I have configured the IBM MQ server as a foreign server in one of the JMS Module of WLS9.1. I am able to identify it using JMX (MBeans).(I thought this was a good approach if u have any other approach for it? reply me).
              Now i want to monitor the Foreign Server i.e. capture the Foreign Server status whether the server is active or not and accordingly deploy/undeploy the Foreign Server.
              Can anyone go through this and reply me with the solution? PLzzzzzzzzzz its very urgent

    A "foreign server" is stateless configuration code that simply maps an application's JNDI lookup request into another vendor's JNDI context. It provides no monitoring.
              If you want to determine the status of the server that a foreign server references, you need to either (A) monitor the foreign server directly or (B) monitor the status of an application or service that depends on the foreign server.
              Tom

  • MDB cannot connect to JMS destination using Foreign Server

    Hi everyone,
    I have configured foreign jms server in weblogic but when MDB tries to connect to specific queue, it gets the following exception:
    I would really appreciate if anyone could help me.
    <Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination or bind to JCA resource adapter: xcg2/smsInQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
    <Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination: xcg2/smsInQueue. The Error was:
    [EJB:011010]The JMS destination with the JNDI name: jmsxcg.out could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml or corresponding annotation is correct, and the JMS destination has been deployed.
    javax.naming.InvalidNameException: jmsxcg.out: [LDAP: error code 34 - Invalid DN]; remaining name 'jmsxcg.out' NestedException Message is :jmsxcg.out: [LDAP: error code 34 - Invalid DN]>
    MDB annotation looks like this:
    @MessageDriven(name="SmsReceiver", mappedName="xcg2/smsInQueue",
    activationConfig = {
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
    @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
    public class SmsReceiverBean implements MessageListener
    weblogic-ejb-jar.xml excerpt:
         <weblogic-enterprise-bean>
              <ejb-name>SmsReceiver</ejb-name>
              <message-driven-descriptor>
                   <pool>
                        <max-beans-in-free-pool>10</max-beans-in-free-pool>
                        <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
                   </pool>
                   <connection-factory-jndi-name>echoQueueConnectionFactory</connection-factory-jndi-name>
              </message-driven-descriptor>
              <transaction-descriptor>
                   <trans-timeout-seconds>600</trans-timeout-seconds>
              </transaction-descriptor>
    <dispatch-policy>MdbSmsWorkManager</dispatch-policy>
         </weblogic-enterprise-bean>
    and the configuration of foreign-server:
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms">
    <foreign-server name="serverr">
    <sub-deployment-name>Subdeployment</sub-deployment-name>
    <foreign-destination name="sms queue>
    <local-jndi-name>xcg2/smsInQueue</local-jndi-name>
    <remote-jndi-name>jmsxcg.out</remote-jndi-name>
    </foreign-destination>
    <foreign-connection-factory name="Connection Factory">
    <local-jndi-name>echoQueueConnectionFactory</local-jndi-name>
    <remote-jndi-name>QueueConnectionFactory</remote-jndi-name>
    </foreign-connection-factory>
    <initial-context-factory>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory>
    <connection-url>tibjmsnaming://xx.xx.xx.xx:7222</connection-url>
    </foreign-server>
    </weblogic-jms>
    PS. I'm able to connect to the weblogic jndi, get connectionFactory echoQueueConnectionFactory, then lookup queue and grab messages so that's i suspect there is something wrong with configuration

    Hmm - I'm not sure what's going on. Two thoughts --
    Thought 1 - According to my (admittedly minimal) research, Tibco is complaining about a syntax error in the lookup name. Perhaps the problem has something to do with your use of a "." in the queue name "jmsxcg.out": WL or Tibco JNDI might be interpreting the "." as a subcontext or some-such. Perhaps try renaming the queue to "jmsxcg_out" throughout (in Tibco and in your Foreign JMS reference).
    Thought 2 - It probably won't make a difference, but you might want try specifying the source destination via the "destinationJndiName" config property instead of via "mappedName".
    @MessageDriven(
      name = "MyMDB",
      activationConfig = {
        @ActivationConfigProperty(propertyName  = "destinationType",
                                  propertyValue = "javax.jms.Queue"),
        @ActivationConfigProperty(propertyName  = "destinationJndiName",
                                  propertyValue = "MyQueue") // Ext. JNDI Name
    )HTH,
    Tom

  • Query while configuring foreign server in JMS module

    Hi All,
    I'm configuring foreign server in my weblogic 10.3 to access the queues in the remote weblogic server 10.3. while configuring the foreign server it is asking for the destination and connection factory JNDIs for both local and remote server. My question is whatever JNDI we gave for the local destination or connection factory whether it should be already existing one or do we need to give that JNDI value unique for that Foreign server. I mean whether we have to create queue and connection factory and use their JNDIs or no need to create queues and connection factory and directly giving the JNDI names.
    And one more question is while configuring JMS adapter in Jdev11g what should be the JNDI name to be given in the JMS adapter configuration wizard.
    Thanks.

    my scenario is I have created a queue and connection factory in one weblogic server A and i have created foreign server in other weblogic server B and using the unique local JNDI names and JNDI names of B in remote JNDI for destination and connection factory tabs. Now in the deployment plan i have created one connection pool in the resource adapter(in my scenario it is JMS adapter) where i have gave the connection factory as local JNDI connection factory.
    Now I created one composite in which i have created one JMS adapter to place data into the queue and deployed the composite. when executing the composite i'm getting an error saying that the resource adapter could not able to find the JNDI name.

  • Weblogic 8.1: Remote/Foreign Server JMS - Destination not found error

    Hi
    This is our current setup: Weblogic Server 8.1 with JMS module running on the same instance as the application. We would like to move JMS out into its own box. I am currently setting up my development environment to test the new setup. These are the steps I followed:
    * Setup the server instance running the application on one box (Box1). Removed the existing JMS Connection Factory and Destination JNDI setup
    * Setup a server instance on another box (Box2) without the application. Created the necessary JMS Connection Factories and Destinations. Started the server instance on Box2
    * Added a Foreign Server configuration on Box1. Created the connection factory and destinations under this foreign server pointing to Box2
    * The Foreign JNDI names are being bound correctly (I verified the JNDI tree on Box1). Restarted the server instance of Box1
    Message-Driven Beans deployed on Box1 are unable to retrieve messages from Box2. The exception thrown is given below. Any help in troubleshooting and resolving this issue is appreciated.
    <Warning> <EJB> <myserver> <main> <<WLS Kernel>> <> <BEA-010061> <The Message-Driven EJB: MyBean is unable to connect to the JMS destination: jms/my.application.firstQueue. The Error was:
    weblogic.jms.common.JMSException: Destination not found
    weblogic.jms.common.JMSException: Destination not found
    at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
    at weblogic.jms.backend.BESession.createConsumer(BESession.java:153)
    at weblogic.jms.backend.BESession.invoke(BESession.java:1457)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
    at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:232)
    at weblogic.jms.frontend.FESession$3.run(FESession.java:1058)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1054)
    at weblogic.jms.frontend.FESession.invoke(FESession.java:2552)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
    at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1860)
    at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1691)
    at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1530)
    at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1720)
    at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:2019)
    at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1180)
    at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:846)
    at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
    at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1660)
    at weblogic.ejb20.deployer.EJBDeployer.startMessageDrivenBeans(EJBDeployer.java:1555)
    at weblogic.t3.srvr.T3Srvr.startMDBs(T3Srvr.java:948)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1024)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    Edited by: user8773992 on Sep 2, 2009 11:31 AM

    1 - Ensure that the MDB is configured to reference the remote connection factory AND remote destination.
    2 - If using the foreign JMS server facility, ensure that it defines the URL of the remote cluster/server, a connection factory mapping, and a destination mapping. Also ensure that the MDB connection factory and destination descriptor fields reference the local JNDI names for the mappings.
    3 - If not using the foreign JMS server facility, ensure that the MDB descriptor has the URL of the remote cluster, and a destination JNDI name that's in the remote cluster. (The connection factory JNDI name is not needed in this case, as the MDB will automatically look for a default connection factory that MDB's use.)
    I think the MDB chapter of the EJB programmer's guide will likely be helpful here. The latest documentation for the latest release may be more up-to-date than 8.1 -- the concepts are the same with the newer releases.
    Tom

  • OSB to MQ, using Foreign Server

    Hi All,
               I am working on OSB to MQ connectivity, using Foreign Server. I was able to establish the connectivity using Sun JDK 1.6. However when I JRockit 1.6 is used, connectivity is not working. There are stuck threads in Weblogic, when weblogic has to invoke the MQ Jars. Any suggestions, will be greatly appreciated.
    Regards.

    Hi
    Thats very strange behavioural diffrerence between Sun & Jrockit.
    Take it you have gone through the stuck threads and realised threads were marked stuck when trying to invoke / load MQ jars? can you copy the stuck threads referring that please.
    Have you tried loading those MQ jars in the classpath of the server .. That way all the necessary jars/classes will be available local to the instance
    and can be located by classloader without much delay.
    HTH
    Sri

  • OSB: JMS Foreign Server

    Hi!
    I have problem with configure BusinesService for HornetQ JMS Server.
    Connection cannot instantiate:
    <Error> <WliSbTransports> <BEA-381502> <Exception in JmsInboundMessageContext.close : javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory jms.WLReceiverCF failed: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
    javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory jms.WLReceiverCF failed: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
         at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:29)
         at weblogic.deployment.jms.JMSConnectionHelper.lookupConnectionFactory(JMSConnectionHelper.java:485)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:268)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)ProxyService for this foreign server work fine.
    Help please!
    Best Regards,
    lam
    Edited by: laaam on Nov 25, 2010 1:02 PM
    Edited by: laaam on Nov 25, 2010 7:52 PM

    Hi Lam,
    I have a successful configuration to JBoss JMS . My foreign server configuration is like this:
    <foreign-server name=”ForeignServer”>
    <default-targeting-enabled>true</default-targeting-enabled>
    <foreign-destination name=”A”>
    <local-jndi-name>A</local-jndi-name>
    <remote-jndi-name>queue/A</remote-jndi-name>
    </foreign-destination>
    <foreign-connection-factory name=”FConf”>
    <local-jndi-name>FConf</local-jndi-name>
    <remote-jndi-name>ConnectionFactory</remote-jndi-name>
    <username>esbuser</username>
    <password-encrypted>{3DES}90sIZwo6Llr9r73p+VXkvQ==</password-encrypted>
    </foreign-connection-factory>
    <initial-context-factory>org.jnp.interfaces.NamingContextFactory</initial-context-factory>
    <connection-url>jnp://localhost:1099</connection-url>
    </foreign-server>
    The difference I can see is the extra jndi property java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces. Can you try removing that ?
    Another try if the above doesn't work is to specify the full jms business service URI if your JBoss destination is not a secured one (if no user name/password is required to access it).
    jms://<WLSHostname>:<wls port>/jms.WLReceiverCF/jms.queue.RegisterDocumentResponse

  • Foreign server or JMS Bridge?

    Weblogic 11g
    WebsphereMQ 7
    Good morning,
    I have a question regarding JMS architecture.
    We’re going to deploy a new app using JMS but all the messaging architecture will be on WebshereMQ.
    Our middleware team recommends us to create a foreign server to communicate with MQ.
    So my question is quite simple, why using a Foregin server instead of a JMS Bridge?
    I’d have used the latter as it aims to communicated with other Message Oriented Middleware.
    Thanks for your wise advices

    You can find more information about integrating with a remote or foreign JMS provider at
    http://docs.oracle.com/cd/E17904_01/web.1111/e13727/interop.htm#i1009767
    This doc discusses a number of approaches and best practices for each of them.
    The messaging bridge does introduce an extra hop; messages are put into a local destination and then forwarded to the final destination. This is useful when the remote destination is not highly available. The bridge will take the messages even when remote destination is not available and then forward them with build-in retry logic when the remote destination becomes available.
    If the remote destination is highly available, foreign JMS server is preferable since it directly access the final destination without an extra hop.
    Hope this helps.
    Dongbo

  • Difference between Foregin Jndi Providers & Foreign Server in weblogic 10.3

    What is the difference between the Foreign Jndi Providers & Foreign Server under Jms Modules in Weblogic 10.3, any suggestions could be appreicated

    Thanks Faisal for the reply.
    In this link, the JNDI connection URL is pointing to local folder. I need to access it from a remote MQ server. Do you have any pointers on how to form the connection url in this scenario?

  • Foreign Server/Destination

    I just went through a painful process of getting a foreign server/destination up and running in WLS 9.2.
              Our production env is moving to 9.2 but a dependent topic is staying on 8.1. Creating a foreign server seemed the ideal approach. I was able to get it to work with <provider-url></provider-url> reference in <message-driven-descriptor> but this requires hard-coding the URL which is bad. We like to move EARs to dev envs and if they work out then copy/migrate them to prod. Hardcoding URLs require rebuilding the EAR.
              Anyway, at first I tried setting up a foreign server and foreign destination but the mdb stopped working. Could not reference the Server. Checking the newsgroup, I discovered that a foreign connection factory needs to be defined and used. Now it's working.
              One thing that has me worried is that I need to manually insert <connection-factory-jndi-name> into the weblogic.ejb.jar.xml. If I update the @MessageDriven annotation, it could wipe out my changes in xml file. How come @MessageDriven does not have a parameter for the connection factory jndi as well as provider url? There is something called @MessageDestination that contains provider url but it appears to be for something else.
              The docs are poor in describing how something like this should be setup. An example would have been really helpful. MedRec and the other example had no foreign server references.

    You can also setup foreign server/Destination with the following annontations in your mdb. I hope this helps
              @ForeignJmsProvider(connectionFactoryJndiName = "weblogic.jms.XAConnectionFactory",
                        providerUrl = "t3://localhost:7021",
                        initialContextFactory = "weblogic.jndi.WLInitialContextFactory")

Maybe you are looking for