... thanks for the suggestions - message groups do sound like a plausible solution.
I am not interested in assigning a group of messages to particular sessions indefinately as the groups will be small and many. Once the high priority message has been dequeued with all related messages (at that point in time) that batch work is done and time to move onto the next high priority message. CorrelationID's also look promising. High do you create a message selector string to select by comparisons to other messages e.g. CorrelationID and Priorty? I can see how this is done in the JMS Message javadoc API. All documentation seems to relate to literal comparisons Thanks again. James.Strachan wrote: > > On 10/10/2007, Terrk K <[EMAIL PROTECTED]> wrote: >> >> I cannot find enough documentation on message selectors but have many >> questions. >> >> Message selectors are more like fliters right? If so, what is the >> underlying >> selection policy of the broker? Age, priority, moon phases? > > The selector describes the filter. > > See the "Message Selectors" section... > http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Message.html > > > As Joe said, Message Groups could be what you need to process groups > of messages by the same consumer; maybe with a selector to filter > 'high priority' messages > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source SOA > http://open.iona.com > > -- View this message in context: http://www.nabble.com/message-selectors-tf4603950s2354.html#a13155279 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
