Modifier and Type | Field and Description |
---|---|
static int |
INDIVIDUAL_ACKNOWLEDGE
With this acknowledgement mode, the client acknowledges a consumed message by calling the
message's
acknowledge method. |
static int |
PRE_ACKNOWLEDGE
Acknowledgement mode to instruct the session that there's no need to acknowledge the delivery
of messages, since they are acknowledged by the JMS Extender before they are sent.
|
AUTO_ACKNOWLEDGE, CLIENT_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE, SESSION_TRANSACTED
close, commit, createBrowser, createBrowser, createBytesMessage, createConsumer, createConsumer, createConsumer, createDurableConsumer, createDurableConsumer, createDurableSubscriber, createDurableSubscriber, createMapMessage, createMessage, createObjectMessage, createObjectMessage, createProducer, createQueue, createSharedConsumer, createSharedConsumer, createSharedDurableConsumer, createSharedDurableConsumer, createStreamMessage, createTemporaryQueue, createTemporaryTopic, createTextMessage, createTextMessage, createTopic, getAcknowledgeMode, getMessageListener, getTransacted, recover, rollback, run, setMessageListener, unsubscribe
static final int PRE_ACKNOWLEDGE
Use of this mode can greatly improve performance and reduce session overhead, but introduces the risk of receiving duplicates for every message received. It must be used only when messaged duplication is not an issue.
static final int INDIVIDUAL_ACKNOWLEDGE
acknowledge
method.
Differently from Session.CLIENT_ACKNOWLEDGE
, in this mode acknowledging a consumed message
acknowledges only that single message. Any other message that the session has consumed remain
unacknowledged.