Randomly ocorrence of “javax.naming.NameNotFoundException: queue not bound”

[vitorcoliveira]

I have one jboss 4.2.3 application consuming from a queue and putting in another queue.  All 3 components running jboss 4.2.3. Deployment of all components were ok. However sometimes my application got this error:

    javax.naming.NameNotFoundException: queue not bound

              at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) ~[jnpserver.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]

              at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) ~[jnpserver.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]

    ...

    at javax.naming.InitialContext.lookup(Unknown Source) ~[na:1.6.0_26]

**or**

    javax.naming.NameNotFoundException: [queue_name] not bound

              at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) ~[jnpserver.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]

              at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) ~[jnpserver.jar:4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)]

    ...

    at javax.naming.InitialContext.lookup(Unknown Source) ~[na:1.6.0_26]

I already verified the `service=JNDIView` on the final queue and everything seems ok. The problem occurs **randomly**. After ~15 minutes the errors stops and my deployment can  process all messages without restart. Despite being random, this error is recurrent.

The jboss of the  destination queue is running on virtual machines. Can this be a performance\load or network problem?

I searched for similar problems and only found occurring at start up of the application. My application is running and errors occurs from time to time randomly 3 to 5 times a day for 15 minutes.

Thank you.

[rafael.alcantara]

Hi Vitor,

         As you asked; theres probably a performance ou network issue causing this. As JMS is statefull; you have to be conected to the destination conection Factory to consume\Produce any messages. 

         Any comunication problem, caused by network issues or stability in destination\origin server qould cause the conection to close and therefore; any atempt to use de Queues deployed in the Destination CF would fail. Normal operations resume after JbossMQ conection manager, reconects.

         You should look for possible overloads or performance problems in the server running the queue ( probably a few minutes before erros start ).  As Jboss 4.2 consoles are very poor; i recomend you install Lambda Probe  ( it´s helped me a lot in performance issues ) to help you investigate

           link to Lambda probe: http://www.lambdaprobe.org/