Throttling consumer traffic in clustered JMS queue

[theone4ever]

Hi all,

We configed hornetq in cluster mode in EAP6.0 (jboss as 7.1.1 i think), and want to throttling the consumer traffic by set max session and consumerMaxRate, see annotation on MDB below, and we have two machines each running one jboss instance in cluster env, so but we expect to consume 10 msg per sec. THis works as long as we only config max session as 1. But if we set max session as 2 (of course we set consumer max rate as 5), then we see about 20 msg consumed per sec, not 10. Does anyone know what is the trick there?

@ActivationConfigProperty(propertyName = "maxSession", propertyValue = "1"),

@ActivationConfigProperty(propertyName = "consumerMaxRate", propertyValue = "10"

Thank you.

[ataylor]

ive just tried this and it worked fine, altho with a single node, what is your topology and where are the MDB's deployed?

[theone4ever]

Hi Andy,

Thank you for quick reply. Our MDB and together with message producer are packaged in the same ear, then deployed on jboss running with standalone-ha.xml some some minor modification. Then two machine running such jboss in the same subnet. Also when when MDB consumes the msg, it ends up a HTTP request towards an external server node. Then we use wireshark IO graphs to monitor # of HTTP requests every sec, and find that depends on number of max session we configed, the totally # of request is different, also result of maxSession x consumerMaxRate is always 10.

Thank you.

[ataylor]

ok, so thats 4 consumers then, 2 per node so I would expect 20 msgs per sec, which is what you are getting

[theone4ever]

Ok, i see. 2 (servers) x 2 (maxSession) x 5 (consumerMaxRate), then i get 20. But what strange is when i config max session as 1, i only get 10 req/sec, it should be 2 (servers) x 1 (max session) x 10 (consumerMaxRate), then i should get 20 too, right?

[ataylor]

yes you should, however with such a low number of consumers maybe its just the speed messages are being distributed between the nodes, tbh its hard to say, remember its a throttle rate not a throughput rate, as you ramp up the consumers it should balance out.