System and method for concentration and load-balancing of requests

• US 7,774,403 B2
• Filed: 10/31/2005
• Issued: 08/10/2010
• Est. Priority Date: 07/27/2000
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Bower, Peter, Ferwerda, Paul
• Primary Examiner(s): Phillips; Hassan
• Assistant Examiner(s): Tiv; Backhean
• Application Number:
  US11/262,632
• Publication Number:
  US 20060069723A1
• Time in Patent Office: 1,744 Days
• Field of Search: 709201-227, 709/231, 719316-330, 726/5
• US Class Current: 709/201
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• 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/10015 Access to distributed or replicated servers, e.g. using brokers
• 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/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method for concentration and load-balancing of requests in a distributed computing environment. In accordance with an embodiment, a system and a method for reducing the number of connections in an Internet environment using one or a plurality of connection handlers which handle the connection from the client to the server, and a listener which determines which connection handler to use to handle the connection. Whereas prior solutions required a (n×m) number of connections to handle requests, the invention allows there to be only m connections which significantly reduces resource requirements and allows scalability.

Claims

1. A system in a distributed object environment that supports server connection concentration, comprising:

a plurality of connection handlers to handle a plurality of connections from a plurality of clients to a plurality of remote servers; and

a listener, running on one or more microprocessors, which determines which particular connection handler of the plurality of connection handlers to handle a particular connection;

wherein the listener upon receiving a request from a client of the plurality of clients to invoke an object on a remote server of the plurality of remote servers performs steps of;

first checking to see if any connection handler currently handles a connection to the remote server;

choosing a least burdened connection handler to balance a load among all available connection handlers;

starting a connection handler to handle the request, if no existing connection handler can handle the connection; and

connecting the remote server to another connection handler and updating a shared memory of the plurality of connection handlers, if the corresponding connection handler cannot handle the connection;

receiving an object reference from the remote server, wherein the object reference contains connection information at the remote server;

associating the object reference with the connection handler that handles the connection to the remote server;

calling an object binding routine to bind the object reference, together with host, port, and client identifier parameters; and

invoking the connection handler to forward the request to the remote server and reply to the client.

2. The system of claim 1, wherein the object is a service at the server.

3. The system of claim 1, wherein the client is any one of a native C++ client, a JAVA client, a notification service, or a native server acting as a client.

4. The system of claim 1, wherein the remote server is any one of a native server, a native client registered for events, or a non-native CORBA-compliant Object Request Broker (ORB) server.

5. The system of claim 1 wherein the request is received via a message queue.

6. The system of claim 1 wherein the request is an Internet Inter-ORB Protocol (IIOP) request, and wherein the connection handler performs steps of:

replacing an original IIOP request id for the IIOP request with a unique id;

placing the request on a list of requests for this context;

sending the IIOP request to the server; and

when a response is received from the server, searching the list of requests for the corresponding request, replacing the unique id with the original IIOP request id, and sending the response to the client.

7. The system of claim 1, wherein upon receiving the request to invoke the object on the remote server the listener performs further steps of adding client information to the object reference received from the remote server and passing the object reference to another remote server.

8. The system of claim 1, wherein the listener maintains a reference count that indicates the number of object references invoked at any one of the plurality of remote servers, and closes a connection to a particular remote server once the reference count is decremented to zero.

9. A method in a distributed object environment that supports server connection concentration, comprising the steps of:

handling, via a plurality of connection handlers, a plurality of connections from a plurality of clients to a plurality of remote servers;

associating a listener with the plurality of connection handlers; and

upon receiving a request at the listener to invoke an object on a remote server of the plurality of remote servers, performing the steps of;

first checking to see if any connection handler currently handles a connection to the remote server;

choosing a least burdened connection handler to balance a load among all available connection handlers;

starting a connection handler to handle the request, if no existing connection handler can handle the connection; and

connecting the remote server to another connection handler and updating a shared memory of the plurality of connection handlers, if the corresponding connection handler cannot handle the connection;

receiving an object reference from the remote server, wherein the object reference contains connection information at the remote server;

associating the object reference with the connection handler that handles the connection to the remote server;

calling an object binding routine to bind the object reference, together with host, port, and client identifier parameters; and

invoking the connection handler to forward the request to the remote server and a reply to the client.

10. The method of claim 9, further comprising:

allowing the object to be a service at the server.

11. The method of claim 9, further comprising:

allowing the client to be any one of a native C++ client, a JAVA client, a notification service, or a native server acting as a client.

12. The method of claim 9, further comprising:

allowing the server to be any one of a native server, a native client registered for events, or a non-native CORBA-compliant ORB server.

13. The method of claim 9 further comprising:

allowing the request to be received via a message queue.

14. The method of claim 9 further comprising:

allowing the request to be an IIOP request;

replacing, via the connection handler, an original IIOP request id for the IIOP request with a unique id;

placing, via the connection handler, the request on a list of requests for this context;

sending, via the connection handler, the IIOP request to the server; and

when a response is received from the server, searching the list of requests for the corresponding request, replacing the unique id with the original IIOP request id, and sending the response to the client.

15. A machine readable memory having instructions stored thereon that when executed by one or more processors cause a system to perform the steps of:

handling, via a plurality of connection handlers, a plurality of connections from a plurality of clients to a plurality of remote servers;

associating a listener with the plurality of connection handlers; and

upon receiving a request at the listener to invoke an object on a remote server of the plurality of remote servers, performing the steps of;

first checking to see if any connection handler currently handles a connection to the remote server;

choosing a least burdened connection handler to balance a load among all available connection handlers;

starting a connection handler to handle the request, if no existing connection handler can handle the connection; and

connecting the remote server to another connection handler and updating a shared memory of the plurality of connection handlers, if the corresponding connection handler cannot handle the connection;

receiving an object reference from the remote server, wherein the object reference contains connection information at the remote server;

associating the object reference with the connection handler that handles the connection to the remote server;

calling an object binding routine to bind the object reference, together with host, port, and client identifier parameters; and

invoking the connection handler to forward the request to the remote server and a reply to the client.