Yup, you're right. The 'JMSXGroupSeq' is not required. I looked at my test
code, which had it set and incorrectly assumed it was required.
So I commented JMSXGroupSeq out of my code, ran the test and it all still
seems to work fine for me. I have two consumers up and running when the
producer sends out the CHECKING and SAVINGS messages. AMQ splits up the
message streams nicely. That is, one consumer gets all the CHECKING messages
and the other gets all the SAVINGS messages. I am using AMQ 5.1 w/async
consumers.
Here's the segment of code that produces the messages.
String s2 = new Date().toString();
for(int i=0; i<20; i++){
msg = session.createTextMessage();
msg.setText("Ping Message[" + i + "] " + s2);
msg.setStringProperty("JMSXGroupID",CHECKING);
//msg.setIntProperty("JMSXGroupSeq", i+1);
qSender.send(msg);
msg = session.createTextMessage();
msg.setText("Ping Message[" + i + "] " + s2);
msg.setStringProperty("JMSXGroupID",SAVINGS);
//msg.setIntProperty("JMSXGroupSeq", i+1);
qSender.send(msg);
}
Joe
www.ttmsolutions.com
Matt23 wrote:
>
> No, I wasn't setting the JMSXGroupSeq as the docs only state to set this
> to 0 if you want to close the message group. I modified my test to set
> this (starting at 1), but it still doesn't work. Is this property supposed
> to be set?
>
> Thanks,
> Matt
>
--
View this message in context:
http://www.nabble.com/Message-groups-not-working-when-consuming-existing-messages-tp18445237p18448814.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
