JNDI Lookup for JMS Topic issue.......!

Question

Hi,
          Our application is deployed on two nodes (MS1 and MS2 in a cluster) and I created JMSServer on MS1, JMS ConnectionFactory and Distributed Topic are targeted on both MS1 and MS2 i.e on entire cluster.
          We have the JMS Code in postStart() method of starup class which extends ApplicationLifecycleListener which would create the JMS Subcriber and set the message listener on to it.
          code snippet:
               System.out.println("createSubscriber called");
               subSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
               // Lookup for the Topic
               Topic cadTopic = (Topic) ctx.lookup("JMSTopicLog4j");
               System.out.println("Topic is: " + cadTopic.getTopicName());
               // Create JMS Subscriber.
               cadSubscriber = subSession.createSubscriber(cadTopic);
               // Set the listener to Subscriber.
               cadSubscriber.setMessageListener(new CADMessageListener());
               topicConnection.start();
          When I start the cluster (managed Servers MS1 and MS2) for the first time and deploy the application on them (entire cluster) it works well i.e. message listener is active and able to receive messages published by publisher but when I try to stop and start MS2 it gives the following exception during server startup
          javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''
          javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''; remaining name 'JMSTopicLog4j'
          at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1123)
          at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:250)
          at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
          at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:204)
          at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:267)
          at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
          Note: I thought my application context is getting started before JNDI tree is loaded but I could see that it is able to lookup the ConnectionFactory and throws the given exception when it comes to lookup code of JMS Topic.
          is there any configuration issue or am I missing something? Please help me in this regard.
          Thanks in advance.
          Kris.

Answer 1

Very interesting, I mean in the sense that we have the same setup, but instead of topic we are using the queues.
          And our problem is exactly the same,deployment works but after restart same javax.naming.NameNotFoundException happens on server 2.