io.mats3.matssocket.impl

Class ClusterStoreAndForward_SQL

java.lang.Object

io.mats3.matssocket.impl.ClusterStoreAndForward_SQL

All Implemented Interfaces:

ClusterStoreAndForward

public class ClusterStoreAndForward_SQL
extends java.lang.Object
implements ClusterStoreAndForward

An implementation of CSAF relying on a shared SQL database to store the necessary information in a cluster setting.

NOTE: This CSAF implementation expects that the database tables are in place. A tool is provided for this, using Flyway: ClusterStoreAndForward_SQL_DbMigrations.

NOTE: There is heavy reliance on the Mats' MatsFactory.ContextLocal feature whereby the current Mats StageProcessor-contextual SQL Connection is available using the MatsFactory.ContextLocal.getAttribute(Class, String...) method. This since several of the methods on this interface will be invoked within a Mats initiation or Stage process lambda, and thus participating in the transactional demarcation established there is vital to achieve the guaranteed delivery and exactly-once delivery semantics.

Nested Class Summary

Nested classes/interfaces inherited from interface io.mats3.matssocket.ClusterStoreAndForward

ClusterStoreAndForward.CurrentNode, ClusterStoreAndForward.DataAccessException, ClusterStoreAndForward.MessageIdAlreadyExistsException, ClusterStoreAndForward.RequestCorrelation, ClusterStoreAndForward.SimpleCurrentNode, ClusterStoreAndForward.SimpleRequestCorrelation, ClusterStoreAndForward.SimpleStoredInMessage, ClusterStoreAndForward.SimpleStoredOutMessage, ClusterStoreAndForward.StoredInMessage, ClusterStoreAndForward.StoredOutMessage, ClusterStoreAndForward.WrongUserException

Constructor Summary

Constructors

Modifier	Constructor and Description
protected	ClusterStoreAndForward_SQL(javax.sql.DataSource dataSource, java.lang.String nodename, java.time.Clock clock)

Method Summary

