0 Replies Latest reply on Nov 7, 2011 7:39 AM by Deepak Pandey

    javax.naming.NameNotFoundException: <queue_name> not bound

    Deepak Pandey Newbie

      We have a adapter that uses Java Messaging Service (JMS) APIs. When this custom adapter is invoked, a JMS messsage is sent by our core Engine to a JMS Queue. A Message Driven Bean (MDB) listening to this JMS Queue picks up the message, consumes it and exeutes the adapter. Most of the time, this adapter works fine. However, sometimes[occurs once in a while] it stops working and throws an error. Below is the stack trace:

       

      (041):Error looking up destination <jms/BLAdapterQueue> for provider <jboss>.

      ....

      ....

      Caused by: javax.naming.NameNotFoundException: BLAdapterQueue not bound

          at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)

          at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)

          at org.jnp.server.NamingServer.getObject(NamingServer.java:785)

          at org.jnp.server.NamingServer.lookup(NamingServer.java:443)

          at org.jnp.server.NamingServer.lookup(NamingServer.java:399)

          at sun.reflect.GeneratedMethodAccessor392.invoke(Unknown Source)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

          at java.lang.reflect.Method.invoke(Method.java:597)

          at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)

          at sun.rmi.transport.Transport$1.run(Transport.java:159)

          at java.security.AccessController.doPrivileged(Native Method)

          at sun.rmi.transport.Transport.serviceCall(Transport.java:155)

          at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)

          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)

          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

          at java.lang.Thread.run(Thread.java:619)

          at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)

          at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)

          at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)

          at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)

          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)

          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)

          at javax.naming.InitialContext.lookup(InitialContext.java:392)

         

      Definition of this queue is given below:

      ===============

      <mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=BLAdapterQueue" xmbean-dd="xmdesc/Queue-xmbean.xml">

              <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>

              <depends>jboss.messaging:service=PostOffice</depends>

              <attribute name="JNDIName">jms/BLAdapterQueue</attribute>

      ===============

       

      Can you please help me understand, in which scenario this kind of issue occurs?