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

Similar Messages

  • 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")

  • Weblogic 10 Ant task, JMS Module & Foreign JMS Destinations

    Any body knows how to configure JMS System Modules (which got introduced in WL ver. 9) and other JMS MBeans such as JMS Destinations and ConnectionFactories under the newly created JMS Module, using ant task for Weblogic 10.3 ?
    Also, when I create the ForeignJMSServer and the child MBeans such as Foreign Destinations and ConnectionFactories using ant task, it just creates the ForeignJMSServer and not creating the child MBeans. The problem is with WL 10. In WL 8.1, it works fine.
    In Weblogic 8.1, þe ant target for this job is as follows.
    ===========================================================================
         <target name="prepareForeignJMSServer">
    <wlconfig url="t3://localhost:7001" username="weblogic"
    password="weblogic" failonerror="false">
    <create type="ForeignJMSServer" name="myForeignJMSServer" property="temp-jms-server">
    <set attribute="InitialContextFactory" value="weblogic.jndi.WLInitialContextFactory"/>
    <set attribute="ConnectionURL" value="t3://192.168.0.23:7001"/>
    <set attribute="Targets" value="mydomain:Name=myserver,Type=Server"/>
    <create type="ForeignJMSConnectionFactory" name="MyRemoteCF">
    <set attribute="LocalJNDIName" value="MyLocalCFJNDI"/>
    <set attribute="RemoteJNDIName" value="MyRemoteCFJNDI"/>
    <set attribute="Username" value="weblogic-remote"/>
    <set attribute="Password" value="weblogic-remote"/>
    </create>
    <create type="ForeignJMSDestination" Name="MyRemoteQueue1">
    <set attribute="LocalJNDIName" value="MyLocalQueue1JNDI"/>
    <set attribute="RemoteJNDIName" value="MyRemoteQueue1JNDI"/>
    </create>
         </create>
              </wlconfig>
         </target>
    =====================================================================
    This target runs without error in WL 10, but does not create the ForeignJMSConnectionFactory and ForeignJMSDestination.
    If some one knows the solution, please give me advice.
    Thanks,

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

  • 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

  • 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.

  • Edit of Foreign JMS module in admin console causes redeployment error

    A JMS module (-jms.xml) for a foreign JMSServer specifies the url of the real JMS server. I am trying to use a deployment plan to make this url a deployment property.
    Following the instructions in "Configuring and Managing Weblogic JMS" and "Deploying Applications to Weblogic Server", I have deployed the module with a fixed URL, and then attempt to edit the url in the admin console. The admin console correctly creates a deployment plan to hold modified value, but then can't redeploy the module due to errors during deployment.
    I experience these errors with the module deployed stand-alone, or when bundled with my enterprise application. I also get the same error if I produce the deployment plan using the PlanGenerator.
    The error seems to be a bug in the deployment plan machinery, since the xpath it produces for the variable-application does not match the xml schema for <weblogic-jms>. The plan.xml refers to "/weblogic-jms/foreign-server[name="IQN_OLTP_FOREIGN_JMS_Server"]/connectionurl" while the schema defines "/weblogic-jms/foreign-server/connection-url".
    Any advice would be welcome.
    We are running 9.2 SP3.
    The messages in the admin console logs are:
    ####<Jan 22, 2009 12:07:02 PM MST> <Info> <J2EE> <truman> <IQN_ADMIN_SERVER> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (
    self-tuning)'> <system> <> <> <1232651222010> <BEA-160166> <References were found in deployment plan for module 'IQN_JMS_OLTP_FOREIGN-jms.xml'
    with uri, '.'. The plan was merged.>
    ####<Jan 22, 2009 12:07:02 PM MST> <Error> <J2EE> <truman> <IQN_ADMIN_SERVER> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default
    (self-tuning)'> <system> <> <> <1232651222024> <BEA-160197> <Unable to load descriptor weblogic.deploy.api.spi.config.DescriptorParser$1@1c7654
    8 finder: weblogic.utils.classloaders.CodeGenClassFinder@1ca6109 annotation: /. of module IQN_JMS_OLTP_FOREIGN-jms.xml. The error is weblogic.d
    escriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'default-targeting-enabled@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://ww
    w.bea.com/ns/weblogic/90:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'foreign-destination@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://www.bea.
    com/ns/weblogic/90:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'foreign-destination@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://www.bea.
    com/ns/weblogic/90:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'foreign-connection-factory@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://w
    ww.bea.com/ns/weblogic/90:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'foreign-connection-factory@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://w
    ww.bea.com/ns/weblogic/90:<null>
    /home/jbullock/development/patch841/domains/IQN/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential
    -encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http://www.bea.com/ns/weblogic/90' instead of 'connectionurl@http://www.bea.com/ns/w
    eblogic/90' here in element foreign-server@http://www.bea.com/ns/weblogic/90:<nullplan.xml>

    I also tried this, without success. Changing the deployment plan to use the element name "connection-url" leads to a different error during deployment:
    <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, IQN_JMS_OLTP_FOREIGN [archive: ../../package/jms/IQN_JMS_OLTP_FOREIGN-jms.xml], to IQN_BATCH IQN_OLTP1 .>
    plan xpath defines an element [connection-url] that is not valid!(There is also a subtle variation in the xpath used in the deployment plan: It isn't clear whether the deployer expects /weblogic-jms/foreign-server/[name="IQN_OLTP_FOREIGN_JMS_Server"]/connection-url or /weblogic-jms/foreign-server[name="IQN_OLTP_FOREIGN_JMS_Server"]/connectionurl. The former, although not really correct XPath syntax, seems to be required for other elements, but in this case, the PlanGenerator emits latter, which is correct XPath, but has the wrong element name.)
    Edited by: John Bullock on Jan 26, 2009 11:59 AM

  • Need separate duplicate JMS modules for each server?

    Using WebLogic 9.2.2 on AIX 5.3.
    I'm trying to set up a domain with 6 managed servers. I need to deploy several JMS queues and a foreign server to each JMSServer on each server. I looked at the JMSModule object, and I'm trying to determine whether it's possible to define a single JMSModule that I can deploy to all of my servers. So far, this doesn't appear to be possible. As a result, I have to do tons of painful cut/paste inside the console. Is this how it's supposed to work?

    David,
    Sorry, if I was not clear earlier.
    A Module can be targeted to a single Cluster, one or more comma separated list of WLS servers and the servers don't have to be part of a cluster (note that certain resources such as UDD or CF that can be targeted to an entire cluster, cannot be done so, if the module is not targeted to the cluster. And to achieve the same, the user has to manually add/remove the managed servers to the list of Module's/sub-deployment's targets whenever a server is added or removed to/from the cluster/domain).
    So, in your case, you can define all the JMS resources for that domain in a single Module descriptor and deploy it to a list of all the managed servers. Then you can use the sub-deployments to group and target them onto other related targets (for example, one or more queues can be grouped as a sub-deployment and targeted to a single JMSServer that is hosted by one of the WLS server instance, where the Module is currently targeted to, etc).
    I believe you are creating/using a "system resource" type module via Admin console, the JMSModules wizard shall walk you through the targeting page, where you can see all the available target servers/clusters.
    Here is an example of config.xml snippet for this kind of module targeting :
    <jms-system-resource>
    <name>SystemModule-0</name>
    <target>Server-0,Server-1</target>
    <sub-deployment>
    <name>ConnectionFactory-0</name>
    <target>Server-0,Server-1</target>
    </sub-deployment>
    <sub-deployment>
    <name>Queues</name>
    <target>JMSServer-0</target>
    </sub-deployment>
    <descriptor-file-name>jms/systemmodule-0-jms.xml</descriptor-file-name>
    </jms-system-resource>
    and the corresponding JMS module descriptor file snippet (can be found under DOMAIN_DIR/config/jms dir) as shown below:
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls
    ="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http:/
    /www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
    <connection-factory name="ConnectionFactory-0">
    <sub-deployment-name>ConnectionFactory-0</sub-deployment-name>
    <jndi-name>ConnectionFactory-0</jndi-name>
    <security-params>
    <attach-jmsx-user-id>false</attach-jmsx-user-id>
    </security-params>
    </connection-factory>
    <queue name="Queue-0">
    <sub-deployment-name>Queues</sub-deployment-name>
    <jndi-name>Queue-0</jndi-name>
    </queue>
    </weblogic-jms>
    That being said, depending on, how many resources (factories, destinations etc) you are having and how you are going to group them, you may end of with too many sub-deployments within a single module, for which you need to carefully select targets/manage them.
    Both approaches (one module descriptor with many sub-deployments and many module descriptors with fewer sub deployments) have positives and negatives, when its comes to manageability. The recommended best practice is to have the JMS resource configuration split into more than one module with fewer number of sub-deployments within each, to have finer control over the resource configuration/management.
    Sounds like, you are trying to configure one queue on every managed server, that has duplicate(same) configuration properties. If that is the case, you can try using the UDD (Uniform Distributed Destination), that comes with automatic member (physical destination) management on all of its targets. That way, all you need is one UDD resource configuration/sub-deployment in the module and target the sub-deployment to the same targets as the module's targets (or accept the default targeting option, if available in the resource targeting page).
    More information on UDDs can be found here:
    http://edocs.bea.com/wls/docs100/jms/dds.html#wp1313025
    Hope this helps.
    Thanks
    Kats

  • 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

  • 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

  • What is the association between JMS Server and JMS Module in weblogic 10?

    Hi,
    I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
    And I have created a JMS Server and Targetted to the current running server (Admin Server).
    But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
    queue = (Queue) initialContext.lookup("jndi_queue");
    Exception:
    javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
    But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
    How JMS Module and JMS server are associated.
    My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
    Please advice.
    Thanks....

    Hi,
    Once you have JMS servers configured:
    Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
    Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
    Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
    For more information, reference the "best practices" chapter of the JMS configuration guide:
    http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
    I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
    Hope this helps,
    Tom

  • Need the JNDI name for Destinations present in JMS Modules

    Hi all,
    I need JNDI`s of all the Destinations present in JMS Modules. With this code i am able to get all info about the JMS Modules, Destinations and as well as information about messages, but still not able to extract JNDI of Destination. Can some one give me pointer on this ?
    try {
    JMXServiceURL serviceUrl =
    new JMXServiceURL(
    "service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.runtime");
    System.out.println("Connecting to: " + serviceUrl);
    Hashtable env = new Hashtable();
    env.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,
    "weblogic.management.remote");
    env.put(javax.naming.Context.SECURITY_PRINCIPAL, "weblogic");
    env.put(javax.naming.Context.SECURITY_CREDENTIALS, "welcome1");
    jmxCon = JMXConnectorFactory.newJMXConnector(serviceUrl, env);
    jmxCon.connect();
    MBeanServerConnection con = jmxCon.getMBeanServerConnection();
    Set<ObjectName> mbeans = con.queryNames(queryObjectName, null);
    for (ObjectName mbeanName : mbeans) {
    String temp = mbeanName.toString();
    System.out.println(temp);
    String[] mBeanAttributes = {"Name", "DestinationType", "MessagesCurrentCount",
    "MessagesPendingCount", "MessagesReceivedCount", "MessagesHighCount" };
    queryObjectName = new ObjectName("*:*,Type=JMSDestinationRuntime");
    mbeans = con.queryNames(queryObjectName, null);
    for (ObjectName mbeanName : mbeans) {
    AttributeList attributes = con.getAttributes(mbeanName, mBeanAttributes);
    System.out.println((Attribute) attributes.get(0)+ "" +
    (Attribute) attributes.get(1)+
    (Attribute) attributes.get(2)+
    (Attribute) attributes.get(3)+
    (Attribute) attributes.get(4)+
    (Attribute) attributes.get(5));
    String temp = mbeanName.toString();
    ObjectInstance inst = con.getObjectInstance(mbeanName);
    System.out.println(temp);
    finally {
    if (jmxCon != null)
    jmxCon.close();
    But Nowhere i am getting the JNDI of destination Queues or Topics.
    Edited by: mdev on Feb 21, 2012 5:21 PM

    You are accessing the runtime mbean of a JMS destination. The JNID name of a destination is not available on the runtime destination MBean.
    If you are using jms-system-resource to deploy your JMS module, you should be able to access the deployment mbean of the destination. The starting MBean for JMS is JMSSystemResourceMBean in this case.

  • Weblogic to Tibco using foreign server Error!!!

    Hi,
    I am integrating Weblogic 11g server with Tibco EMS using the foreign jms server.
    I have created a foreign jms server, foreign connection factory and a foreign destination in the jms module.
    but while sending the message to foreign destination queue i am getting the following error::
    [JMSClientExceptions:055014] Error Sending Message
    Could anyone help me on this?
    Thanks in advance,
    Uday

    Hi,
    To help you I need the class.java, xslt or xquery from where you are trying to send the message and the settings you gave to the queue in the foreing server.
    Make sure you are giving up the correct security parameters .
    Regards.
    Lucas.

  • 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.

Maybe you are looking for

  • Compressor 2.3.1 Cannot submit batch error message What is causing this?

    Just installed FCP 5 with DVD Studio pro 4 and Compressor 2 and tried to do a batch compression exported from FCP, I selected the compression I wanted and chose my destination and clicked submit and I get this error message "Cannot submit batch Unabl

  • How can I delete one of my apple id

    My husband has a Apple Mac I have a I pad 2 and a I phone 4. When I go into the App Store to sign in the I pad and phone want me to sight in as his apple I'd Please help thank you Fishponds

  • User profile doesn't quite load...

    This morning when I tried to log-in using my user ID, the desktop came up but the dock, hard drive icon and menu bar appeared then disappeared, cycling through endlessly. I cannot click on the hard drive icon or anything on the menu bar (when it appe

  • Photosmart D7560 will not print envelopes - load paper into main tray

    My photosmart d7560 will not print envelopes, after moving the envelope into position for printing, the message "load paper into main tray" is displayed.  It does print the envelope data correctly on a piece of 8.5x11 paper.  Setup is for a #10 enve

  • Viewing images and flash in brower

    I have create a flash swf file and a background image in photoshop, an I am having a problem viewing either in the browser. The page is blank where the file is suppose to be. I've recently had switched to a different server using http vs htpdocs, the