Hello, I noticed that declaring ring queue with just max-queue-count parameter prevents me sending messages with nonempty content:
# qpid-config add queue Test2 --max-queue-count=100 --limit-policy=ring # ./spout -c 100 --content "a" Test2 2011-10-05 10:53:18 warning Exception received from broker: resource-limit-exceeded: resource-limit-exceeded: resource-limit-exceeded: Policy exceeded on Test2, policy: size: unlimited; count: max=100, current=0; type=ring (qpid/broker/QueuePolicy.cpp:87) [caused by 3 \x00:\x00] 2011-10-05 10:53:18 warning Exception received from broker: resource-limit-exceeded: resource-limit-exceeded: resource-limit-exceeded: Policy exceeded on Test2, policy: size: unlimited; count: max=100, current=0; type=ring (qpid/broker/QueuePolicy.cpp:87) [caused by 1 \x00:\x00] Failed to connect (reconnect disabled) # ./spout -c 100 Test2 # While when I define also max-queue-size, nonempty messages are accepted: # qpid-config del queue Test2 --force # qpid-config add queue Test2 --max-queue-count=100 --max-queue-size=100000 --limit-policy=ring # ./spout -c 100 --content "a" Test2 # Debugging the failing case, qpidd really rejects the messages due to size: 2011-10-05 10:53:18 debug Message too large for ring queue Test2 [size: unlimited; count: max=100, current=0; type=ring] : message size = 1 bytes: max queue size = 0 bytes Is that intentional or not? As I would assume not specifying max-queue-* parameter means I don't want to restrict the queue in that manner.. I will create JIRA and (try to) propose a patch for it if you see it as a bug as well. Kind regards, Pavel --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org
