schedulePeriodForDestinationPurge Provided By A-MQ Broker Repeadedly Logs JMSException To The Same TOPIC
Issue
activemq.xml has a following settings:
schedulePeriodForDestinationPurge=“10000”
gcInactiveDestinations="true"
inactiveTimeoutBeforeGC=“60000"
Although a subscriber keeps subscribing a TOPIC, A-MQ tries to remove the TOPIC every 10 sec, and log the ERROR
ERROR region.RegionBroker: Failed to remove inactive destination Topic: destination=A.4725, subscriptions=1
javax.jms.JMSException: Destination still has an active subscription: topic://A.4725
at org.apache.activemq.broker.region.AbstractRegion.removeDestination(AbstractRegion.java:271)
at org.apache.activemq.broker.region.RegionBroker.removeDestination(RegionBroker.java:354)
at org.apache.activemq.broker.BrokerFilter.removeDestination(BrokerFilter.java:179)
at org.apache.activemq.broker.BrokerFilter.removeDestination(BrokerFilter.java:179)
at org.apache.activemq.broker.BrokerFilter.removeDestination(BrokerFilter.java:179)
at org.apache.activemq.broker.region.RegionBroker.purgeInactiveDestinations(RegionBroker.java:897)
at org.apache.activemq.broker.region.RegionBroker$1.run(RegionBroker.java:118)
at org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Environment
- Red Hat JBoss A-MQ
- 6.2.1
- 6.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.