A client uses a QueueReceiver object to receive messages that
have been delivered to a queue.
Although it is possible to have multiple QueueReceivers
for the same queue, the JMS API does not define how messages are
distributed between the QueueReceivers.
If a QueueReceiver specifies a message selector, the
messages that are not selected remain on the queue. By definition, a message
selector allows a QueueReceiver to skip messages. This
means that when the skipped messages are eventually read, the total ordering
of the reads does not retain the partial order defined by each message
producer. Only QueueReceivers without a message selector
will read messages in message producer order.
Creating a MessageConsumer provides the same features as
creating a QueueReceiver. A MessageConsumer object is
recommended for creating new code. The QueueReceiver is
provided to support existing code.
See Also: javax.jms.Session.createConsumer(DestinationString)
See Also: javax.jms.Session.createConsumer(Destination)
See Also: javax.jms.QueueSession.createReceiver(QueueString)
See Also: javax.jms.QueueSession.createReceiver(Queue)
See Also: javax.jms.MessageConsumer |