WO2004059906A1 - Procede d'administration de connexions a une base de donnees - Google Patents
Procede d'administration de connexions a une base de donnees Download PDFInfo
- Publication number
- WO2004059906A1 WO2004059906A1 PCT/CN2003/001016 CN0301016W WO2004059906A1 WO 2004059906 A1 WO2004059906 A1 WO 2004059906A1 CN 0301016 W CN0301016 W CN 0301016W WO 2004059906 A1 WO2004059906 A1 WO 2004059906A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- connection
- transaction
- database
- pool
- connections
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
Definitions
- connection management includes the management of establishing, using, and closing connections. At the beginning, because the database is accessed infrequently, traditional connection management adopts the strategy of establishing and closing when needed, mainly divided into distributed transactions and worker threads. 2 A way of management.
- the transaction mode only provides a method for managing distributed transactions, internalizing the application into global transactions, and transforming the application's use of connections into acquiring and closing connections through global transactions.
- US Patent No. 333141 filed on June 14, 1999, discloses a method for supporting distributed transactions using the JDBC1.0 driver, which provides a JDBC1.0-based support The method of distributed transactions is not to allocate a new physical connection for each connection request, but to maintain a mapping table internally for global transactions and the connections they use. Because this method is transaction-based, in this method, transaction acquisition and closing connections do not have an effective use of the connection, so even if there are multiple connection requests to the database in a transaction, the same connection is still maintained. Use, causing waste of resources.
- US Patent No. 611604 filed on July 7, 2000, discloses a method and system for managing the connection of a database management system.
- Each database management system corresponds to a database system, and a series of working threads are built therein.
- Distributing database requests to these worker threads for execution also includes connecting specific connections, worker threads and used database subsystems.
- This threading method makes full use of the advantages of computer thread management, greatly improves the execution efficiency, and greatly improves the application performance.
- this method is thread-based, and in this way, the thread acquires and closes the connection. There is no effective use of connections. Therefore, once the same worker thread calls to the same database subsystem, the same connection is still used, causing inefficiency.
- connection management technologies has the following defects, respectively: 1) The use of the same connection by the same worker thread to the same subsystem or the same transaction to the same connection of the database is equal to the allocation of the application or sub-application A fixed connection, regardless of the actual use of the connection, does not manage the connection as a whole, making the connection use inefficient; 2) there is a connection established and closed, but there is no condition for judging the need to establish and close the connection There are no methods and strategies for establishing, distributing, using, and recycling connections, so there is no reasonable use Connections; 3) Connections cannot be reused; 4) Management of allocating and reclaiming connections is not involved.
- the technical problem to be solved by the present invention is to provide a database connection management method that can overcome the shortcomings of the prior art.
- the module packaging technology, connection pool design mode, connection management method, and transaction processing method are used to restore the common connection. Consistent management of application and transaction connections provides effective methods, so that connections can be reused and used reasonably, reducing the handshake overhead of connection building and improving database efficiency; ensuring the consistency of transaction connections in the method of forming transactions; reducing The coupling of the details of the database establishment link makes the module easy to maintain; it provides connection management guarantee for secure, high reliability and high performance applications.
- the module encapsulation technology refers to encapsulating a series of strategies for connection resource allocation, reuse, and connection pool initialization in a module.
- connection pool for storing database connections, and configure the number of connection generations and the maximum reusable number of each connection that should be placed when the connection pool is initialized;
- connection pool for each ordinary connection request, establishment and allocation are made so that they can be reused;
- connection pool a transaction processing method is used to establish, allocate, and use a transaction connection. To maintain its uniqueness, consistency, and support for nested transactions;
- connection pool the used database connection is recycled so that it can be reused.
- initialization includes the following steps:
- the step (1.3) includes the following steps: determining whether there is an idle connection in the connection pool, and if there is an idle connection, directly assigning the connection and starting to reference the count; if not, Then it is judged whether there is a connection that can be reused, if there is a reusable connection, it is directly allocated to the connection with the smallest reference count, and the reference count of the connection is incremented; otherwise, a new connection is established and allocated, and the connection is initialized at the same time .
- the step (1.4) includes the steps of starting a transaction to obtain a connection, and submitting and rolling back a transaction to dry the connection.
- the step (1.5) includes the following steps: determining whether the connection pool is full, such as closing the connection if the connection pool is full; otherwise, putting the connection into the connection pool.
- the database connection and connection management are sealed.
- a count and Each connection is configured with a maximum reusable number, which is to increase the reference count of the connection each time an ordinary connection is used; select the connection with the smallest reference count as the available connection, and when the connection reference count is less than the maximum
- the reusable number is judged to be a reusable connection.
- the number of connection generations to be placed when the connection pool configuration is initialized is determined.
- the number of connections in the connection pool is less than the above configuration number, it is determined that the connection pool is not full.
- the step of starting a transaction includes determining whether a connection already exists in the transaction. If a connection exists, the connection is still allocated and its nesting level count is incremented; otherwise, it is determined whether there is an idle connection. If there are idle connections, allocate idle connections; otherwise, establish and allocate new connections.
- the step of committing and rolling back the transaction includes judging whether it belongs to a nested transaction, and if it belongs, the nesting level of the connection is decremented; otherwise, the transaction is rolled back; wherein the rollback transaction includes the following steps:
- a transaction registry is provided for each transaction connection, and the correspondence relationship between the thread number where the transaction initiator is located and the connection used by the transaction is registered in the transaction registry when it is established, and the correspondence relationship is deleted at the end. ;
- the transaction has no correspondence in the transaction registry, and it is determined that the transaction is not connected.
- a count of the nesting level is provided for each transaction connection. The count is started when it is established, and it is incremented every time it is used, and it is decremented every time it is used.
- the transaction is a nested connection.
- connection pool sets non-transaction attributes when initial connections are established, initializes connections when allocating new idle connections, maintains non-transaction attributes when recovering ordinary connections, and restores non-transaction attributes when transactions are rolled back to ensure idleness.
- Connections are non-transactional attributes, regardless of transactional connections and ordinary connections. When allocating idle connections, both transactional connections and ordinary connections can use all idle connections.
- the database connection management method provided by the present invention can be applied to the development of various database applications. Compared with traditional transaction and thread connection management methods, the traditional method establishes connections when needed, closes them when they are used, and directly opens and closes the database through threads and global transactions. It lacks connection management and module isolation. It cannot be reused, and the management features such as connection allocation, recycling, and transaction connection management consistency provided by the present invention can be conveniently added as separate modules to the entire system, and all interactions between the development of database business applications and the database are placed in the database.
- the processing module provided by the invention can achieve efficient and secure connection multiplexing, and effectively solves the abuse and recovery of the connection and greatly improves the efficiency.
- the connection management module made by the method provided by the present invention is compared with the previous connection application for efficiency testing.
- FIG. 1 is a schematic flowchart of establishing, assigning, and using a common connection by using a database connection management method provided by the present invention
- FIG. 2 is a schematic flowchart of starting a transaction by a transaction processing method using the method provided by the present invention
- FIG. 3 is a schematic flow chart of a method provided by the present invention for submitting and rolling back transactions through a transaction processing method
- FIG. 4 is a schematic flowchart of recovering connections by using the method provided by the present invention. DETAILED DESCRIPTION OF THE INVENTION The method of the present invention is further developed in conjunction with the following, and the main basic points of the method of the present invention are as follows:
- connection pool to store management connections; the connection pool can be generated according to the specific application to provide the number of connections that should be placed when the connection pool is initialized.
- the dynamically generated connections in the program are also placed in the connection pool.
- the application obtains the connection pool from the connection pool to create a new connection pool. Or the connection is allocated, after the connection is used up, the connection pool recycles or puts the connection dry.
- the connection pool lays the foundation for the overall management of the connection.
- connection is divided into two types of transaction connection and ordinary connection, and different methods for transaction connection and ordinary connection management are adopted for different characteristics of ordinary connection and transaction connection:
- the allocation of idle connections is a case where transaction connections and ordinary connections are not distinguished when applying for a connection, and they are treated the same to avoid when the transaction connection is applied for and the transaction connection has been used up. Although there is an idle ordinary connection, it cannot be used. Conversely, when the ordinary connection is applied for, and the ordinary connection has been used up, although there is an idle transaction connection, it cannot be used.
- the strategy of reusing ordinary connections and effectively using connections in the inventive method is: Does not distinguish between (static connection) established during initialization and (dynamic connection) re-established when the program is run, 1. According to the specific situation, set the maximum possible Number of multiplexing, multiplexing connections that can be multiplexed. As long as it is an established connection, when the connection reference count is less than the maximum reusable number, it can be reused. The reference count is the number of times a common connection has been multiplexed; the maximum reusable number is the maximum multiplexed number of connections configured by the system. 2. According to the specific situation, set the number of initial connections in the connection pool and recycle the connections that should be recycled.
- the configuration number of the initial connection of the connection pool may determine the frequency of using idle connections and the frequency of establishing connections in a specific application.
- the maximum reusable number of connections and the number of initial connections in the connection pool ensure the multiplexing efficiency and usage efficiency of the connection.
- Transaction processing methods include starting transactions, committing and rolling back transactions. For transactions, pass Through transaction processing methods, so that the transaction does not directly obtain the management of the connection, ensure that the transaction is unique to the connection used, and provide convenience for other modules to start the transaction; at the same time, you can organize the transaction in other ways, or you can call the implemented method to Organize transactions, and even call transaction methods in transactions to form nested transactions.
- the transaction connection allocation, recycling, and consistent commit of operations on the connection, rollback, and the uniqueness of the connections that make up the transaction operation are all guaranteed by the transaction processing method. At this time, it not only meets the transaction requirements for the connection, but also does not prevent the connection reuse, and realizes the safe reuse.
- the present invention proposes an efficient database connection multiplexing method, which is described in each step by step as follows:
- Step 1 establish and initialize the connection pool
- the first step is to establish a connection pool when the system (DBMS) is initialized, and the connection pool is configured according to the specific system usage to configure the number of connections that should be placed when the connection pool is initialized. At the same time, the maximum number of multiplexable connections can be configured.
- the second step is to initialize the connection pool, that is, when the system receives the connection request for the first time, the connection request includes ordinary connection and transaction connection. The system initializes the connection pool, establishes the connection according to the configured number of connections, and puts it into the connection pool. .
- Step 2 Use connection pool management methods to establish, allocate, and initialize and use connections.
- the initial connection specifically refers to setting the type of the connection when assigning an idle or new connection, which is a normal connection, setting a non-transaction attribute, providing a reference count, which is a transaction connection, setting a transaction attribute, and providing a nested hierarchy of records.
- the number also provides explicit transaction start, end (commit or rollback) statements, and a transaction registry for the transaction connection.
- the above transaction registry registers the correspondence between the transaction initiator and the connection used by the transaction to ensure the consistency of the connection used by the transaction.
- the table is dynamically generated at runtime based on the actual call situation. This table isolates the transaction processing part and the connection management part.
- the connection used by the transaction in the present invention is the only one used in the running of the transaction and cannot be reused.
- the method of the present invention is used to establish, allocate, initialize, and reuse common connections by using a connection pool management method that avoids the overhead of establishing a handshake for each connection.
- “Start” in the figure indicates that when an application requests a common connection , Go to step 1; step 1 to check whether the connection pool has been initialized. No, initialize the connection pool first, and then go to step 2; if yes, go directly to step 2.
- Step 2 query whether there is the call in the transaction registry Yes, it indicates that the request for the ordinary connection is part of the transaction, and the consistency of the connection should be guaranteed, so the connection registered by the caller in the transaction registry is returned; if not, the process proceeds to step 3.
- Step 3 query whether there are unused idle connections in the connection pool.
- Step 4 query whether there are reusable Connection, that is, whether there is a connection whose number of references does not reach the maximum reuse count. No, a new connection is established, and the connection is Start the reference count; if yes, then find a connection with the smallest reference count and not reaching the maximum reference count in the connection pool, reuse the connection and increase its reference count by 1. Multiplexing the connection means, first There is a connection that can be reused. It does not distinguish between a connection established during initialization (static connection) and a connection that is re-established when the program is run (dynamic connection).
- connection pool As long as it is not an idle connection, whether it is a normal connection or a transactional connection, as long as If it is not occupied, it is popped from the stack (connection pool), it is judged to be a normal connection, it is judged that the reference count is the smallest, and the connection is reused.
- connection pool management method is invoked to establish, allocate, and initialize, and only use a transaction connection by using the transaction processing modes of start, commit, and rollback.
- the connection of transactions is consistent in the method of forming a transaction. Sex guarantees, and Set of business support.
- step 1 checks whether the connection pool has been initialized. No, initialize the connection pool first and proceed to step 2; If yes, go directly to step 2.
- step 2 check whether there is a connection used by the transaction initiator for registration in the transaction registry. Yes, it indicates that this is a nested transaction and returns the transaction initiator used in the transaction registry. Connect and increment the nesting level count of the transaction connection; if no, go to step 3.
- Step 3 queries whether there are unused idle connections in the connection pool. If yes, go directly to step 4; if no, create a For a new connection, go to step 4.
- Step 4 Register the correspondence between the thread number where the transaction initiator is located and the connection used by the transaction to the transaction registry, and at the same time start the transaction nesting level count and set the corresponding transaction connection Properties. All subsequent accesses to the database by the same transaction are done by looking up the registry and using already allocated connections, which guarantees All operations in this transaction use the same database connection.
- commit and roll back the transaction "Start" in the figure indicates that when all tasks of the transaction are completed, the steps of calling the commit and roll back transaction are entered. First obtain the connection used by the transaction from the call value of the transaction connection, and then check the type and nesting level of the connection used by the transaction in the transaction registry.
- connection used is Nested transactions, decreasing the nesting level of the connection; when the connection exists and the nesting level is less than or equal to 1, the use of the connection is not a nested transaction, submit all operations completed on the connection to the database, and connect from the transaction Remove the connection number from the call value pair, restore the non-transactional attributes of the connection, delete the initiator of the transaction and the used transaction connection pair from the transaction registry, and then call the connection pool management method to recover the connection.
- Step 3 use the connection pool manager Cannot recycle connection.
- Step 1 check whether the connection is empty or has been closed. Yes, the call returns; instead, go to step 2.
- Step 2 Check whether the transaction consists of a series of existing database methods in the transaction connection registry, that is, whether the connection exists. Yes, the call returns; instead, go to step 3.
- Step 3 Check whether there are other referees for the connection, that is, check whether there are registrations of recyclers for the connection in the transaction registry.
- Step 4 Check whether the number of connections in the connection pool has reached the initial set number. No, put the connection into the connection pool; Yes, close the connection and recycle. Closing the connection means that it does not distinguish between the connection established during initialization (static connection) and the connection re-established when the program is run (dynamic connection). When the used connection is released, only the connection in the stack (connection pool) is released. The number does not reach the number of connections initially configured. Instead of closing it because it is a dynamic connection, it pushes it onto the stack for later use.
- connection pool parent object such as defined as ConpoolClas s
- connection child objects such as defined as ConnClas s
- transaction registry parent object such as defined AfregClas s
- transaction sub-objects such as AffClas s
- connection number attributes of the connection pool object such as (Defined as lnkNum), the number of initial connections (such as beginNum), the maximum number of multiplexed ordinary connections (such as muxNum), and the create () method
- the initialization operation using the constructor) method
- Connection pool management methods include creating new connections (such as defined as creatComi O), obtaining ordinary connections (such as defined by getCommConn ()), releasing multiplexed ordinary connections (defined as releaseMuxConn ()), and recycling connections (such as defined as releaseConn O) method to ensure secure reuse of ordinary connections.
- connection object Define the non-transactional attributes of the connection object (such as defined as commTrue), the reference attribute of the common connection object (such as defined as usedTrue) or the nesting level of the transaction connection (such as defined as usedN legs) and the connection initialization operation (using Constructor) method.
- record attributes of the transaction registry object such as affRecord
- affRecord which records the originator of the transaction
- the transaction connection including connection, connection type, and nesting level
- delRecord O the definition of the transaction A method of registering transactions (such as defined as regRecord O) and transaction declaring transactions of registry objects (such as defined as delRecord O).
- connection call attributes of the transaction object such as defined as usedLink
- the transaction processing methods include methods to start the transaction (such as defined as beginTrans 0), and commit and roll back the transaction (such as defined to endTrans O).
- the Connpool When the system is initialized, call the Connpool.
- CreateConn () creates the connection sub-object ConnClassN (1 ⁇ N ⁇ beginNum), set ConnClassN. usedTrue: -False, push the connection into the connection pool stack.
- the application requests a transaction connection
- the transaction object corresponding to the application is AffClassN (N is a natural number)
- RegRecord ConnClassK, transaction number
- BeginTrans thePool. ConnClassK
- UsedLink thePool. CoimClassK.
- EndTrans () is called, which includes obtaining the connection number from thePool.
- the system in the specific implementation provided by the present invention refers to a database management system DBMS.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR0317733-5A BR0317733A (pt) | 2002-12-25 | 2003-11-28 | Processo para administração de conexão de base de dados |
AU2003289602A AU2003289602A1 (en) | 2002-12-25 | 2003-11-28 | A method for administrating database connection |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB021399484A CN1317653C (zh) | 2002-12-25 | 2002-12-25 | 一种数据库连接的高效管理方法 |
CN02139948.4 | 2002-12-25 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2004059906A1 true WO2004059906A1 (fr) | 2004-07-15 |
Family
ID=32661076
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2003/001016 WO2004059906A1 (fr) | 2002-12-25 | 2003-11-28 | Procede d'administration de connexions a une base de donnees |
Country Status (4)
Country | Link |
---|---|
CN (1) | CN1317653C (zh) |
AU (1) | AU2003289602A1 (zh) |
BR (1) | BR0317733A (zh) |
WO (1) | WO2004059906A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11995481B2 (en) | 2022-08-22 | 2024-05-28 | Sap Se | Efficient connection pooling |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8244865B2 (en) * | 2004-10-08 | 2012-08-14 | International Business Machines Corporation | Method and apparatus for autonomic management of connection pools |
CN1815469B (zh) * | 2005-02-01 | 2010-04-28 | 华为技术有限公司 | 一种数据库连接资源的管理方法 |
JP2006228135A (ja) * | 2005-02-21 | 2006-08-31 | Brother Ind Ltd | コンテンツ提供システム,出力制御装置およびプログラム |
CN100395710C (zh) * | 2005-05-27 | 2008-06-18 | 华为技术有限公司 | 一种多线程应用程序访问数据库的方法 |
CN100458790C (zh) * | 2006-12-31 | 2009-02-04 | 中国建设银行股份有限公司 | 访问数据库的方法和系统 |
CN101447993B (zh) * | 2008-12-23 | 2012-01-25 | 深圳市金蝶中间件有限公司 | 查找连接池中未释放的连接的方法和装置 |
CN101777047A (zh) * | 2009-01-08 | 2010-07-14 | 国际商业机器公司 | 多租户环境下访问数据库的系统、设备和方法 |
CN102081611B (zh) * | 2009-11-26 | 2012-12-19 | 中兴通讯股份有限公司 | 一种主、备网管系统数据库同步的实现方法及装置 |
CN102346767B (zh) * | 2011-09-19 | 2013-04-17 | 北京金和软件股份有限公司 | 一种基于双连接池的数据库连接方法 |
CN103365929B (zh) * | 2012-04-10 | 2016-09-28 | 阿里巴巴集团控股有限公司 | 一种数据库连接的管理方法及系统 |
CN103810203B (zh) * | 2012-11-13 | 2018-02-27 | 深圳市腾讯计算机系统有限公司 | 一种数据库管理系统连接复用方法及装置 |
CN103064964B (zh) * | 2012-12-29 | 2016-04-20 | 天津南大通用数据技术股份有限公司 | 一种支持分布式事务的数据库的连接方法 |
CN103067293B (zh) * | 2012-12-31 | 2017-03-22 | 北京京东世纪贸易有限公司 | 负载均衡设备的连接管理和复用的方法和系统 |
CN103646084A (zh) * | 2013-12-16 | 2014-03-19 | 浪潮电子信息产业股份有限公司 | 一种基于c程序连接mysql数据库的管理方法 |
CN105512188A (zh) * | 2015-11-25 | 2016-04-20 | 用友网络科技股份有限公司 | 数据连接方法和数据连接系统 |
CN105426544B (zh) * | 2015-12-25 | 2020-06-30 | 北京奇虎科技有限公司 | 监控数据库状态的方法及装置 |
CN107291747A (zh) * | 2016-03-31 | 2017-10-24 | 北京优朋普乐科技有限公司 | 一种数据库连接池的管理方法、装置及系统 |
CN106446183B (zh) * | 2016-09-28 | 2019-05-31 | 中国农业银行股份有限公司 | 数据库连接方法及装置 |
CN106550027B (zh) * | 2016-10-25 | 2020-02-21 | 深圳中兴网信科技有限公司 | 设备连接方法和设备连接系统 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999030514A2 (en) * | 1997-12-12 | 1999-06-17 | Alcatel Usa Sourcing, L.P. | Network management |
CN1238618A (zh) * | 1998-04-06 | 1999-12-15 | 三星电子株式会社 | 网管系统配置网络结构时自动发现和定位网络单元的方法 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3166943B2 (ja) * | 1992-12-31 | 2001-05-14 | ソニー株式会社 | データベースアクセス処理方法 |
US6138143A (en) * | 1999-01-28 | 2000-10-24 | Genrad, Inc. | Method and apparatus for asynchronous transaction processing |
US6704779B1 (en) * | 1999-11-24 | 2004-03-09 | Unisys Corporation | Method and apparatus for a web application server to provide an administration system using a dual set of tiered groups of objects |
-
2002
- 2002-12-25 CN CNB021399484A patent/CN1317653C/zh not_active Expired - Lifetime
-
2003
- 2003-11-28 WO PCT/CN2003/001016 patent/WO2004059906A1/zh not_active Application Discontinuation
- 2003-11-28 BR BR0317733-5A patent/BR0317733A/pt not_active Application Discontinuation
- 2003-11-28 AU AU2003289602A patent/AU2003289602A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1999030514A2 (en) * | 1997-12-12 | 1999-06-17 | Alcatel Usa Sourcing, L.P. | Network management |
CN1238618A (zh) * | 1998-04-06 | 1999-12-15 | 三星电子株式会社 | 网管系统配置网络结构时自动发现和定位网络单元的方法 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11995481B2 (en) | 2022-08-22 | 2024-05-28 | Sap Se | Efficient connection pooling |
Also Published As
Publication number | Publication date |
---|---|
CN1317653C (zh) | 2007-05-23 |
AU2003289602A1 (en) | 2004-07-22 |
BR0317733A (pt) | 2005-11-22 |
CN1510575A (zh) | 2004-07-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2004059906A1 (fr) | Procede d'administration de connexions a une base de donnees | |
US8327375B2 (en) | System and method for supporting resource enlistment synchronization | |
US7650400B2 (en) | Dynamic configuration and self-tuning on inter-nodal communication resources in a database management system | |
US6832238B1 (en) | Local transaction management | |
CN104793988B (zh) | 跨数据库分布式事务的实现方法和装置 | |
Parrington et al. | The design and implementation of Arjuna | |
US6560609B1 (en) | Delegating instance management functions to underlying resource managers | |
US6925644B2 (en) | Method, apparatus, and product for leasing of group membership in a distributed system | |
US7743083B2 (en) | Common transaction manager interface for local and global transactions | |
US7353495B2 (en) | Method for protection against interleaving transactions using a transaction manager | |
JPH1049380A (ja) | スペース効率の良いオブジェクト・ロッキング・システム及び方法 | |
US20060167999A1 (en) | Ensuring a given transactional unit of work arrives at an appropriate server instance | |
US20090300017A1 (en) | Transaction Parallel Control Method, and Database Managemet System | |
JP2001527244A (ja) | オブジェクト・リレーショナル・マッピングにおけるクエリー実行をクライアントとサーバーとで効率的に分割する方法及び装置 | |
JPH1063568A (ja) | マルチスレッド環境におけるメモリの割り当て方法及びシステム | |
CN109255701B (zh) | 一种网贷业务数据处理方法 | |
CN103546440B (zh) | 一种客户端发起事务的事务实现方法和系统 | |
JP2001527242A (ja) | ロックグループを用いた楽観的並行処理制御のためのきめ細やかな整合性をもたらす仕組み | |
KR20060108204A (ko) | 네트워크를 통한 트랜잭션식 파일 동작을 위한 방법 및시스템 | |
CN105635298B (zh) | 一种基于业务隔离原理的数据采集设备统一接入系统 | |
JP2002505471A (ja) | 遠隔処理の中断および継続の方法と装置 | |
CN102063338A (zh) | 一种请求独占资源的方法及装置 | |
US20090100082A1 (en) | Replication and mapping mechanism for recreating memory durations | |
US9582313B2 (en) | Connection resource system | |
JP2001056767A (ja) | トランザクションサービス同期インターフェースを使用して、内部状態のクリーンアップを実施するための方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 3249/DELNP/2005 Country of ref document: IN |
|
ENP | Entry into the national phase |
Ref document number: PI0317733 Country of ref document: BR |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: JP |