Scalable java servers for network server applications

• US 7,139,805 B2
• Filed: 05/30/2001
• Issued: 11/21/2006
• Est. Priority Date: 05/30/2000
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Seagren, Charles F., Chapman, Barbara A.
• Primary Examiner(s): PWU, JEFFREY C
• Application Number:
  US09/870,029
• Publication Number:
  US 20020007410A1
• Time in Patent Office: 2,001 Days
• Field of Search: 709/227, 709238-241, 709/228, 709/225, 709/202, 709/204, 709/217, 714/4
• US Class Current: 709/207
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• CPC Class Codes: G06F 11/2007 using redundant communication media
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 11/2089 Redundant storage control functionality
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1017 based on a round robin mechanism
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer

Abstract

A system for providing Java-implemented Application Servers to a plurality of clients. Each of the Java-implemented Application Servers is configured to execute on a processing element of a server which has multiple independent processing elements arranged such that a failure of one processing element does not affect the operability of the other processing elements. A Distributor is provided to enable making connections with the clients and then determine which of the Application Servers actually services the clients requests. The Distributor attempts to choose the Application Server that has the fewest number of clients as the server for a new client request. A monitoring program restarts the Distributor if it fails. The system thus provides a scalable and available set of Java-implemented Application Servers without requiring any change to the Java-implemented application itself.

Claims

1. A system for providing Java-implemented Application Servers to a plurality of clients, the system comprising:

a computing system having a plurality of processing elements, each element configured such that, despite a failure of one processing element, the remaining processing elements continue to function;

a plurality of Java-implemented Application Servers, at least one Server assigned to execute on one or more processing elements; and

a distributor module that is configured to capture connection requests from a client on a port, to select one of the plurality of Application Servers to communicate with the requesting client during the connection and to assign the connection request to the selected one of the plurality of Application Servers, such that, after the assignment, the selected Application Server communicates directly with the client,

wherein the distributor module is configured to capture client connection requests only for one of a plurality of Application server classes,

a monitoring module that is configured to restart the distributor and any Application server that fails.

2. A system for providing Java-implemented Application Servers to a plurality of clients as recited in claim 1,

wherein the distributor module is configured to select one of the Application Servers by:

determining whether there is an Application Server supporting fewer connections than the other Application Servers,

if there is such an Application Server, sending to the Application Server a message that identifies the client making the connection request,

if there is no such Application Server, placing the client connection request on a waiting list until such an Application Server is available, and

when such an Application Server becomes available, sending to the Application Server a message that identifies the client making the connection request.

3. A system for providing Java-implemented Application Servers to a plurality of clients as recited in claim 2, wherein determining whether there is an Application Server supporting fewer connections than the other Application Servers is performed by executing a weighted round robin procedure.

4. A system for providing Java-implemented Application Servers to a plurality of clients as recited in claim 1, wherein the distributor module is further configured to:

maintain an information structure that includes a number indicating how many clients have a connection with each Application Server,

receive a message from an Application Server that a connection between the Application Server and a client is closed, and

update the number of clients with a connection to the Application Server that sent the message.

5. A method for providing Java-implemented Application Servers to a plurality of clients, the method comprising:

providing a plurality of processing elements, each element configured such that, despite a failure of one processing element, the remaining processing elements continue to function;

causing a plurality of Java-implemented Application Servers to execute on the processing elements, at least one Server assigned to execute on one or more of the processing elements;

receiving incoming client connection requests at at least one port managed by a distributor module, the distributor module being configured to receive client connection requests only for one of a plurality of Application server classes;

selecting one of the Application Servers to communicate with the client during the connection; and

assigning, by the distributor module, the connection request to the selected Application Server such that, after the assignment, the selected Application Server communicates with the client directly,

wherein the distributor module maintains an information structure that includes a number indicating how many clients have a connection with each Application Server; and

further comprising the steps of;

receiving a message from an Application Server that a connection between the Application Server and a client is closed; and

updating the number of clients with a connection to the Application Server that sent the message.

6. A method for providing Java-implemented Application Servers to a plurality of clients as recited in claim 5, further comprising the steps of:

monitoring the operation of the Application Servers and the distributor module for failures;

if a failure occurs in the distributor module, restarting the distributor module; and

if a failure occurs in one of the Application servers, restarting the Application server.

7. A method for providing Java-implemented Application Servers to a plurality of clients as recited in claim 5, wherein the step of selection one of the Application Servers includes the steps of:

determining whether there is an Application Server supporting fewer connections than the other Application Servers;

if there is such an Application Server, sending to the Application Server a message that identifies the client making the connection request;

if there is no such Application Server, placing the client connection request on a waiting list until such an Application Server is available; and

when such an Application Server becomes available, sending to the Application Server a message that identifies the client making the connection request.

9. The system of claim 7 wherein the plurality of application servers are implemented using Java.

8. A system, comprising:

a plurality of processing elements, each processing element configured such that, despite a failure of one processing element, the remaining processing elements continue to function;

a plurality of application servers assigned to execute on the processing elements, wherein the plurality of application servers comprise distinct classes of application servers; and

a plurality of distributor modules coupled between the application servers and a plurality of clients, wherein each distributor module is configured to handle client connection requests to only a distinct class of application servers,

wherein each distributor module has an initialization phase, a main operating phase and a restart phase.

10. The system of claim 8 wherein, in the initialization phase, a given distributor module obtains a server class name for itself and server class names for application servers associated with the given distributor module.

11. The system of claim 8 wherein, in the main operating phase, a given distributor module sends an address of a requesting client to an application server that is currently handling the fewest number of clients.

12. The system of claim 8 wherein, in the restarting phase, a given distributor module begins a dialog with each application server associated with the given distributor module.

13. The system of claim 8 wherein a distinct class of application servers comprises one of a manager class and an employee class.

14. A method, comprising:

initializing a distributor module, the distributor module being assigned to distribute client connection requests to only one of a plurality of application server types;

receiving incoming client connection requests by the distributor module; and

distributing each client connection request by the distributor module to one of the assigned type of application servers based on a determination of which application server is currently handling the fewest number of clients,

wherein the distributor module is configured to maintain an information structure that includes a number indicating how many clients have a connection with each application server, receive a message from an application server that a connection between the application server and a client is closed, and update the number of clients with a connection to the Application Server that sent the message.

15. The method of claim 14 wherein distributing each client connection request by the distributor module further comprises determining when an application server has not responded to the distributor module regarding a previous request.

16. The method of claim 14 further comprising placing a client connection request on a waiting list until the determination of which application server is currently handling the fewest number of clients is made.