System and method for using a gridlink data source to connect an application server with a clustered database

• US 9,092,460 B2
• Filed: 06/24/2011
• Issued: 07/28/2015
• Est. Priority Date: 09/15/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Somogyi, Alex, Revanuru, Naresh, Irudayaraj, Rajkumar, Felts, Stephen, Zhou, Tong, Zhao-Perez, Frances
• Primary Examiner(s): Keehn, Richard G
• Application Number:
  US13/168,506
• Publication Number:
  US 20120066363A1
• Time in Patent Office: 1,495 Days
• Field of Search: 709/223
• US Class Current: 1/1
• CPC Class Codes: G06F 15/17318 Parallel communications techniques, e.g. gather, scatter, reduce, roadcast, multicast, all to all
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 49/358 Infiniband Switches
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: Y10T 409/308904 : Multiple row dividing head
• CPC Class Codes: Y10T 409/309072 : including cutter limited to rotary motion
• CPC Class Codes: Y10T 409/309128 : with means to adjust work support vertically
• CPC Class Codes: Y10T 409/309352 : Cutter spindle or spindle support
• CPC Class Codes: Y10T 409/309408 : with cutter holder

Abstract

A system and method can support using a data source to connect an application server with a clustered database. The clustered database includes a plurality of database instances and is associated with a notification service. The notification service can be used by the clustered database to broadcast notifications that describe a state change in the plurality of database instances. The data source includes a connection pool, which manages a set of connections to the plurality of database instances in the clustered database. The data source operates to register with the notification service to receive notifications on the change of the clustered database, wherein the application server operates to configure and manage connection to the clustered database, adaptively according to the state change of the clustered database at run time.

Claims

1. A system to support connecting an application server with a clustered database, comprising:

an application server operating on one or more microprocessor;

a clustered database having a heterogeneous plurality of data providers;

a notification service operating on the clustered database;

wherein the notification service is used by the clustered database to broadcast notifications that describe a state change in the clustered database;

a single data source operating on the application server wherein the single data source operates to connect the application server with the clustered database, and wherein the single data source comprises a connection pool which manages a heterogeneous set of connections to the heterogeneous plurality of data providers in the clustered database, wherein particular connections of said heterogeneous set of connections are configured for connecting to particular data providers of said heterogeneous plurality of data providers;

wherein the single data source registers with the notification service of the clustered database to receive said notifications that describe a state change in the clustered database;

wherein the single data source receives, from the notification service of the clustered database, notifications that describe a state change in the clustered database; and

wherein, in response to receiving said notifications that describe a state change in the clustered database, the single data source configures said connection pool to manage said heterogeneous set of connections between the application server and the heterogeneous plurality of data providers in the clustered database adaptively according to the state change of the clustered database at run time.

2. The system according to claim 1, wherein:

the state change of the clustered database includes one of;

one or more data providers have been stopped or taken out by an unplanned outage, and

a data provider is added in or restarted after an outage.

3. The system according to claim 1, wherein:

the single data source provides database fast connection failover capabilities and responds to database service events to ensure each connection of said heterogeneous set of connections is valid.

4. The system according to claim 1, wherein:

the single data source operates to use metrics to monitor actions taken by the application server.

5. The system according to claim 1, wherein:

the single data source operates to poll the heterogeneous set of connections to the plurality of data providers in the clustered database as an alternative to the notification service.

6. The system according to claim 1, wherein:

the single data source operates to receive notifications from the notification service that contain load balancing advisory events.

7. The system according to claim 1, further comprising:

the single data source ensures that all database operation within context of a global transaction are directed to a same database instance.

8. The system according to claim 1, further comprising:

the single data source supports a planned shut down operation of a targeted database instance in the clustered database.

9. The system according to claim 8, wherein:

the single data source allows any in progress transactions to complete before closing and recreating one or more physical connections.

10. The system according to claim 8, wherein:

the single data source cleans up idle connections so that new requests for connections are not sent to the targeted database instance in the clustered database.

11. A method to support connecting an application server with a clustered database having a heterogeneous plurality of data providers, said method comprising:

providing an application server operating on one or more microprocessor;

providing a notification service operating on a clustered database;

wherein the notification service is used by the clustered database to broadcast notifications that describe a state change in the clustered database;

providing single a data source on the application server wherein the single data source operates to connect the application server with the clustered database, and wherein the single data source comprises a connection pool which manages a heterogeneous set of connections to the heterogeneous plurality of data providers in the clustered database, wherein particular connections of said heterogeneous set of connections are configured for connecting to particular data providers of said heterogeneous plurality of data providers;

registering the single data source with the notification service of the clustered database to receive said notifications that describe a state change in the clustered database;

receiving with the single data source, from the notification service of the clustered database, notifications that describe a state change in the clustered database; and

wherein, in response to receiving said notifications that describe a state change in the clustered database, the single data source configures said connection pool to manage said heterogeneous set of connections between the application server and the heterogeneous plurality of data providers of the clustered database adaptively according to the state change of the clustered database at run time.

12. The method of claim 11, wherein the state change of the clustered database includes one of:

one or more data providers have been stopped or taken out by an unplanned outage, and

a data provider is added in or restarted after an outage.

13. The method of claim 11, wherein:

the single data source provides database fast connection failover capabilities and responds to database service events to ensure each connection of said heterogeneous set of connections is valid.

14. The method of claim 11, wherein:

the single data source operates to receive notifications from the notification service that contain load balancing advisory events.

15. The method of claim 11, wherein:

the single data source ensures that all database operations within context of a global transaction are directed to a same database instance.

16. The method of claim 11, wherein:

the single data source supports a planned shut down operation of a targeted database instance in the clustered database.

17. The method of claim 11, wherein:

the single data source supports a planned shut down operation of a targeted database instance in the clustered database by allowing any in progress transactions to complete before closing and recreating one or more physical connections.

18. The method of claim 11, wherein:

the single data source supports a planned shut down operation of a targeted database instance in the clustered database; and

the single data source cleans up idle connections so that new requests for connections are not sent to the targeted database instance in the clustered database.

19. A non-transitory computer readable storage medium including instructions stored thereon for supporting connecting an application server with a clustered database having a heterogeneous plurality of data providers, wherein said instructions, when executed cause a computer system to perform steps comprising:

providing an application server operating on one or more microprocessor;

providing a notification service operating on a clustered database;

wherein the notification service is used by the clustered database to broadcast notifications that describe a state change in the clustered database;

providing a single data source on the application server wherein the single data source operates to connect the application server with the clustered database, and wherein the single data source comprises a connection pool which manages a heterogeneous set of connections to the heterogeneous plurality of data providers in the clustered database, wherein particular connections of said heterogeneous set of connections are configured for connecting to particular data providers of said heterogeneous plurality of data providers;

registering the single data source with the notification service of the clustered database to receive said notifications that describe a state change in the clustered database;

receiving with the single data source, from the notification service of the clustered database, notifications that describe a state change in the clustered database; and

wherein, in response to receiving said notifications that describe a state change in the clustered database, the single data source configures said single data source to manage said heterogeneous set of connections between the application server and the heterogeneous plurality of data providers of the clustered database adaptively according to the state change of the clustered database at run time.

20. A non-transitory computer readable storage medium of claim 19, wherein:

the single data source provides database fast connection failover capabilities and responds to database service events to ensure each connection of said heterogeneous set of connections is valid.