Autonomic adjustment of connection keep-alives

• US 7,460,556 B2
• Filed: 02/17/2005
• Issued: 12/02/2008
• Est. Priority Date: 02/17/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Wisniewski, Robert, Joglekar, Niharika Sudhir, Lokhande, Bhushan Kamlakar, Duggirala, Surya V., Goshgarian, Matthew Ara
• Primary Examiner(s): Shah; Chirag G
• Assistant Examiner(s): Zhou; Yong
• Application Number:
  US11/060,358
• Publication Number:
  US 20060182141A1
• Time in Patent Office: 1,384 Days
• Field of Search: 370/328, 370/395.1, 370/465, 370/295.1, 709/223, 709/224, 709/227
• US Class Current: 370/465
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A server computer system includes a keep-alive autonomic adjustment mechanism that monitors current operating conditions and dynamically adjusts the keep-alive specification to optimize the keep-alives for the current operating conditions. The keep-alive autonomic adjustment mechanism monitors the total number of clients, and the average number of requests per client. The value of a keep-alive specification that determines how log to keep a connection open may be dynamically and autonomically adjusted by the keep-alive autonomic adjustment mechanism according to the monitored current operating conditions. The keep-alive autonomic adjustment mechanism may also include the ability to autonomically enable and disable the keep-alives. In this manner the performance of the server may be tuned to optimize the effect of using keep-alives according to current operating conditions.

Claims

1. A computer-implemented method for a server application to manage connection keep-alives, the method comprising the steps of:

(A) enabling a keep-alive mechanism that keeps a connection to a client open according to a defined keep-alive specification;

(B) monitoring number of clients and average number of requests per client for the server application;

(C) automatically enabling the keep alive mechanism when the number of clients is in excess of a first predetermined threshold;

(D) automatically enabling the keep alive mechanism when the number of requests per client is in excess of a second predetermined threshold;

(E) automatically disabling the keep alive mechanism when the number of clients is below the first predetermined threshold and the average number of requests per client is below the second predetermined threshold;

(F) setting the keep-alive specification to a minimal value when the number of clients is above the first predetermined threshold and the average number of requests per client is below the second predetermined threshold;

(G) setting the keep-alive specification to a maximum value when the number of clients is below the first predetermined threshold and the average number of requests per client is above the second predetermined threshold; and

(H) setting the keep-alive specification to a midrange value between the minimal value and the maximum value when the number of clients is above the first predetermined threshold and the average number of requests per client is above the second predetermined threshold.