I'm hanging on a JNDI lookup (highlighted below). Are there any simple reasons why this might happen in a lookup? I have not seen JNDI calls hang like that in JBoss.

jndiContext = new InitialContext();
System.out.println("Messaging: lookup ConnectionFactory");
queueConnectionFactory = (QueueConnectionFactory)
jndiContext.lookup("ConnectionFactory");
System.out.println("Messaging: Creating QueueConnection");
queueConnection = queueConnectionFactory.createQueueConnection( );
queueConnection.start( );

FYI, I have two services defined as MBeans. When the class that uses this code is called from one service, the lookup does not hang, but calls coming from the second service ('BPMLEngine') do hang. The 'BPMLEngine' service depends on JMS, I don't think that would effect JNDI lookups.





<!-- Client Startup service -->



<!-- Engine startup service-->

jboss.mq.destination:service=Queue,name=testQueue