Server-side connection resource pooling

• US 8,713,186 B2
• Filed: 03/12/2008
• Issued: 04/29/2014
• Est. Priority Date: 03/13/2007
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Chidambaran, Lakshminarayanan, Krishnaswamy, Srinath, Itikarlapalli, Krishna Mohan, Neel, Kevin, Seshadri, Sreekumar K., Giloni, Jonathan, McKinley, Scot, Thammaiah, Ravi
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US12/047,278
• Publication Number:
  US 20080228923A1
• Time in Patent Office: 2,239 Days
• Field of Search: 709/225, 709/227, 709/237
• US Class Current: 709/227
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/562 Brokering proxy services

Abstract

A server side connection pool provides pooling of server connections. Thus, client side processes do not create groups of dedicated resources. Clients are provided the capability to communicate to a server side connection broker process to GET a pooled server connection comprising connection state plus a thread of execution for doing some work, whereby requesting the work can bypass the connection broker process and go directly to the assigned pooled connection. Once the client issues a RELEASE to release the pooled connection back to the pool, a completely different client process on potentially a different client middle tier machine can reuse the same pooled connection. The server-side connection pool can be logically partitioned into sub-pools that correspond to connection classes that typically correspond to respective applications. A client process can request a pooled connection having a particular state, where a stored procedure can be executed to generate such state.

Claims

1. A method comprising:

receiving, at a server-side connection broker from a client process, a request for a connection to a server, said request for a connection being sent via a network transport connection between the client process and the server-side connection broker;

in response to said request,

said server-side connection broker selecting a server connection from a pool of server connections, wherein said server connection comprises a thread of execution;

handing-off said network transport connection between the client process and the server-side connection broker to the server connection to (1) establish said server connection to be an end point for said network transport connection and to (2) bypass said server-side connection broker within said network transport connection while said server connection is the end point of said network transport connection;

receiving, at said server connection and from said client process via said network transport connection, a request for one or more server operations; and

said server connection performing said one or more server operations and returning a corresponding result to said client process via said network transport connection; and

after said result is returned, handing-back said network transport connection to said server-side connection broker to establish the server-side connection broker to be the end point for said network transport connection and cause said server-side connection broker to listen for further requests via said network transport connection.

2. The method of claim 1, wherein said pool is logically partitioned into a plurality of sub-pools, and wherein each sub-pool is associated with a respective connection class.

3. The method of claim 2, wherein said request for a server connection is a first request for a server connection and is received via a first network transport connection from a first client process associated with a particular application, said method further comprising:

receiving, at said server-side connection broker via a second network transport connection from a second client process associated with said particular application, a second request for a server connection, wherein said second request identifies a particular connection class;

in response to said second request and based on said particular connection class;

said server-side connection broker selecting a server connection from a particular sub-pool associated with said particular connection class; and

handing-off said second network transport connection to the selected server connection.

4. The method of claim 2, wherein said request for a server connection is a first request for a server connection and is received via a first network transport connection from a first client process associated with a particular application, said method further comprising:

associating with said server connection a particular connection class that corresponds to said particular application;

after said first client process releases said server connection back to said pool, receiving, at said server-side connection broker via a second network transport connection and from a second client process associated with said particular application, a second request for a server connection, wherein said second request identifies said particular connection class; and

in response to said second request and based on said particular connection class, handing-off said second network transport connection to the server connection.

5. The method of claim 1, wherein said request for a connection is a request for a server operation and not an explicit request for a server connection.

6. The method of claim 1, wherein said server connection is associated with a corresponding server connection state data structure with which server connection state is maintained for said server connection.

7. The method of claim 6, wherein said request for a server connection is a first request for a server connection and is received via a first network transport connection from a first client process associated with a particular application, and wherein after said first client process releases said server connection back to said pool, said server connection state data structure represents a first server connection state of said server connection, said method further comprising:

receiving, at said server-side connection broker via a second network transport connection and from a second client process associated with said particular application, a second request for a server connection; and

in response to said second request, handing-off said second network transport connection to the server connection, wherein said server connection state data structure represents said first server connection state of said server connection.

8. The method of claim 6, wherein said request for a server connection is a first request for a server connection and is received via a first network transport connection from a first client process associated with a particular application, and wherein after said first client process releases said server connection back to said pool, said server connection state data structure represents a first server connection state of said server connection, said method further comprising:

receiving, at said server-side connection broker via a second network transport connection and from a second client process associated with said particular application, a second request for a server connection, wherein said second request comprises a request for a server connection having an initialization server connection state;

in response to said second request, said server connection modifying said server connection state data structure to represent an initialization server connection state; and

handing-off said second network transport connection to the server connection, wherein said server connection is associated with said server connection state data structure that represents said initialization server connection state and said server connection still comprises said thread of execution.

9. The method of claim 6, wherein said request for a server connection is a first request for a server connection and is received via a first network transport connection from a first client process associated with a particular application, and wherein after said first client process releases said server connection back to said pool, said server connection state data structure represents a first server connection state of said server connection, said method further comprising:

