Session Modes available for Session objects
| Member 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. |
| 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. |
| NO_ACKNOWLEDGE | No acknowledge is required. Messages sent to a NO_ACKNOWLEDGE session are immediately deleted from the server. Messages received in this mode are not recovered, and as a result messages may be lost and/or a duplicate message may be delivered if an initial attempt to deliver a message fails. This mode is supported for applications that do not require the quality of service provided by session acknowledge, and that do not want to incur the associated overhead.You should avoid using this mode if your application cannot handle lost or duplicate messages. |
| SESSION_TRANSACTED | This value is returned from the method AcknowledgeMode if the session is transacted. If a ISession is transacted, the acknowledgement mode is ignored. |
Namespace: WebLogic.Messaging
Assembly: WebLogic.Messaging (in WebLogic.Messaging.dll)