Managing Communications in a Multi-Client, Multi-Server Environment

• US 20140344337A1
• Filed: 03/31/2014
• Published: 11/20/2014
• Est. Priority Date: 05/16/2013
• Status: Active Grant

• Current Assignee: Toshiba Global Commerce Solutions Holdings Corporation (Toshiba Corporation)
• Original Assignee: Toshiba Global Commerce Solutions Holdings Corporation (Toshiba Corporation)
• Inventors: Marchesseault, Bradley T., Sramka, Peter, Lopez, Luis, Darden, Zachary McCain
• Granted Patent: US 9,596,297 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 2209/5013 Request control
• CPC Class Codes: G06F 2209/541 Client-server
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/143 Termination or inactivation of sessions, e.g. event-controlled end of session
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols

Abstract

According to one aspect of the present disclosure, a method is implemented by a server in a server cluster. A request received from a client includes a session identifier (ID) identifying a session between the client and the server, and a correlation ID that is linked to the request. If the correlation ID is not included in an individual server-specific session microcache for the session, the request is processed to determine a response, the response is added to the session microcache, and the response and an indication of the correlation ID are sent to the client. If the correlation ID and a response to the request are stored in the session microcache, the response and an indication of the correlation ID are re-sent to the client. The session ID and session microcache are transferred to another of the plurality of servers in the server cluster to continue the session.

Claims

1. A method of processing a request received from a client, the method being implemented by one of a plurality of servers in a server cluster and comprising:

receiving, from the client, a request that includes;

a session identifier (ID) identifying a session between the client and the server; and

a correlation ID that is linked to the request;

determining whether the correlation ID is included in an individual server-specific session microcache of the session;

if the correlation ID is not included in the session microcache, processing the request to determine a response, adding the response to the session microcache, and sending the response along with an indication of the correlation ID to the client;

if the correlation ID and a response to the request are stored in the session microcache, re-sending the response along with an indication of the correlation ID to the client; and

transferring the session ID and session microcache to another of the plurality of servers in the server cluster to continue the session.

2. The method of claim 1, further comprising:

receiving a response list from the client which contains correlation IDs linked to responses that have been received at the client from one or more servers of the server cluster for requests submitted as part of the session; and

if responses for any of the correlation IDs in the response list are stored in the session microcache, deleting those responses from the session microcache.

3. The method of claim 2, wherein deleting a response comprises deleting a record in the session microcache that includes both the response and the correlation ID for the response.

4. The method of claim 1, further comprising:

if a given response has resided in the session microcache for a predefined time period without the server receiving an indication that the client has received the response, deleting the response from the session microcache.

5. The method of claim 1, further comprising:

starting a timer based on a duplicate request being received; and

if a response to the duplicate request is not available after the timer indicates that a predefined time period has transpired, sending an error response to the client that includes an indication of the correlation ID for the request.

6. The method of claim 1, further comprising:

deleting a session microcache based on the session being terminated.

7. A method implemented by a client, comprising:

generating a request that includes;

a session identifier (ID) that identifies a session between the client and one of a plurality of servers of a server cluster;

a correlation ID that is linked to the request; and

a response list that contains correlation IDs linked to responses received from one or more servers of the server cluster for requests submitted by the client as part of the session;

sending the request to the server;

if a response to the request is not received within a predefined time period, re-sending the request to the same or another server of the server cluster; and

if a response to the request is received within the predefined time period, updating the response list to include the correlation ID, and sending the updated response list to the same or another server of the server cluster.

8. The method of claim 7, wherein the updated response list is sent to the same or another server of the server cluster as part of a subsequent, different request that is linked to a different correlation ID.

9. The method of claim 7, wherein the response list contains a predefined quantity of correlation IDs linked to the most recently received responses for the session.

10. The method of claim 7, further comprising:

abandoning the request if the request has been sent a predefined quantity of times without receiving a response.

11. A server that is part of a server cluster which includes a plurality of other servers, the server comprising:

a memory circuit configured to store an individual server-specific session microcache for a session between the server and a client; and

one or more processing circuits configured to;

receive, from the client, a request that includes;

a session identifier (ID) identifying the session between the client and the server; and

a correlation ID that is linked to the request;

determine whether the correlation ID is included in the session microcache;

if the correlation ID is not included in the session microcache, process the request to determine a response, add the response to the session microcache, and send the response along with an indication of the correlation ID to the client;

if the correlation ID and a response to the request are stored in the session microcache, re-send the response along with an indication of the correlation ID to the client; and

transfer the session ID and session microcache to another of the plurality of servers in the server cluster to continue the session.

12. The server of claim 11, wherein the one or more processing circuits are further configured to:

receive a response list from the client which contains correlation IDs linked to responses that have been received at the client from one or more servers of the server cluster for requests submitted by the client as part of the session; and

if responses for any of the correlation IDs in the response list are stored in the session microcache, delete those responses from the session microcache.

13. The server of claim 12, wherein to delete a response, the one or more processing circuits are configured to delete a record in the session microcache that includes both the response and the correlation ID for the response.

14. The server of claim 11, wherein the one or more processing circuits are further configured to:

if a given response has resided in the session microcache for a predefined time period without the server receiving an indication that the client has received the response, delete the response from the session microcache.

15. The server of claim 11, wherein the one or more processing circuits are further configured to:

start a timer based on a duplicate request being received; and

if a response to the duplicate request is not available after the timer indicates that a predefined time period has transpired, send an error response to the client that includes an indication of the correlation ID for the request.

16. The server of claim 11, wherein the one or more processing circuits are further configured to:

delete a session microcache based on the session being terminated.

17. A client, comprising:

one or more processing circuits configured to;

generate a request that includes;

a session identifier (ID) that identifies a session between the client and one of a plurality of servers of a server cluster;

a correlation ID that is linked to the request; and

a response list that contains correlation IDs linked to responses received from one or more servers of the server cluster for requests submitted by the client as part of the session;

send the request to the server;

if a response to the request is not received within a predefined time period, re-send the request to the same or another server of the server cluster; and

if a response to the request is received within the predefined time period, update the response list to include the correlation ID, and send the updated response list to the same or another server of the server cluster; and

a memory circuit configured to store the response list.

18. The client of claim 17, wherein the updated response list is sent to the same or another server of the server cluster as part of a subsequent, different request that is linked to a different correlation ID.

19. The client of claim 17, wherein the response list contains a predefined quantity of correlation IDs linked to the most recently received responses for the session.

20. The client of claim 17, wherein the one or more processing circuits are further configured to:

abandon the request if the request has been sent a predefined quantity of times without receiving a response.