receiving, at said server-side connection broker via a second network transport connection and from a second client process associated with said particular application, a second request for a connection, wherein said second request comprises a request for a server connection having a second server connection state that is different from said first server connection state;

in response to said second request;

said server connection modifying said server connection state data structure to represent said second server connection state by executing a stored machine-executable procedure associated with said particular application; and

handing-off said second network transport connection to the server connection.

10. The method of claim 1,

via said network transport connection, said server-side connection broker receiving a certain message from said client process for a server operation;

and

wherein a second message is piggybacked to said certain message, said second message requesting a server connection for said client process.

11. The method of claim 1, further comprising:

said server-side connection broker associating a network connection state with said network transport connection;

said server connection handing-off said network transport connection to said server-side connection broker;

said server-side connection broker receiving via said network transport connection a certain request from said client process for a server operation; and

said server-side connection broker selecting a certain server connection for said client process based on said network connection state.

12. The method of claim 11,

wherein said pool is logically partitioned into a plurality of sub-pools;

and

wherein the the method further includes selecting, based on said network connection state, a sub-pool from which to select a server connection to associate with the said client process.

13. The method of claim 1, further including:

via said network transport connection, said server-side connection broker receiving a certain message from said client process for a server operation; and

wherein a second message is piggybacked to said certain message, said second message requesting to release a server connection for said client process.

14. The method of claim 1, further including in response to a period of time elapsing without receiving a request for a certain operation from said client, reclaiming said server connection for said client process.

15. The method of claim 1, further including receiving from said client process a certain message via a one way remote procedure call, said message requesting to release said server connection.

16. The method of claim 1, further including:

receiving a release message from said client process to release said server connection,

in response to receiving said release message, retaining an association between said client process and said server connection.

17. The method of claim 16, wherein the step of retaining includes retaining cached state that corresponds to a tight coupling between said client process and said server connection.

18. The method of claim 16, further including:

reclaiming said server connection that was retained; and

subsequent to reclaiming, receiving a certain message from said client process to perform a server operation; and

in response to receiving said certain message, returning another message indicating that said server connection is not associated with said client process.

19. The method of claim 1, wherein the server-side connection broker runs on the server.

20. A non-transitory computer-readable storage medium storing instructions which, when executed by one or more processors, cause said one or more processors to perform steps comprising:

receiving, at a server-side connection broker from a client process, a request for a connection to a server, said request for a connection being sent via a network transport connection between the client process and the server-side connection broker;

in response to said request,

said server-side connection broker selecting a server connection from a pool of server connections, wherein said server connection comprises a thread of execution;

handing-off said network transport connection between the client process and the server-side connection broker to the server connection to (1) establish said server connection to be an end point for said network transport connection and to (2) bypass said server-side connection broker within said network transport connection while said server connection is the end point of said network transport connection;

receiving, at said server connection and from said client process via said network transport connection, a request for one or more server operations; and

said server connection performing said one or more server operations and returning a corresponding result to said client process via said network transport connection; and

after said result is returned, handing-back said network transport connection to said server-side connection broker to establish the server-side connection broker to be the end point for said network transport connection and cause said server-side connection broker to listen for further requests via said network transport connection.

21. The non-transitory medium of claim 20, wherein said pool is logically partitioned into a plurality of sub-pools, and wherein each sub-pool is associated with a respective connection class.

22. The non-transitory medium of claim 21, wherein said request for a server connection is a first request for a server connection and is received via a first network transport connection from a first client process associated with a particular application, whether the instructions which, when executed by one or more processors, cause said one or more processors to further perform:

receiving, at said server-side connection broker via a second network transport connection from a second client process associated with said particular application, a second request for a server connection, wherein said second request identifies a particular connection class;

in response to said second request and based on said particular connection class;

said server-side connection broker selecting a server connection from a particular sub-pool associated with said particular connection class; and

handing-off said second network transport connection to the selected server connection.

23. The non-transitory medium of claim 21, wherein said request for a server connection is a first request for a server connection and is received via a first network transport connection from a first client process associated with a particular application, whether the instructions which, when executed by one or more processors, cause said one or more processors to further perform:

associating with said server connection a particular connection class that corresponds to said particular application;

after said first client process releases said server connection back to said pool, receiving, at said server-side connection broker via a second network transport connection and from a second client process associated with said particular application, a second request for a server connection, wherein said second request identifies said particular connection class; and

in response to said second request and based on said particular connection class, handing-off said second network transport connection to the server connection.

24. The non-transitory medium of claim 20, wherein said request for a connection is request for a server operation and not an explicit request for a server connection.

25. The non-transitory medium of claim 20, wherein said server connection is associated with a corresponding server connection state data structure with which server connection state is maintained for said server connection.

26. The non-transitory medium of claim 20, whether the instructions which, when executed by one or more processors, cause said one or more processors to further perform:

said server-side connection broker associating a network connection state with said network transport connection;

said server connection handing-off said network transport connection to said server-side connection broker;

said server-side connection broker receiving via said network transport connection a certain request from said client process for a server operation; and

said server-side connection broker selecting a certain server connection for said client process based on said network connection state.

27. The non-transitory medium of claim 20, wherein the server-side connection broker runs on the server.