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.
