I have been using AMQ 5.8 configured for virtual topics for about 18 months with minimum issues. Recently I have upgraded the AMQ to 5.12 and since then, each ~24 hours I am experiencing the situation when messages that are posted to a virtual topic are not dispatched to consumers. The AMQ monitoring console indicates that number of pending messages are increased, however no messages are actually dequeued so active consumers are not getting any messages. If I click on 'Browse' then I don't see any messages even when number of pending messages are around 50,000. The are no errors reported in the AMQ logs nor any problems reported by the client. If I stop the AMQ, remove the content from 'data' folder , start the AMQ then everything is working for about one day and then I am experiencing the exact problem again. Consumers are not using any selector.
Has anybody experienced the same issue? Any input appreciated. I am including my configuration. thank you <broker xmlns="http://activemq.apache.org/schema/core" brokerName="event-broker" dataDirectory="${activemq.data}"> <destinationPolicy> <policyMap> <policyEntries> <policyEntry topic=">" producerFlowControl="true" maxPageSize="40" maxBrowsePageSize="80" durableTopicPrefetch="5" topicPrefetch="5"> <pendingMessageLimitStrategy> <constantPendingMessageLimitStrategy limit="10"/> </pendingMessageLimitStrategy> </policyEntry> <policyEntry queue=">" producerFlowControl="true" memoryLimit="30mb" maxPageSize="40" maxBrowsePageSize="80"> <deadLetterStrategy> <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" /> </deadLetterStrategy> </policyEntry> </policyEntries> </policyMap> </destinationPolicy> <destinationInterceptors> <virtualDestinationInterceptor> <virtualDestinations> <virtualTopic name="VirtualTopic.Event" prefix="Consumer.*." selectorAware="true"/> </virtualDestinations> </virtualDestinationInterceptor> </destinationInterceptors> <managementContext> <managementContext createConnector="true"/> </managementContext> <persistenceAdapter> <kahaDB directory="${activemq.data}/kahadb"/> </persistenceAdapter> <systemUsage> <systemUsage> <memoryUsage> <memoryUsage percentOfJvmHeap="70" /> </memoryUsage> <storeUsage> <storeUsage limit="300 gb"/> </storeUsage> <tempUsage> <tempUsage limit="50 gb"/> </tempUsage> </systemUsage> </systemUsage> <transportConnectors> <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/> </transportConnectors> <shutdownHooks> <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" /> </shutdownHooks> </broker> <import resource="jetty.xml"/> <import resource="camel.xml"/> </beans> -- View this message in context: http://activemq.2283324.n4.nabble.com/Messages-are-not-dispatched-to-consumers-of-Virtual-Topic-tp4703876.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.