Is your issue that certain consumers become too slow? If so, you can always set the JMSXGroupSeq header to −1 to force a new consumer (maybe set this periodically or after a certain number of messages)...
here is a good article that discusses this a bit... http://scottcranton.blogspot.com/2010/09/activemq-message-groups.html Either way, I'd think this could be a feature of the message groups. Basically let you specify a frequency (either elapsed time or message count) to force a new consumer for a group. Would serve to better randomize the load across consumers to protect against slow consumers, etc... Martin C. wrote: > > Hi, > > we currently use message groups to ensure ordered delivery of messages > within a given group. As noted on the documentation for message > groups, this often does not scale very well with variable consumer > counts, as in this case the oldest consumers will hog all message > groups. > > In our use-case, and I suppose this might apply to others as well, we > simply don't care which consumer consumes which message, but only, > that the next message from the same message group is not consumed > before the first has been processed. So my idea would be to add a > configuration option, that a consumer will release the message group > directly after consuming its current message, releasing the message > group for re-distribution to other brokers. > > Would something like this be possible / do I overlook some downside of > this approach? > > Best regards, > Martin > -- View this message in context: http://activemq.2283324.n4.nabble.com/Fwd-Message-groups-enhancement-feature-request-tp3635293p3637432.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
