0 Replies Latest reply on Dec 19, 2005 3:02 AM by Evyatar Kafkafy

    "queue not bound" after long operation (40 hours)

    Evyatar Kafkafy Newbie

      Hi all

      I use JBoss 3.2.6 on Windows 2003, JMS persisted to Oracle.
      JBoss runs OK for several hours. Then left running for the weekend but there are almost no requests for about 38 hours.
      Then after 38 hours there is a request (a method invocation of an EJB. I use CMT) and the code inside it tries to lookup a queue through the JNDI and I get

      javax.naming.NameNotFoundException: queue not bound
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:490)
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:498)
      at org.jnp.server.NamingServer.getObject(NamingServer.java:504)
      at org.jnp.server.NamingServer.lookup(NamingServer.java:248)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:530)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
      at javax.naming.InitialContext.lookup(InitialContext.java:347)
      ... (my code that calls lookup)

      The same code works fine for several months now (but not tested in scenarios of long operation).
      A call to JNDI lookup of the Connection Factory, just a few lines before, succeeded (well, I did not get an exception).

      After that, every lookup of that queue gave the same exception. Restarting JBoss of course fixed that.

      My direction are to something that is cached for several hours (JVM, JBoss, JNP, or in my usage of JNDI).

      Anyone has a clue? Seen this before?