Client/server architecture supporting concurrent servers within a server with a transaction manager providing server/connection decoupling

• US 5,761,507 A
• Filed: 03/05/1996
• Issued: 06/02/1998
• Est. Priority Date: 03/05/1996
• Status: Expired due to Term

• Current Assignee: GlobalFoundries, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Govett, Ian Robert
• Primary Examiner(s): Kim, Kenneth S.
• Application Number:
  US08/610,943
• Time in Patent Office: 819 Days
• Field of Search: 395/200.03, 395/200.09, 395/200.12, 395/684, 395/200.33, 395/200.49, 395/200.57, 395/672, 395/674, 395/675
• US Class Current: 718/101
• CPC Class Codes: G06F 2209/5022 Workload threshold
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system

Abstract

A transaction manager intercepts all requests for service from any of a plurality of clients, establishes connections independently of task requests and assigns available servers to the requests in the order the requests are received in order to provide equitable distribution of service resources over an increased number of client/server connections. Preferably, the transaction manager provides for starting at least one server independently of any request, direction of all client requests for server connections to a transaction manager independently of any server, placement of task requests in a queue and starting and stopping additional servers based on queue length.

Claims

1. A method of performing a remote procedure call from a remote procedure call client on a first data processor by a server running on a second data processor, said second data processor including a remote procedure call transaction manager, said method including the steps of

starting a server independently of a remote procedure call by loading and initializing an application providing a service corresponding to a remote procedure call on said second data processor,

establishing a connection between said remote procedure call client and a connection handle in said transaction manager,

receiving at said transaction manager a representation of a remote procedure call over said connection,

transferring said remote procedure call and said connection handle from said transaction manager to an available server by said transaction manager in order of receipt and independently of said step of establishing a connection, and

controlling said server to communicate a result of said remote procedure call to said client in accordance with said connection handle and return said connection handle to said transaction manager.

2. A method as recited in claim 1, including the further step of

starting another server at said second data processor when the number of requests awaiting assignment of a server exceeds a configuration value.

3. A method as recited in claim 2, including the further step of stopping an idle server at said second data processor after a time delay by unloading from said second data processor said application corresponding to said idle server.

4. A method as recited in claim 3, wherein said time delay is set in accordance with an amount of time required for starting a server.

5. A method as recited in claim 2, including the further step of

placing a representation of a remote procedure call in a queue.

6. A method as recited in claim 5, wherein said representation of a remote procedure call is a socket handle.

7. A method as recited in claim 2, including the further step of

placing a remote procedure call in a queue.

8. A method as recited in claim 1, including the further step of

logging server transactions.

9. A method as recited in claim 1, including the further step of

time stamping completion of processing of a client request by a server.

10. A method as recited in claim 1, including the further step of

processing an administrative command.

11. A transaction manager for a data processing network including a remote procedure call client at a first data processor and a resource at a second data processor, said transaction manager including

means for starting a server providing a service corresponding to a remote procedure call on said second data processor by loading on said second data processor an application providing said service independently of a remote procedure call,

means including a connection handle for establishing a connection between said remote procedure call client and said connection handle independently of said server,

means for receiving a representation of a remote procedure call over said connection,

means for transferring said remote procedure call including said connection handle to an available server in order of receipt and independently of said means for establishing a connection whereby said server is enabled to communicate a result of said remote procedure call to said remote procedure call client in accordance with said connection handle and return said connection handle to said transaction manager.

12. A transaction manager as recited in claim 11 further including

means for starting an additional server at said second data processor when the number of requests awaiting assignment of a server exceeds a configuration value.

13. A transaction manager as recited in claim 12, further including means for stopping an idle server at said second data processor after a time delay by unloading from said second data processor said application corresponding to said idle server.

14. A transaction manager as recited in claim 13, wherein said time delay includes means for storing a configurable parameter.

15. A transaction manager as recited in claim 14, wherein said configurable parameter is set in accordance with an amount of time required for starting a server.