Hello,
It seems I am missing yet another setting to completely disable producer
flow control. I am using virtual topics and despite plenty of temp space
being availble, it seems the dispatch from the topic to the consumer queue
is being blocked:
2013-07-22 14:13:00,601 | INFO | TopicSubscription:
consumer=ID:dpr-app1-38753-1374486415369-1:25:1:1, destinations=49,
dispatched=1, delivered=237, matched=0, discarded=0: Pending message cursor
[org.apache.activemq.broker.region.cursors.FilePendingMessageCursor@10dce3f6]
is full, temp usage (1%) or memory usage (147%) limit reached, blocking
message add() pending the release of resources. |
org.apache.activemq.broker.region.TopicSubscription | ActiveMQ
Broker[DPR_APP1_PROD] Scheduler
My destination policies look like this:
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" producerFlowControl="false">
<pendingSubscriberPolicy>
<fileCursor/>
</pendingSubscriberPolicy>
</policyEntry>
<policyEntry queue=">" producerFlowControl="false">
<pendingQueuePolicy>
<fileQueueCursor/>
</pendingQueuePolicy>
</policyEntry>
<policyEntry tempQueue="true" producerFlowControl="false">
<pendingQueuePolicy>
<fileQueueCursor/>
</pendingQueuePolicy>
</policyEntry>
<policyEntry tempTopic="true" producerFlowControl="false">
<pendingSubscriberPolicy>
<fileCursor/>
</pendingSubscriberPolicy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
As there is still plenty of temp space left (1% of 5GB) I would not expect
to see any blocking going on?
As a side question: Why might be "memory usage" at 147% while temp usage is
at 1%?
Thanks!
Ralf
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumer-queues-for-virtual-topics-do-not-receive-messages-tp4669577.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
