JNDI bindings not being replicated across servers in a cluster

Question

According to the Weblogic Server documentation, JNDI bindings are
          automatically replicated across the servers in a cluster.
          http://www.weblogic.com/docs45/classdocs/weblogic.jndi.WLContext.html#REPLIC
          ATE_BINDINGS
          This is not proving to be true in my testing. Perhaps it's "just broken", or
          perhaps my cluster isn't correctly configured...
          Here is a reproducible case. Install the following on two or more servers in
          a cluster. You'll need to change line 26 of test1 to reference one of the
          servers explicitly.
          Test 1 works fine, since both web servers connect to the same server for
          JNDI usage. The test should return the last host to hit the page, along with
          the current host name. Alternating between servers in the cluster will
          alternate the results. However, the fact that I'm specifically naming a
          server in the cluster breaks the whole point of clustering -- if that server
          goes down, the application ceases to function properly.
          Test 2, which is supposedly the right way to do it, does not work, an error
          message is logged:
          Tue Jan 04 08:17:15 CST 2000:<I> <ConflictHandler> ConflictStart
          lastviewhost:java.lang.String (from
          [email protected]:[80,80,7002,7002,-1])
          And then both servers begin to report that they have been the only server to
          hit the page. Alternating between servers will have no effect -- both
          servers are looking solely at their own copies of the JNDI tree. No
          replication is occurring.
          What is up with this? Any ideas?
          Tim
          [test1.jsp]
          [test2.jsp]
          

Answer 1

1. yes
          <JMSConnectionFactory AllowCloseInOnMessage="false"
          DefaultDeliveryMode="Persistent" DefaultPriority="4"
          DefaultTimeToLive="0"
          JNDIName="xlink.jms.factory.commerceFactory"
          MessagesMaximum="10" Name="xlink.jms.factory.commerceFactory"
          OverrunPolicy="KeepOld" Targets="bluej,biztalk-lab,devtestCluster"/>
          2. No I am just using the jndi name of the queue.
          This is an example of how I send a message:
               Context ctx = new InitialContext();
          QueueConnectionFactory qconFactory;
          QueueConnection qcon;
          QueueSession qsession;
          QueueSender qsender;
          Queue queue;
          ObjectMessage msg;
          qconFactory = (QueueConnectionFactory) ctx.lookup("xlink.jms.factory.commerceFactory");
          qcon = qconFactory.createQueueConnection();
          qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
          queue = (Queue) ctx.lookup("xlink.jms.queue.biztalk-lab.OrdrspImport");
          qsender = qsession.createSender(queue);
          msg = qsession.createObjectMessage(reportExecutorContainer);
          qcon.start();
          qsender.send(msg);
          qsender.close();
          qsession.close();
          qcon.close();
          3. I don't know those setting (wl 6.1sp7)