The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jun. 02, 2009
Filed:
Oct. 18, 2004
Srinivas Hasti, Raleigh, NC (US);
Gabriel Garcia Montero, Chapel Hill, NC (US);
Aravind Srinivasan, Raleigh, NC (US);
Renganathan Sundararaman, Cary, NC (US);
Kevin Edward Vaughan, Fuquay Varina, NC (US);
Srinivas Hasti, Raleigh, NC (US);
Gabriel Garcia Montero, Chapel Hill, NC (US);
Aravind Srinivasan, Raleigh, NC (US);
Renganathan Sundararaman, Cary, NC (US);
Kevin Edward Vaughan, Fuquay Varina, NC (US);
International Business Machines Corporation, Armonk, NY (US);
Abstract
Session state affinity is maintained in a workload balancing system that includes a hypertext transfer protocol (HTTP) routing server and a plurality of application servers. The application servers maintain backup session state information for a first session to a first server of the plurality of application servers at fewer than all of the plurality of application servers, detect the unavailability of the first application server at an application server of the plurality of application servers other than the first application and determine a second server that continues the first session. An identification of the second server and the first session is sent from an application server of the plurality of application servers to a HTTP routing server responsive to detecting the unavailability of the first server. The identification of the second server and the first session is received at the HTTP routing server and communications associated with the first session are routed from the HTTP routing server to the second server responsive to receiving the identification of the second server so that backup session state information maintained at the second server is used to continue the first session from the first server at the second server.