System and method for achieving scalability in domain computing

• US 8,166,095 B2
• Filed: 07/28/2010
• Issued: 04/24/2012
• Est. Priority Date: 07/27/2000
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Ferwerda, Paul, Bower, Peter
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US12/845,630
• Publication Number:
  US 20110016203A1
• Time in Patent Office: 636 Days
• Field of Search: 709/217, 709/223, 709/224, 709/225
• 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 connection management system can achieve scalability for domain computing among a plurality of domains. Each of the plurality of domains comprises a collection of machines and resources that are administrated as a unit. A connection concentrator can connect, and support communication between, a plurality of processes in a first domain and a plurality of processes in a second domain. The connection concentrator uses one connection to communicate with any one of the plurality of processes in the first domain, and can communicate with each one of the plurality of processes in the second domain.

Claims

1. A system of connection management to achieve scalability for domain computing, comprise:

a connection concentrator that manages connections between a plurality of domains, wherein each domain of the plurality of domains comprises a collection of machines and resources that are administrated as a unit,

wherein the connection concentrator uses a plurality of handlers to handle communication between a plurality of processes in a first domain in the plurality of domains and a plurality of processes in a second domain in the plurality of domains, wherein each handler associated with the connection concentrator uses a plurality of connections to communicate with the plurality of processes in the second domain and uses one connection to communicate with a particular process of the plurality of processes in the first domain,

wherein the connection concentrator is associated with a plurality of listeners, and wherein each listener operates to

receive a request for a connection between a first process in the first domain and a second process in the second domain,

determine which handler handles the connection by first checking to see if any handler currently handles the connection to the first process in the first domain, wherein the listener chose a least burdened handler to handle the connection if no handler currently handles the connection, and

hash a host/port associated with the connection in a data structure and looks in the data structures to determine whether the host/port is already in use, wherein identification information for the handler is returned if a host/port is in use and not at a multiplex user limit, and

wherein the connection concentrator switches the handler to an appropriate context for a particular type associated with the connection, wherein the connection is at least one of a bi-directional connection, a paired second connection, and an outbound connection.

2. The system of claim 1, further comprising:

another connection concentrator that allows the plurality of processes in the first domain to communicate with the plurality of processes in the second domain, wherein the another connection concentrator communicates with each one of the plurality of processes in the first domain and uses one connection to communicate with any one of the plurality of processes in the second domain.

3. The system of claim 1, wherein:

a connection between one of the plurality of processes in the first domain and the plurality of processes in the second domain through the connection concentrator is initiated from within the first domain.

4. The system of claim 1, wherein:

a connection between one of the plurality of processes in the first domain and the plurality of processes in the second domain through the connection concentrator is initiated from within the second domain.

5. The system of claim 1, wherein:

a connection between one of the plurality of processes in the first domain and the plurality of processes in the second domain through the connection concentrator is asymmetric.

6. The system of claim 1, wherein:

a connection between one of the plurality of processes in the first domain and the plurality of processes in the second domain through the connection concentrator is symmetric.

7. The system of claim 1, wherein:

the connection concentrator uses a remote connection to communicate with a first process in the first domain, and a local connection to communicate with a second process in the second domain.

8. The system of claim 1, wherein:

a handler updates an activity timestamp field for the connection, and a listener operated to timeout the connection if no activity takes place within a user specified time period.

9. The system of claim 8, wherein:

a listener marks the connection as closed and removes a host/port entry, and the handler operates to disconnect the connection when said handler sees the connection has been marked as closed.

10. The system of claim 1, wherein:

the first process operates to connect to a handler and create a persistent subscription to an event, wherein the first process then disconnects from the handler, and the first process is provided with events for that persistent subscription once the first process reconnects to a handler associated with the connection concentrator.

11. A method of connection management to achieve scalability for domain computing, comprise:

managing, via a connection concentrator, connections between a plurality of domains, wherein each domain of the plurality of domains comprises a collection of machines and resources that are administrated as a unit;

using, via the connection concentrator, a plurality of handlers to handle communication between a plurality of processes in a first domain in the plurality of domains and a plurality of processes in a second domain in the plurality of domains, wherein each handler associated with the connection concentrator uses a plurality of connections to communicate with the plurality of processes in the second domain and uses one connection to communicate with a particular process of the plurality of processes in the first domain;

associating a plurality of listeners with the connection concentrator, wherein each listener operates to

receive a request for a connection between a first process in the first domain and a second process in the second domain,

determine which handler handles the connection by first checking to see if any handler currently handles the connection to the first process in the first domain, wherein the listener chose a least burdened handler to handle the connection if no handler currently handles the connection, and

hash a host/port associated with the connection in a data structure and looks in the data structures to determine whether the host/port is already in use, wherein identification information for the handler is returned if a host/port is in use and not at a multiplex user limit; and

switching, via the connection concentrator, the handler to an appropriate context for a particular type associated with the connection, wherein the connection is at least one of a bi-directional connection, a paired second connection, and an outbound connection.

12. A non-transitory machine readable storage medium having instructions stored thereon that when executed by one or more processors cause a system to:

manage, via a connection concentrator, connections between a plurality of domains, wherein each domain of the plurality of domains comprises a collection of machines and resources that are administrated as a unit;

use, via the connection concentrator, a plurality of handlers to handle communication between a plurality of processes in a first domain in the plurality of domains and a plurality of processes in a second domain in the plurality of domains, wherein each handler associated with the connection concentrator uses a plurality of connections to communicate with the plurality of processes in the second domain and uses one connection to communicate with a particular process of the plurality of processes in the first domain; and

associate a plurality of listeners with the connection concentrator, wherein each listener operates to

receive a request for a connection between a first process in the first domain and a second process in the second domain,

determine which handler handles the connection by first checking to see if any handler currently handles the connection to the first process in the first domain, wherein the listener chose a least burdened handler to handle the connection if no handler currently handles the connection, and

hash a host/port associated with the connection in a data structure and looks in the data structures to determine whether the host/port is already in use, wherein identification information for the handler is returned if a host/port is in use and not at a multiplex user limit; and

switch, via the connection concentrator, the handler to an appropriate context for a particular type associated with the connection, wherein the connection is at least one of a bi-directional connection, a paired second connection, and an outbound connection.