Modifier and Type	Method and Description
void	boot() Start the ClusterStoreAndForward, perform DB preparations and migrations.
void	closeSession(java.lang.String matsSocketSessionId) Invoked when the client explicitly tells us that he closed this session, CLOSE_SESSION.
static ClusterStoreAndForward_SQL	create(javax.sql.DataSource dataSource, java.lang.String nodename)
void	deleteMessageIdsFromInbox(java.lang.String matsSocketSessionId, java.util.Collection<java.lang.String> clientMessageIds) Deletes the incoming message Ids, as we've established that the client will never try to send this particular message again.
void	deregisterSessionFromThisNode(java.lang.String matsSocketSessionId, java.lang.String connectionId) Deregisters a Session home when a WebSocket is closed.
java.util.Optional<ClusterStoreAndForward.RequestCorrelation>	getAndDeleteRequestCorrelation(java.lang.String matsSocketSessionId, java.lang.String serverMessageId)
java.util.Optional<ClusterStoreAndForward.CurrentNode>	getCurrentRegisteredNodeForSession(java.lang.String matsSocketSessionId)
ClusterStoreAndForward.StoredInMessage	getMessageFromInbox(java.lang.String matsSocketSessionId, java.lang.String clientMessageId)
java.util.List<ClusterStoreAndForward.StoredOutMessage>	getMessagesFromOutbox(java.lang.String matsSocketSessionId, int maxNumberOfMessages) Fetch a set of messages, up to 'maxNumberOfMessages' - but do not include messages that have been attempted delivered already (marked with ClusterStoreAndForward.outboxMessagesAttemptedDelivery(String, Collection)).
java.util.List<MatsSocketServer.MatsSocketSessionDto>	getSessions(boolean onlyActive, java.lang.String userId, java.lang.String appName, java.lang.String appVersionAtOrAbove) Direct implementation of MatsSocketServer.getMatsSocketSessions(boolean, String, String, String) - go read there for semantics.
int	getSessionsCount(boolean onlyActive, java.lang.String userId, java.lang.String appName, java.lang.String appVersionAtOrAbove) Direct implementation of MatsSocketServer.getMatsSocketSessionsCount(boolean, String, String, String) - go read there for semantics.
boolean	isSessionExists(java.lang.String matsSocketSessionId)
void	notifySessionLiveliness(java.util.Collection<java.lang.String> matsSocketSessionIds) Shall be invoked on some kind of schedule (e.g.
void	outboxMessagesAttemptedDelivery(java.lang.String matsSocketSessionId, java.util.Collection<java.lang.String> serverMessageIds) Marks the specified messages as attempted delivered and notches the ClusterStoreAndForward.StoredOutMessage.getDeliveryCount() one up.
void	outboxMessagesComplete(java.lang.String matsSocketSessionId, java.util.Collection<java.lang.String> serverMessageIds) States that the messages are delivered.
void	outboxMessagesDeadLetterQueue(java.lang.String matsSocketSessionId, java.util.Collection<java.lang.String> serverMessageIds) States that the messages overran the accepted number of delivery attempts.
void	outboxMessagesUnmarkAttemptedDelivery(java.lang.String matsSocketSessionId) When this method is invoked, ClusterStoreAndForward.getMessagesFromOutbox(String, int) will again return messages that has previously been marked as attempted delivered with ClusterStoreAndForward.outboxMessagesAttemptedDelivery(String, Collection).
long	registerSessionAtThisNode(java.lang.String matsSocketSessionId, java.lang.String userId, java.lang.String connectionId, java.lang.String clientLibAndVersions, java.lang.String appName, java.lang.String appVersion) Registers a Session home to this node - only one node can ever be home, so any old is deleted.
int	scavengeSessionRemnants() Shall be invoked on some kind of schedule (e.g.
void	storeMessageIdInInbox(java.lang.String matsSocketSessionId, java.lang.String clientMessageId) Stores the incoming message Id, to avoid double delivery.
java.util.Optional<ClusterStoreAndForward.CurrentNode>	storeMessageInOutbox(java.lang.String matsSocketSessionId, java.lang.String serverMessageId, java.lang.String clientMessageId, java.lang.String traceId, MatsSocketServer.MessageType type, java.lang.Long requestTimestamp, java.lang.String envelope, java.lang.String messageJson, byte[] messageBinary) Stores the message for the Session, returning the nodename for the node holding the session, if any.
void	storeRequestCorrelation(java.lang.String matsSocketSessionId, java.lang.String serverMessageId, long requestTimestamp, java.lang.String replyTerminatorId, java.lang.String correlationString, byte[] correlationBinary)
java.util.Collection<java.lang.String>	timeoutSessions(long notLiveSinceTimestamp) Shall be invoked on some kind of schedule (e.g.
void	updateMessageInInbox(java.lang.String matsSocketSessionId, java.lang.String clientMessageId, java.lang.String envelopeWithMessage, byte[] messageBinary) Stores the resulting message (envelope and binary), so that if the incoming messages comes again (based on ClusterStoreAndForward.storeMessageIdInInbox(String, String) throwing ClusterStoreAndForward.MessageIdAlreadyExistsException), the result from the previous processing can be returned right away.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ClusterStoreAndForward_SQL

protected ClusterStoreAndForward_SQL(javax.sql.DataSource dataSource,
                                     java.lang.String nodename,
                                     java.time.Clock clock)

Method Detail

create

public static ClusterStoreAndForward_SQL create(javax.sql.DataSource dataSource,
                                                java.lang.String nodename)

boot

public void boot()

Description copied from interface: ClusterStoreAndForward

Start the ClusterStoreAndForward, perform DB preparations and migrations.

Specified by:

boot in interface ClusterStoreAndForward

registerSessionAtThisNode

public long registerSessionAtThisNode(java.lang.String matsSocketSessionId,
                                      java.lang.String userId,
                                      java.lang.String connectionId,
                                      java.lang.String clientLibAndVersions,
                                      java.lang.String appName,
                                      java.lang.String appVersion)
                               throws ClusterStoreAndForward.WrongUserException,
                                      ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Registers a Session home to this node - only one node can ever be home, so any old is deleted. When "re-registering" a session, it is asserted that the provided 'userId' is the same UserId as originally registered - a ClusterStoreAndForward.WrongUserException is thrown if this does not match.

Specified by:

registerSessionAtThisNode in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the SessionId for this connection.

userId - the UserId, as provided by AuthenticationPlugin, that own this MatsSocketSessionId

connectionId - an id that is unique for this specific WebSocket Session (i.e. TCP Connection), so that if it closes, a new registration will not be deregistered by the old MatsSocketSession realizing that it is closed and then invoking ClusterStoreAndForward.deregisterSessionFromThisNode(String, String)

clientLibAndVersions - the Client Library and Versions + runtime information for the Client.

appName - the AppName of the accessing Client app

appVersion - the AppVersion of the accessing Client app

Returns:

the created timestamp - which is either "now" if this is the first register, or if it a "reconnect", when this MatsSocketSession was initially created

Throws:

ClusterStoreAndForward.WrongUserException - if the userId provided does not match the original userId that created the session.

ClusterStoreAndForward.DataAccessException - if problems with underlying data store.

deregisterSessionFromThisNode

public void deregisterSessionFromThisNode(java.lang.String matsSocketSessionId,
                                          java.lang.String connectionId)
                                   throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Deregisters a Session home when a WebSocket is closed. This node's nodename and this WebSocket Session's ConnectionId is taken into account, so that if it has changed async, it will not deregister a new session home (which can potentially be on the same node the 'connectionId' parameter).

Specified by:

deregisterSessionFromThisNode in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the MatsSocketSessionId for which to deregister the specific WebSocket Session's ConnectionId.

connectionId - an id that is unique for this specific WebSocket Session (i.e. TCP Connection), so that if it closes, a new registration will not be deregistered by the old MatsSocketSession realizing that it is closed and then invoking ClusterStoreAndForward.deregisterSessionFromThisNode(String, String)

Throws:

ClusterStoreAndForward.DataAccessException

getCurrentRegisteredNodeForSession

public java.util.Optional<ClusterStoreAndForward.CurrentNode> getCurrentRegisteredNodeForSession(java.lang.String matsSocketSessionId)
                                                                                          throws ClusterStoreAndForward.DataAccessException

Specified by:

getCurrentRegisteredNodeForSession in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the MatsSocketSessionId for which to find current session home.

Returns:

the current node holding MatsSocket Session, or empty if none.

Throws:

ClusterStoreAndForward.DataAccessException

isSessionExists

public boolean isSessionExists(java.lang.String matsSocketSessionId)
                        throws ClusterStoreAndForward.DataAccessException

Specified by:

isSessionExists in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the MatsSocketSessionId for which to check whether there is a session

Returns:

whether a CSAF Session exists - NOTE: Not whether it is currently registered!

Throws:

ClusterStoreAndForward.DataAccessException

getSessions

public java.util.List<MatsSocketServer.MatsSocketSessionDto> getSessions(boolean onlyActive,
                                                                         java.lang.String userId,
                                                                         java.lang.String appName,
                                                                         java.lang.String appVersionAtOrAbove)
                                                                  throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Direct implementation of MatsSocketServer.getMatsSocketSessions(boolean, String, String, String) - go read there for semantics.

Specified by:

getSessions in interface ClusterStoreAndForward

Returns:

the list of all MatsSocketSessions currently registered with this MatsSocketServer instance matching the constraints if set - as read from the data store.

Throws:

ClusterStoreAndForward.DataAccessException

getSessionsCount

public int getSessionsCount(boolean onlyActive,
                            java.lang.String userId,
                            java.lang.String appName,
                            java.lang.String appVersionAtOrAbove)
                     throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Direct implementation of MatsSocketServer.getMatsSocketSessionsCount(boolean, String, String, String) - go read there for semantics.

Specified by:

getSessionsCount in interface ClusterStoreAndForward

Returns:

the count of all MatsSocketSessions currently registered with this MatsSocketServer instance matching the constraints if set - as read from the data store.

Throws:

ClusterStoreAndForward.DataAccessException

closeSession

public void closeSession(java.lang.String matsSocketSessionId)
                  throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Invoked when the client explicitly tells us that he closed this session, CLOSE_SESSION. This deletes the session instance, and any messages in queue for it. No new incoming REPLYs, SENDs or RECEIVEs for this SessionId will be sent anywhere. (Notice that the implementation might still store any new outboxed messages, not checking that the session actually exists. But this SessionId will never be reused (exception without extreme "luck"), and the implementation will periodically purge such non-session-attached outbox messages).

Specified by:

closeSession in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the MatsSocketSessionId that should be closed.

Throws:

ClusterStoreAndForward.DataAccessException

notifySessionLiveliness

public void notifySessionLiveliness(java.util.Collection<java.lang.String> matsSocketSessionIds)
                             throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Shall be invoked on some kind of schedule (e.g. every 1 minute) by every node to inform ClusterStoreAndForward about which Sessions are currently live on that node. Sessions that aren't live, will be scavenged after some time by invocation of ClusterStoreAndForward.timeoutSessions(long).

Specified by:

notifySessionLiveliness in interface ClusterStoreAndForward

Parameters:

matsSocketSessionIds - which sessions are currently live on the invoking node.

Throws:

ClusterStoreAndForward.DataAccessException

timeoutSessions

public java.util.Collection<java.lang.String> timeoutSessions(long notLiveSinceTimestamp)
                                                       throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Shall be invoked on some kind of schedule (e.g. every 10 minutes on average). Times out any session which have not been notified about liveliness since the supplied timestamp (millis from epoch).

Specified by:

timeoutSessions in interface ClusterStoreAndForward

Parameters:

notLiveSinceTimestamp - decides which sessions are too old: Sessions which have not been notified about liveliness since this timestamp will be deleted.

Returns:

which sessions was timed out.

Throws:

ClusterStoreAndForward.DataAccessException

scavengeSessionRemnants

public int scavengeSessionRemnants()
                            throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Shall be invoked on some kind of schedule (e.g. every hour on average). Scavenges all inboxes, outboxes and "request boxes" for any lingering data for closed and timed out sessions.

Specified by:

scavengeSessionRemnants in interface ClusterStoreAndForward

Returns:

how many items was scavenged, for logging. May return constant zero if not readily available.

Throws:

ClusterStoreAndForward.DataAccessException

storeMessageIdInInbox

public void storeMessageIdInInbox(java.lang.String matsSocketSessionId,
                                  java.lang.String clientMessageId)
                           throws ClusterStoreAndForward.MessageIdAlreadyExistsException,
                                  ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Stores the incoming message Id, to avoid double delivery. If the Client MessageId (cmid) already exists, a ClusterStoreAndForward.MessageIdAlreadyExistsException will be raised - this implies that a double delivery has occurred.

Specified by:

storeMessageIdInInbox in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the MatsSocketSessionId for which to store the incoming message id.

clientMessageId - the client's message Id for the incoming message.

Throws:

ClusterStoreAndForward.MessageIdAlreadyExistsException - if the Client MessageId (cmid) already existed for this SessionId.

ClusterStoreAndForward.DataAccessException

updateMessageInInbox

public void updateMessageInInbox(java.lang.String matsSocketSessionId,
                                 java.lang.String clientMessageId,
                                 java.lang.String envelopeWithMessage,
                                 byte[] messageBinary)
                          throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Stores the resulting message (envelope and binary), so that if the incoming messages comes again (based on ClusterStoreAndForward.storeMessageIdInInbox(String, String) throwing ClusterStoreAndForward.MessageIdAlreadyExistsException), the result from the previous processing can be returned right away.

Specified by:

updateMessageInInbox in interface ClusterStoreAndForward

Throws:

ClusterStoreAndForward.DataAccessException

getMessageFromInbox

public ClusterStoreAndForward.StoredInMessage getMessageFromInbox(java.lang.String matsSocketSessionId,
                                                                  java.lang.String clientMessageId)
                                                           throws ClusterStoreAndForward.DataAccessException

Specified by:

getMessageFromInbox in interface ClusterStoreAndForward

Throws:

ClusterStoreAndForward.DataAccessException

deleteMessageIdsFromInbox

public void deleteMessageIdsFromInbox(java.lang.String matsSocketSessionId,
                                      java.util.Collection<java.lang.String> clientMessageIds)
                               throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Deletes the incoming message Ids, as we've established that the client will never try to send this particular message again.

Specified by:

deleteMessageIdsFromInbox in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the MatsSocketSessionId for which to delete the incoming message id.

clientMessageIds - the client's message Ids for the incoming messages to delete.

Throws:

ClusterStoreAndForward.DataAccessException

storeMessageInOutbox

public java.util.Optional<ClusterStoreAndForward.CurrentNode> storeMessageInOutbox(java.lang.String matsSocketSessionId,
                                                                                   java.lang.String serverMessageId,
                                                                                   java.lang.String clientMessageId,
                                                                                   java.lang.String traceId,
                                                                                   MatsSocketServer.MessageType type,
                                                                                   java.lang.Long requestTimestamp,
                                                                                   java.lang.String envelope,
                                                                                   java.lang.String messageJson,
                                                                                   byte[] messageBinary)
                                                                            throws ClusterStoreAndForward.DataAccessException,
                                                                                   ClusterStoreAndForward.MessageIdAlreadyExistsException

Description copied from interface: ClusterStoreAndForward

Stores the message for the Session, returning the nodename for the node holding the session, if any. If the session is closed/timed out, the message won't be stored (i.e. dumped on the floor) and the return value is empty. The Server MessageId (smid) is set by the caller - and since this might have a collision, the method throws ClusterStoreAndForward.MessageIdAlreadyExistsException if unique constraint fails. In this case, a new Server MessageId should be picked and try again.

Specified by:

storeMessageInOutbox in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the matsSocketSessionId that the message is meant for.

serverMessageId - unique id for outbox'ed message within the MatsSocketSessionId. Must be long enough that it is extremely unlikely that is collides with another message within the same MatsSocketSessionId - but do remember that there will at any one time be pretty few messages in the outbox for a given MatsSocketSession.

clientMessageId - For Client Replies to requests from Server-to-Client, this is the Client's Message Id, which we need to send back with the Reply so that the Client can correlate the Request. (Nullable, since not all messages are replies).

traceId - the server-side traceId for this message.

type - the type of the outgoing message (RESOLVE, REJECT or PUB).

requestTimestamp - For Client Replies to requests from Server-to-Client, this is the timestamp we received the Request.

envelope - the JSON-serialized MatsSocket Envelope without the 'msg' field set.

messageJson - the JSON-serialized message - the piece that sits in the 'msg' field of the Envelope. (Nullable)

messageBinary - the binary part of an outgoing message. (Nullable)

Returns:

the current node holding MatsSocket Session, or empty if none.

Throws:

ClusterStoreAndForward.MessageIdAlreadyExistsException - if the Server MessageId (smid) already existed for this SessionId.

ClusterStoreAndForward.DataAccessException

getMessagesFromOutbox

public java.util.List<ClusterStoreAndForward.StoredOutMessage> getMessagesFromOutbox(java.lang.String matsSocketSessionId,
                                                                                     int maxNumberOfMessages)
                                                                              throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Fetch a set of messages, up to 'maxNumberOfMessages' - but do not include messages that have been attempted delivered already (marked with ClusterStoreAndForward.outboxMessagesAttemptedDelivery(String, Collection)). If ClusterStoreAndForward.outboxMessagesUnmarkAttemptedDelivery(String) is invoked, that mark will be unset.

Specified by:

getMessagesFromOutbox in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the matsSocketSessionId that the message is meant for.

maxNumberOfMessages - the maximum number of messages to fetch.

Returns:

a list of json encoded messages destined for the WebSocket.

Throws:

ClusterStoreAndForward.DataAccessException

outboxMessagesAttemptedDelivery

public void outboxMessagesAttemptedDelivery(java.lang.String matsSocketSessionId,
                                            java.util.Collection<java.lang.String> serverMessageIds)
                                     throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

Marks the specified messages as attempted delivered and notches the ClusterStoreAndForward.StoredOutMessage.getDeliveryCount() one up. If ClusterStoreAndForward.outboxMessagesUnmarkAttemptedDelivery(String) is invoked (typically on reconnect), the mark will be unset, but the delivery count will stay in place - this is to be able to abort delivery attempts if there is something wrong with the message.

Specified by:

outboxMessagesAttemptedDelivery in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the matsSocketSessionId that the serverMessageIds refers to.

serverMessageIds - which messages failed delivery.

Throws:

ClusterStoreAndForward.DataAccessException

outboxMessagesUnmarkAttemptedDelivery

public void outboxMessagesUnmarkAttemptedDelivery(java.lang.String matsSocketSessionId)
                                           throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

When this method is invoked, ClusterStoreAndForward.getMessagesFromOutbox(String, int) will again return messages that has previously been marked as attempted delivered with ClusterStoreAndForward.outboxMessagesAttemptedDelivery(String, Collection). Notice that the ClusterStoreAndForward.StoredOutMessage.getDeliveryCount() will not be reset, but the ClusterStoreAndForward.StoredOutMessage.getAttemptTimestamp() will now again return null.

Specified by:

outboxMessagesUnmarkAttemptedDelivery in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the matsSocketSessionId whose messages now shall be attempted.

Throws:

ClusterStoreAndForward.DataAccessException

outboxMessagesComplete

public void outboxMessagesComplete(java.lang.String matsSocketSessionId,
                                   java.util.Collection<java.lang.String> serverMessageIds)
                            throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

States that the messages are delivered. Will typically delete the message.

Specified by:

outboxMessagesComplete in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the matsSocketSessionId that the serverMessageIds refers to.

serverMessageIds - which messages are complete.

Throws:

ClusterStoreAndForward.DataAccessException

outboxMessagesDeadLetterQueue

public void outboxMessagesDeadLetterQueue(java.lang.String matsSocketSessionId,
                                          java.util.Collection<java.lang.String> serverMessageIds)
                                   throws ClusterStoreAndForward.DataAccessException

Description copied from interface: ClusterStoreAndForward

States that the messages overran the accepted number of delivery attempts.

Specified by:

outboxMessagesDeadLetterQueue in interface ClusterStoreAndForward

Parameters:

matsSocketSessionId - the matsSocketSessionId that the serverMessageIds refers to.

serverMessageIds - which messages should be DLQed.

Throws:

ClusterStoreAndForward.DataAccessException

storeRequestCorrelation

public void storeRequestCorrelation(java.lang.String matsSocketSessionId,
                                    java.lang.String serverMessageId,
                                    long requestTimestamp,
                                    java.lang.String replyTerminatorId,
                                    java.lang.String correlationString,
                                    byte[] correlationBinary)
                             throws ClusterStoreAndForward.DataAccessException

Specified by:

storeRequestCorrelation in interface ClusterStoreAndForward

Throws:

ClusterStoreAndForward.DataAccessException

getAndDeleteRequestCorrelation

public java.util.Optional<ClusterStoreAndForward.RequestCorrelation> getAndDeleteRequestCorrelation(java.lang.String matsSocketSessionId,
                                                                                                    java.lang.String serverMessageId)
                                                                                             throws ClusterStoreAndForward.DataAccessException

Specified by:

getAndDeleteRequestCorrelation in interface ClusterStoreAndForward

Throws:

ClusterStoreAndForward.DataAccessException