When isTransacted is set to false, the session is non-transacted. In this case, the argument acknowledgeMode specifies how messages are acknowledged. Possible values appear in the table below:
Acknowledgement Mode
Meaning
Session.AUTO_ACKNOWLEDGE
Session automatically acknowledges a client's receipt of a message.
Session.CLIENT_ACKNOWLDEGE
Client acknowledges a message by calling its acknowledge() method. Acknowledging a message acknowledges all messages so far consumed in this session, up to and including the message being acknowledged.
Session.DUPS_OK_ACKNOWLEDGE
Session slowly acknowledges delivery of messages. It is most likely some duplicate messages will arrive if the JMS provider fails. Therefore, use this mode only with consumers that can tolerate duplicate messages.
Sessions retain messages until they are acknowledged. If the acknowledgement mode is Session.AUTO_ACKNOWLEDGE, the session retains the message until all consumers have received it. If the acknowledgement mode is Session.CLIENT_ACKNOWLDEGE, the message must be explicitly acknowledged with the acknowledge() method. Another way to acknowledgement is Session.DUPS_OK_ACKNOWLEDGE. This mode facilitates the session's task of filtering out duplicates. Use it only with a client that can tolerate duplicate messages.
Wiki Content Tree
Your Feedback Needed!
We need your help to improve this wiki site. If you have any suggestions or corrections, write to us at techw@gigaspaces.com. Please provide a link to the wiki page you are referring to.
Previous release
Add Comment