public interface QueueReceiver
A client uses a QueueReceiver
object to receive messages that have been delivered to a queue.
Although it is possible to have multiple QueueReceiver
s for the same queue, the JMS API does not define how messages are distributed between the QueueReceiver
s.
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 QueueReceiver
s 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.
Session.createConsumer(Destination, String)
, Session.createConsumer(Destination)
, QueueSession.createReceiver(Queue, String)
, QueueSession.createReceiver(Queue)
, MessageConsumer
Queue
getQueue()
Queue
associated with this queue receiver. getQueue
Queue getQueue() throws JMSException
Queue
associated with this queue receiver.
Queue
JMSException
- if the JMS provider fails to get the queue for this queue receiver due to some internal error.
Copyright 2007 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.
Scripting on this page tracks web page traffic, but does not change the content in any way.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4