The SessionConstants type exposes the following members.
Fields
| Name | Description | |
|---|---|---|
| AUTO_ACKNOWLEDGE |
With this acknowledgment mode, the session automatically acknowledges
a client's receipt of a message either when the session has successfully
returned from a call to receive or when the message
listener the session has called to process the message successfully
returns.
| |
| CLIENT_ACKNOWLEDGE |
With this acknowledgment mode, the client acknowledges a consumed
message by calling the message's acknowledge method.
Acknowledging a consumed message acknowledges all messages that the
session has consumed.
When client acknowledgment mode is used, a client may build up a large number of unacknowledged messages while attempting to process them. A JMS provider should provide administrators with a way to limit client overrun so that clients are not driven to resource exhaustion and ensuing failure when some resource they are using is temporarily blocked. | |
| DUPS_OK_ACKNOWLEDGE |
This acknowledgment mode instructs the session to lazily acknowledge
the delivery of messages. This is likely to result in the delivery of
some duplicate messages if the JMS provider fails, so it should only be
used by consumers that can tolerate duplicate messages. Use of this
mode can reduce session overhead by minimizing the work the
session does to prevent duplicates.
| |
| SESSION_TRANSACTED |
This value is returned from the method
getAcknowledgeMode if the session is transacted.
If a Session is transacted, the acknowledgement mode
is ignored.
|