hank you very much. I have updated to version 5.3.2. Now I'll monitor the situation. I'll also check via JMX the subscriber list. But the only subscriber are the MDBs and all the MDBs are defined as follow:
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"), @ActivationConfigProperty(propertyName = "clientId", propertyValue="TOPIC-RECEIVER"), @ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue="Durable"), @ActivationConfigProperty(propertyName = "subscriptionName", propertyValue="TopicReceiver") rajdavies wrote: > > Firstly - upgrade to 5.3.2 - there are some minor bug fixes - but also > performance enhancements. I would check that you don't have a durable > subscriber in your system that was active at some point - but is no loner > - you can use JMX to do this > -- View this message in context: http://old.nabble.com/KahaDB-and-TOPIC-problems-%28with-MDB-DURABLE-SUBSCRIPTION%29-tp29053774p29073418.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
