Maintaining HTTP session affinity in a cluster environment

• US 6,947,992 B1
• Filed: 05/01/2000
• Issued: 09/20/2005
• Est. Priority Date: 05/01/2000
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Shachor, Gal
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): LAFORGIA, CHRISTIAN A
• Application Number:
  US09/562,375
• Time in Patent Office: 1,968 Days
• Field of Search: 709/201, 709/203, 709/227, 709/219, 709/229, 709/228, 380/30, 713/201
• US Class Current: 709/228
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/563 Data redirection of data network streams

Abstract

A method for controlling communications between a client and a cluster of servers includes conducting a first communication session over a network between the client and a selected one of the servers in the cluster, and sending identifying data generated responsive to the first communication session over the network for storage by the client. Upon receiving a request from the client to conduct a second communication session, the request comprising the identifying data, the request is routed to the selected server responsive to the identifying data in the request.

Claims

1. A method for controlling communications between a client and a cluster of servers, comprising:

conducting a first communication session over a network between the client and a selected one of the servers in the cluster;

updating a value of a version-validity counter so as to identify a current version of session data in a cache held by the selected one of the servers;

sending identifying data generated responsive to the first communication session together with the updated value of the counter over the network for storage by the client;

receiving a request from the client to conduct a second communication session, the request comprising the identifying data; and

routing the request to the selected server responsive to the identifying data in the request; and

receiving the routed request at the server and comparing a first value of the version-validity counter comprised in the request from the client to a second value of the version-validity counter held by the server so as to determine whether to use the session data in the cache in the second communication session.

2. A method according to claim 1, wherein conducting the first communication session comprises communicating using an application protocol.

3. A method according to claim 2, wherein the application protocol comprises the Hypertext Transfer Protocol (HTTP), and wherein receiving the request comprises receiving a HTTP request.

4. A method according to claim 3, wherein the network comprises the Internet, and wherein the servers comprise Web servers.

5. A method according to claim 1, wherein the identifying data comprise a reference to a network address of the selected server.

6. A method according to claim 5, wherein the network address comprises an Internet Protocol (IP) address.

7. A method according to claim 1, wherein the identifying data comprise an identification of a routing port associated with the selected server.

8. A method according to claim 1, wherein conducting the first communication session comprises running an application process on the selected server, and wherein the identifying data comprise an identification of the application process.

9. A method according to claim 8, wherein routing the request comprises passing the request to be handled by the application process.

10. A method according to claim 1, and comprising storing the session data from the first communication session in a session holder and retrieving the stored session data from the session holder for use in the second communication session responsive to a mismatch between the first and second values of the version-validity counter.

11. A method according to claim 1, wherein updating the value of the version-validity counter comprises updating the value responsive to a change of a predetermined type in the session data.

12. A method according to claim 1, wherein sending the identifying data comprises sending a cookie to be stored by the client.

13. A method according to claim 1, wherein receiving the request from the client comprises receiving a Uniform Resource Locator (URL) that has been rewritten by a server to include the identifying data.

14. Network server apparatus, comprising:

a cluster of servers, coupled to communicate with a client over a network, and operative, responsive to a first communication session conducted between the client and a selected one of the servers in the cluster, to send identifying data generated responsive to the first communication session over the network for storage by the client,

wherein the selected one of the servers comprises a cache, and wherein the identifying data sent to the client comprise a value of a version-validity counter, which is updated by the selected one of the servers so as to identify a current version of session data in the cache; and

a router, coupled to receive a request from the client to conduct a second communication session, the request comprising the identifying data, and to route the request to the selected server responsive to the identifying data in the request,

wherein the selected server compares a first value of the version-validity counter comprised in the request from the client to a second value of the version-validity counter held by the server so as to determine whether to use the session data in the cache in the second communication session.

15. Apparatus according to claim 14, wherein the servers comprise application servers, which communicate with the client using an application protocol.

16. Apparatus according to claim 15, wherein the application protocol comprises the Hypertext Transfer Protocol (HTTP), and wherein the request comprises a HTTP request.

17. Apparatus according to claim 16, wherein the network comprises the Internet, and wherein the servers comprise Web servers.

18. Apparatus according to claim 14, wherein the identifying data comprise a reference to a network address of the selected server.

19. Apparatus according to claim 18, wherein the network address comprises an Internet Protocol (IP) address.

20. Apparatus according to claim 14, wherein the router comprises a plurality of ports, and wherein the identifying data comprise an identification of one of the ports that is linked to the selected server.

21. Apparatus according to claim 14, wherein the first communication session is conducted by an application process running on the selected server, and wherein the identifying data comprise an identification of the application process, responsive to which the selected server passes the request to be handled by the application process.

22. Apparatus according to claim 14, and comprising a session holder, which is coupled to receive and store the session data from the first communication session, wherein the servers are adapted to retrieve the stored session data from the session holder for use in the second communication session responsive to a mismatch between the first and second values of the version-validity counter.

23. A computer software product for controlling communications between a client and a cluster of servers, the product comprising a computer-readable medium in which program instructions are stored, which instructions, when read by a selected one of the servers, cause the server to conduct a first communication session over a network with the client and to update a value of a version-validity counter so as to identify a current version of session data in a cache held by the server, and to send identifying data generated responsive to the first communication session together with the updated value of the counter over the network for storage by the client, so that when a request comprising the identifying data is received at the cluster from the client to conduct a second communication session, the request is routed to the selected server responsive to the identifying data in the request, and the server, upon receiving the routed request, compares a first value of the version-validity counter comprised in the request from the client to a second value of the version-validity counter held by the server so as to determine whether to use the session data in the cache in the second communication session.

24. A product according to claim 23, wherein the servers comprise Web servers, which communicate with the client using the Hypertext Transfer Protocol (HTTP), and wherein the request comprises a HTTP request.