NameNotFoundException when using JMS in a Cluster

Question

Whenever I start my cluster with my test application deployed or on occasion while my cluster is running and I'm deploying my test application I get the following exception:
javax.naming.NameNotFoundException: Unable to resolve 'test'. Resolved ''; remaining name 'test'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
Following is a snippet of code I'm using that deals with retrieving the topic named 'test':
InitialContext _initialContext = null;
try {
_initialContext = new InitialContext(environment);
_initialContext.lookup("ConnectionFactory");
try {
_initialContext.lookup("test");
} catch (NamingException exception) {
LOG.error("", exception);
} catch (NamingException exception) {
LOG.error("A naming exception has occurred!", exception);
} finally {
if (_initialContext != null) {
try {
_initialContext.close();
} catch (NamingException exception) {
LOG.error("A naming exception has occurred!", exception);
The '_initialContext.lookup("test")' invocation is the one causing the mentioned exception.
I used the snippet of code in my test Servlet's constructor, init(...) and service(...) methods. During Cluster start-up it always fails in the constructor or service(...) method. If I use the code in the service(...) method after Cluster start-up if the service(...) method is hit within a couple of seconds after Cluster start-up the exception is thrown, if I wait for a minute or so the exception is not thrown. It almost looks like the JMS Topic becomes available after some time but is not available during start-up. I would think the JMS Connection Factory and Topics should be set-up and available before invoking my test Servlet's constructor and init(...) method. Did I misconfigure something in my Cluster?
I'm using WebLogic Server 10.3. I have a cluster setup with 1 Administration Server and 3 Managed Nodes. I'm using a Node Manager on each of the nodes to start up the various WebLogic Server instances. Additionally I have the following setup:
- 1 Migratable Target (/w User Preferred Server set to node 1 and /w Constrained Candidate Servers set to nodes 1, 2 and 3)
- 1 JMS Server (targeted at the Migratable Target)
- 1 JMS Module (targeted at the Cluster)
- 1 Connection Factory (/w Default Targeting enabled resulting in the Cluster being targeted)
- 1 Subdeployment
- 1 Topic named 'test' (when defining the Subdeployment I'm only able to target it to the JMS Server)
Any help is appreciated!
Thanks,
Jack...

Answer 1

You can configure JMS servers to run anywhere and you can put
          your connection factories anywhere. If multiple JMS servers are
          going to share a database then they need unique table prefixes. You
          don't need any special DDL.
          _sjz.