Hi Wolf-Dieter,

I am runnning JBoss with the default HSQL DB for JMS. I realise that this is not the best way to deal with the messaging inside JBoss and I am busy moving to another dbms.

I have a standard 3 environment setup in which I have a development environment, a user acceptance testing environment and a production environment. I have the same JBoss configuration in all 3 environments, but I am only experiencing this problem in the one environment. I have checked that there is available disk capacity and memory on that machine and the usage is more or less the same as the other 2 environments.

I have 2 MDBeans that perform different functions based on the content of the message posted to the topic. So this is 2 seperate MDBean classes, both configured with activation config as:

   activationConfig = {

         @ActivationConfigProperty(propertyName = "destinationType",propertyValue = "javax.jms.Topic"),

         @ActivationConfigProperty(propertyName = "destination",propertyValue = "topic/Application_Events"),

         @ActivationConfigProperty(propertyName = "useDLQ",propertyValue = "true"),

         @ActivationConfigProperty(propertyName = "messageSelector", propertyValue = "type = 'TriggerEvent'"),

         @ActivationConfigProperty(propertyName = "DLQJNDIName",propertyValue = "queue/DLQ")

      },

Both beans are configured with this activation config, and after start up, both receive and process messages sent to the topic. However after some time goes by ( could be weeks) bean 2 stops receiving messages and a restart is required of the container.