Hi Roger, you can always explicitly "close" a message group
http://activemq.apache.org/message-groups.html#MessageGroups-ClosingaMessageGroup Timeout also makes sense, can you log it in Jira, so it can be considered as an enhancement in future implementations. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Mon, Oct 24, 2011 at 11:35 PM, Roger Fischer < roger.fisc...@abb.ventyx.com> wrote: > Hello, > > has it been considered to add a timeout to JMSXGroupID, after which the > routing to the consumer would be deleted? > > We have a scenario where two related messages (ie. same JMSXGroupID) arrive > in short succession, requiring the second message to be deliver to the same > consumer as the first. But then there may be no other related message for a > long time (many minutes). When finally the next message with the same > JMSXGroupID arrives, it can be load balanced as if there had been no > preceding messages with the same JMSXGroupID. > > Thanks... > > Roger > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/JMSXGroupID-timeout-tp3934661p3934661.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
