1 2 Previous Next 16 Replies Latest reply on Jun 28, 2004 8:57 PM by Adrian Brock

    MDB ACTIVE but stops consuming

    amresh Newbie

      We are using
      Jboss 3.2.1 on Linux
      JDBC2 persistence manager persisting in Sybase database

      We have come across a strange problem. In last few months this is the second occurence where a MDB consuming messages from a PERSISTENT queue suddenly stops to do so. The MDB (with a max pool size of 1) is seen to be active in the JMX-console. New messages get added to the queue with out any problem.

      There are no exceptions in the processing of the previous message or otherwise. During both the occurences we restarted the server to resolve the problem (we should have tried deactivating and activating the MDB before restart).

      Thread dump taken before the restart does not suggest any locking/contention.

      "Connection Consumer for dest QUEUE.test" prio=1 tid=0x0x6069f430 nid=0x2111 in Object.wait() [6147b000..6147b840]
      at java.lang.Object.wait(Native Method)
      - waiting on <0x4e781818> (a EDU.oswego.cs.dl.util.concurrent.LinkedNode)
      at java.lang.Object.wait(Object.java:426)
      at EDU.oswego.cs.dl.util.concurrent.SynchronousChannel.put(SynchronousChannel.java:152)
      - locked <0x4e781818> (a EDU.oswego.cs.dl.util.concurrent.LinkedNode)
      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$WaitWhenBlocked.blockedAction(PooledExecutor.java:778)
      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor.execute(PooledExecutor.java:877)
      at org.jboss.jms.asf.StdServerSession.start(StdServerSession.java:357)
      at org.jboss.mq.SpyConnectionConsumer.run(SpyConnectionConsumer.java:240)
      at java.lang.Thread.run(Thread.java:536)

      Any help with regards to this would be appreciated.



        1 2 Previous Next