Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
  • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
  • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F15/00—Digital computers in general; Data processing equipment in general
  • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
  • G06F15/163—Interprocessor communication
  • G06F15/173—Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
  • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
  • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
  • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04J—MULTIPLEX COMMUNICATION
  • H04J3/00—Time-division multiplex systems
  • H04J3/22—Time-division multiplex systems in which the sources have different rates or codes
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2209/00—Indexing scheme relating to G06F9/00
  • G06F2209/50—Indexing scheme relating to G06F9/50
  • G06F2209/5011—Pool

Definitions

• connection pool such as a Java Database Connectivity (JDBC) connection pool is provided by the application server.
• JDBC Java Database Connectivity
• the connection pool provides a number of already set up connections with a database. These connections are provided to applications of the application server as needed.
• Such connection pools allow for a relatively large number of applications in the application server to access a database while reducing the database connection time for the application.
• Figure 1 is a diagram illustrating the use of a multipool with a multipool manager of one embodiment.
• Figures 2A-2B are diagrams illustrating the use of a multipool manager having an active connection pool list.
• Figures 3A-3B are flowcharts that illustrate the use of an active connection pool list of one embodiment.
• Figure 4 is a diagram illustrating the operation of a multipool manager of one embodiment of the present invention.
• Figures 5A-5B are diagrams that illustrate the use of callbacks with a multipool manager of embodiments of the present invention.
• Figure 6 is a flowchart illustrating the use of callbacks with a multipool manager of one embodiment of the present invention.
• FIG. 1 is a diagram that illustrates the operation of a multipool manager 102.
• the database instances 104 and 106 can each contain a current version of a database run on independent machines, for example.
• connection pool 108 and connection pool 110 When there are multiple database instances, it can be desirable to use multiple connection pools, such as connection pool 108 and connection pool 110.
• a multipool system can be used. In a multipool system, a multipool manager 102 can determine which connection pool to use to obtain a connection for an application into the database system.
• Diffferent methods for selecting a connection pool are possible.
• One selection method has a primary connection pool and a backup connection pool. The connections are first attempted at a primary connection pool and then upon failure event, the connections are then sent through a backup connection pool.
• Another method is a load balancing method where the connections are distributed between multiple connection pools to balance the load at the different connection pools.
• a round-robin method is an example of a load balancing method.
• One embodiment of the present invention comprises a multipool system to connect to database instances comprising multiple connection pools 202 and 204.
• the connection pools 202 and 204 are adapted to provide connections to database instances 206 and 208.
• a multipool manager 210 is adapted to select and set up connections to a database instance through a connection pool.
• the multipool manager 210 is adapted to keep track of dead connection pools between requests for conections.
• the multipool manager 210 can select a connection pool in a manner that avoids any dead connection pools. For the example of figure 2A, the multipool manager can avoid selecting connection pool A if it is dead.
• a selection of only non-dead connection pools is done as authorized by an application. hi one embodiment, the application indicates by a callback or by configuration info whether to switch connection pools.
• the multipool manager 210 can be adapted to maintain a list 212 of active connection pools and to use the list 212 to determine what connection pool to connect through.
• list is not meant to imply any specific data structure.
• the active connection pools on the list can include those connection pools that are not those connection pools determined by the multipool manager to be dead.
• Dead connection pools can be tested in the background to see whether they should be returned to the active connection pool list.
• the list of active connection pools can be a subset of a candidate list provided by an application. Alternatively, separate candidate lists and active lists can be maintained, and the multipool manager can select a connection pool that is on both lists.
• the multipool manager 210 can store an indication for each connection pool associated with the candidate list indicating whether the connnection pool is active or dead.
• connection pool A is dead, thus not on the active connection pool list 212.
• An application such as an application 220, can request a connection into one of the database instances 206 or 208 through the multipool manager 210.
• the multipool manager 210 selects a connection through the connection pool
• the multipool manager 210 can test whether a connection pool has been revived in the background asynchronously.
• an asychronous background test module 214 can be used.
• Figure 2B illustrates an example of this background testing.
• a SQL test query is sent to the dead connection pool A. If the correct answer is obtained from the database instance 206, the multipool manager 210 can update the active connection pool list
• connection pool A a connection through the connection pool A is possible.
• Figure 3B illustrates a flowchart illustrating the asynchronous testing of a dead connection pools.
• preset wait time passes in step 300.
• the wait time can be set by an application and stored with the coiifigureation information for the multipool manager or a default value can be used
• step 302 the dead connection pool is tested. If the dead connection pool has revived as indicated by the test, the active connection pool list 306 is updated, otherwise, the cycle repeats waiting the preset time in step 300.
• Figure 3 A illustrates the operation of the request for a connection to a database in one embodiment, hi step 308, a request for connection to the database is received at a multipool manager, hi step 310, the multipool manager can select a connection pool.
• the multipool manager 210 selects a connection pool on an active connection pool list.
• the connection can then be attemped. hi step 312, it is checked whether the connection pool is dead. If the connection pool is dead, in step 314, the active connection pool list is updated and new connection pool is selected from the active pool list. If the connection pool is not dead, in step 315, it is checked to see whether the connection pool is full. If there is no available connections, then the multipool manager can select another connection pool from the active connection pool list, in step 310. If any selected connection pool is not dead or full, then, in step 316, the connection is done through the selected connection pool.
• FIG. 4 is a flowchart illustrating different conditions that can occur in one embodiment of the present invention, hi step 402, a request for a connection to the database is received at a multipool manager, hi step 404 a multipool manager selects a connection pool from the active pool list. Its possible, as determined in step 408, that the selected connection pool is a newly revived connection pool. If so, this is called a failback as indicated in step 410. In step 412, it is checked whether the connection pool is dead.
• connection pool list is updated in step 414, and in step 416, another connection pool is selected from the active connection pool list, this is called a failover condition, hi step 418, if the connection pool is not dead it is checked to see whether the connection pool is full. If the connection pool is full, in step 420, it is checked to see whether a spillover is allowed. If it is, in step 422 another connection pool is selected from the active connection pool list. Step 424, shows a connection is made. As described below an application may authorize a failback, failover or spillover condition with a callback or with config information.
• One embodiment of the present invention is a multipool manager adapted to select and set up connections to a database instance through a connection pool.
• the multipool manager is adapted to keep track of dead connection pools.
• the multipool manager implements a selection method in which the multipool manager avoids selecting dead connection pools to provide a connection for an appplication.
• One embodiment of the present invention is a multipool system to connect to database instances comprising multiple connection pools.
• the connection pools are adapted to provide connections to database instances.
• a multipool manager is adapted to select and set up connections to a database instance through a connection pool.
• the multipool manager is adapted to keep track of dead connection pools and to asynchronously test whether a connection pool is revived.
• the multipool manager implements callbacks to an application in order to get authorization from the application for a switch of connection pools.
• a multipool system is used to connect to database instances with multiple connection pools.
• the connection pools 502 and 504 are adapted to provide connections to database instances 508 and 510.
• a multipool manager 506 is adapted to select and set up connections to a database instance through a connection pool.
• the multipool manager 506 is adapted to check with an application 512 before switching connection pools. In the example of figure 5A 3 a callback is available from the multipool manager 506 to the application 512. If the connection pool is to be switched, the multipool manager 506 can do a callback to the application 512 to determine whether the application will authorize the switch.
• the active connection pool list includes connection pool B but not connection pool A.
• a request for connection is received by the multipool manager 506.
• a callback is done to the application 512.
• the callback can be, for example, the calling of the callback method 514 which is part of the application 512.
• the multipool manager 506 can store configuration information 506a which may include an indication of what conditions the callback is to be sent and/or an indication of the callback method name, in this case, callback method A.
• the application code can implement a callback method 514 in any manner.
• a callback response is received by the multipool manager in step 3.
• the callback response can be an indication which multipool manager 506 can use to determine how to connect.
• the callback response indications include an "OK" indication.
• the multipool manager switches to the new connection pool.
• Another callback response indication is a "retry” indication. If a "retry” indication is received, the multipool manager 506 can attempt to get a connection with the old connection pool.
• Another possible callback response indication is a "don't reconnect” indication. When a "don't reconnect” indication is received the multipool manager not attempt to make a connection.
• Figure 5B illustrates a possible reason that a "retry" indication might be provided by the callback method. In one example, it may be desirable to do a certain number of attempts onto a primary database instance before switching over to a secondary database instance.
• Figure 5B illustrates an example in which an independent ping is done from the application 512 to the database insta ⁇ ice . 508 as part of the callback method. If the independent ping comes up with an indication that the database instance 508 is still running, the application can send a "retry" indication. If the application 512 is sufficiently convinced that the database instance is down, a "OK" callback response can be sent.
• any callback method can be implemented by the application 512.
• the multipool manager has a callback interface that can be implemented by any application code.
• Figure 6 is a diagram illustrating the operation of callbacks of one embodiment, hi step 602, it is checked if the connection pool switched as determined by the multipool manager. If the connect pool is not to be switched,; the connection is done to the connection pool in step 604. If the connection is to be switched, then in step 606, it is checked whether a callback is indicated for the condition. If no callbacks is indicated, then the connection is done through the new connection pool without a callback- If a callback is indicated, in step 610, a callback is done. If an "OK" indication is received, the connection is done with the new connection pool in step 614. If a retry indication is received, a connection is attempted to be done using the old connection pool, in step 616.
• a multipool manager is adapted to select and set up connections to a database instance through a connection pool.
• the multipool manager is adapted to check with an application before switching connection pools.
• MultiPools can check with the application before failing over to alternate Pools. This is useful if the configured test for the Pool currently in use encounters a random or transient failure, if the application wants to control when a Database Management System (DBMS) instance that's currently not handling clients is brought back into service or if applications can specified an identity when getting connections from Pools, and connections from a matching pool should be returned. This is useful in cases where the DBMS vendor does not provide native support for setting client identities on anonymous JDBC connections. A number of improvements can be implemented for multipools.
• DBMS Database Management System
• FAILOVER - Existing MultiPool algorithm "HIGH_AVAILABILITY" will be renamed as “FAJLOVER”. It will also optionally provide the ability to route application requests for connections to alternative Pools if the current Pool is busy.
• HEALTH - Existing functionality will be improved to mark dead Pools so that application requests for connections are not routed to these Pools.
• CALLBACK - A callback interface will be provided to applications to control MultiPool decision to failover to alternative Pools when a failed Pool is detected, or to fail back to Pools previously marked dead.
• FAILOVER can have connections sent through a primary connection pool and have these connections routed through a secondary connection pool upon the failure of the primary connection pool. FAILOVER can optionally also be able to route application requests for connections to alternative Pools if the current Pool is busy.
• applications will also be able to configure the following MultiPool attribute:
• MultiPool can be able to implement and register a callback with the system. This callback can be invoked when the MultiPool detects a dead or busy Pool, giving application the ability to control whether MultiPool fails over to an alternative Pool or not.
• applications will be able to implement the following interface:
• WebLogic Server will invoke this interface ' s * method “allowPoolFailover ( ) " and take different actions depending upon
• Multipools can be enhanced to internally monitor and track the health of the Pools underneath. If a Pool is determined to be dead, it will be marked so and subsequent application requests for connections will not be routed to that Pool.
• applications will be able to configure the following JDBCMultiPoolMBean attribute:
• Embodiments may be implemented using a conventional general purpose or a specialized digital computer or microprocessor(s) programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art.
• Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.
• the invention may also be implemented by the preparation of integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be readily apparent to those skilled in the art.
• One embodiment includes a computer program product which is a storage medium
• the storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, micro drive, and magneto-optical disks, ROMs, Rams, EPROM's, EPROM's, Drams, Rams, flash memory devices, magnetic or optical cards, Nan systems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
• the present invention includes software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention.
• software may include, but is not limited to, device drivers, operating systems, execution environments/containers, and user applications.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Software Systems (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• Computer Hardware Design (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mathematical Physics (AREA)
• Multimedia (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
• Hardware Redundancy (AREA)
• Stereo-Broadcasting Methods (AREA)
• Compression Or Coding Systems Of Tv Signals (AREA)

Priority Applications (3)

Applications Claiming Priority (6)

Publications (2)

Family

ID=36647997

Family Applications (1)

Country Status (5)

Cited By (7)

Family Cites Families (5)

• 2005
  • 2005-12-21 KR KR1020077017651A patent/KR20070110011A/ko not_active Application Discontinuation
  • 2005-12-21 JP JP2007549495A patent/JP2008525916A/ja active Pending
  • 2005-12-21 EP EP05855184A patent/EP1844395A4/en not_active Withdrawn
  • 2005-12-21 AU AU2005323039A patent/AU2005323039B2/en active Active
  • 2005-12-21 WO PCT/US2005/046581 patent/WO2006073865A2/en active Application Filing

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events