Hello, We are investigating using message groups as a technique to insure "in order" processing of various IDs. In the past (2010), I have found posts mentioning that more than 1024 message groups will trigger an overflow for the default implementations. http://scott.cranton.com/2010/09/activemq-message-groups.html
I can't find anything specific that is newer on the topic except "there could be a massive number of individual message groups we use hash buckets rather than the actual JMSXGroupID string." The word "massive" is ambiguous and relative. Say we are using social security numbers as our IDs and have millions of customers. Is 2 million records going to be supportable by default? I also understand hashmaps pretty well. I don't understand what is meant by using "hash buckets" rather than the JMSXGroupID string. In a usual hashmap implementation a bucket would store a certain number of hashed keys. What does it matter if the key is stored or a hashed key is stored, and what is the relation to the bucket? Thanks in advance. Derek -- View this message in context: http://activemq.2283324.n4.nabble.com/Message-Group-Limitations-how-many-simulataneous-groups-are-supported-tp4706412.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
