WO2008110115A1

WO2008110115A1 - Transaction coordinator, resource using terminal, service terminal, and method of distributed transaction processing

Info

Publication number: WO2008110115A1
Application number: PCT/CN2008/070471
Authority: WO
Inventors: Shikai Liu; Qingchun Shen
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-03-14
Filing date: 2008-03-11
Publication date: 2008-09-18
Also published as: CN101046815A

Abstract

A transaction coordinator (11), transaction resource using terminal (1) and service terminal (2) are disclosed, a method for processing the distributed transaction by the transaction resource using terminal (1) and the service terminal (2) is also disclosed. The using terminal (1) registers the transaction resource client terminal (12); submitts a submitting request through the registered transaction resource client terminal (12); logs out the transaction resource client terminal (12). According to the transaction identifier in the service operation request, the service terminal (2) looks up the corresponding transaction adapter (211); replaces the current transaction with the transaction adapter (211); executes the service operation; registers the resource manager (22) to the transaction adapter (211) cooresponding to the transaction identifier; according to the transaction identifier in the submitting request, conveys the submitting request to the corresponding transaction adapter (211), executes the submit through the registered resource manager (22).

Description

Transaction coordinator, resource usage end, server side, and distributed transaction processing method

The present invention relates to a distributed transaction processing technology, and more particularly to a method for a transaction coordinator, a transaction resource user, a server, a transaction resource user, and a server to process a distributed transaction. Background technique

With the extensive development of enterprise application systems, there are more and more information interactions between financial management systems, management analysis systems, business systems, customer relationship management systems, logistics management systems, billing systems, etc., which requires enterprise data to have consistency. The need for enterprise data consistency requires atomicity, consistency, isolation, and persistence (Atomicity, Consistency, Isolation, Durability, ACID), which requires distributed transaction processing, and transaction processing needs to be multiple Implemented between transactional resources.

A transaction is a series of operations performed as a single logical unit of work. A distributed transaction is an ACID transaction between two or more transactional resources (for example, two separate databases).

The existing transactional unified framework based on the J2EE Connector Architecture (J2EE Connector Architecture, JCA) implements cross-system transaction unification. Under this framework, the Resource Adapter provides a Connection and Connection Factory interface, and the connection factory is responsible for creating connections to the Application System. The Connection Manager manages the connections of different application systems. When connection management receives a connection request from a connection factory, connection management obtains the connection from the connected cache container, Pool Manager. If there is no connection available in the connection pool, a new physical connection is created by calling the Managed Connection Factory.

The existing JCA-based transactional unified architecture has the following drawbacks: Interface is complex, implementation is difficult, and even some existing systems cannot implement JCA's standard interface in mechanism, which is only applicable to The application system built by the J2EE specification cannot solve the data consistency requirements not based on the J2EE specification or non-Java application system, such as C++ application, #application, etc. Summary of the invention

The purpose of the embodiments of the present invention is to provide an interface device, a transaction coordinator that conforms to data consistency requirements, a transaction resource usage end, a transaction resource server, a transaction resource usage end, and a server-side distributed transaction processing method to implement a cross-system. Distributed transaction processing, and is applicable to a variety of application systems based on J2EE, J2SE (Java 2 Standard Edition), C++, #.

In order to achieve the above object, an embodiment of the present invention provides a distributed transaction processing method for a transaction resource usage end, which includes the following steps:

Register a transactional resource client;

Submitting, by the transaction resource client, a submission request carrying a transaction identifier to a transaction resource server; and

Log out of the transaction resource client.

In order to achieve the above object, an embodiment of the present invention further provides a distributed transaction processing method of a transaction resource server, including: searching for a corresponding transaction adapter according to a transaction identifier carried in a service operation request; and replacing a current transaction with the transaction adapter Performing a business operation according to the business operation request; registering a resource manager to the transaction adapter; forwarding the submit request to the transaction adapter according to a transaction identifier carried in the submit request; and executing by the resource manager submit.

In order to achieve the above object, an embodiment of the present invention further provides a transaction coordinator, including: a transaction proxy module, configured to submit a submission request carrying a transaction identifier by using a registered transaction resource client; and a registration module, configured to register to participate in the current a transaction resource client of the transaction, and notifying the transaction agent module of the registration information; the transaction resource client is at least one; the submit request forwarding module is configured to submit a submit request to the transaction proxy module; and the logout module is configured to log off The transaction resource client of the current transaction, and notifies the transaction agent module of the logout information. In order to achieve the above object, an embodiment of the present invention further provides a transaction resource usage end, including: a transaction coordinator, configured to coordinate transaction resources, and perform distributed transaction control, where the transaction coordinator includes: a transaction proxy module for registering The transaction resource client submits the commit request carrying the transaction identifier; the registration module is configured to register the transaction resource client participating in the current transaction, and notify the transaction proxy module of the registration information; the transaction resource client is at least one; submit the request a forwarding module, configured to submit a submit request to the transaction proxy module; and a logout module, configured to cancel the transaction resource client of the current transaction, and notify the transaction proxy module of the logout information;

a service operation requesting module, configured to submit, by the transaction resource client, a business operation request carrying a transaction identifier;

Submit a request module for initiating a submit request;

A transaction resource client, used to communicate with a transaction resource server, submit a business operation request, and submit a request.

In order to achieve the above object, an embodiment of the present invention further provides a transaction resource server, including: a transaction mapping module, configured to search a transaction adapter corresponding to a transaction identifier; the transaction mapping module includes: a transaction adapter, configured to forward the submission request To the registered resource manager; a recording module, configured to record a correspondence between the transaction identifier and the transaction adapter, and a lookup module, configured to find a transaction adapter corresponding to the transaction identifier;

a transaction adapter creation module, configured to create a transaction adapter, and save a transaction identifier and a transaction adapter to the recording module;

a resource manager, configured to perform a submission according to the submit request;

A transaction manager that replaces the current transaction with the transaction adapter and the registration and deregistration of the resource manager. In the embodiment of the present invention, the transaction coordinator controls the transaction at the upper layer of the transaction manager, and realizes the atomicity, consistency, isolation, and durability required by the distributed transaction processing, and the transaction adapter as an interface is easy to use; The example implements cross-system distributed transaction processing, which is based on

Data manipulation of various application systems such as J2EE, J2SE (Java 2 Standard Edition), C++, C#, etc. Consistency requirements.

The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments. DRAWINGS

1 is a schematic diagram of a first structure of a transaction resource usage end according to an embodiment of the present invention;

2 is a schematic diagram of a first structure of a transaction resource server according to an embodiment of the present invention;

3 is a schematic structural diagram of a distributed transaction processing system formed by a transaction resource use end and a transaction resource server according to an embodiment of the present invention;

4 is a schematic diagram of a first structure of a transaction coordinator according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a second structure of a transaction coordinator according to an embodiment of the present invention;

6 is a schematic diagram of a second structure of a transaction resource usage end according to an embodiment of the present invention;

7 is a schematic diagram of a second structure of a transaction resource server according to an embodiment of the present invention;

8 is a first flowchart of a distributed transaction processing method of a transaction resource usage end according to an embodiment of the present invention;

9 is a first flowchart of a distributed transaction processing method of a transaction resource server according to an embodiment of the present invention;

10 is a second flow diagram of a distributed transaction processing method for a transaction resource usage end according to an embodiment of the present invention;

11 is a second flow diagram of a distributed transaction processing method of a transaction resource server according to an embodiment of the present invention;

12 is a third flow diagram of a distributed transaction processing method of a transaction resource usage end according to an embodiment of the present invention;

FIG. 13 is a third flowchart of a distributed transaction processing method of a transaction resource server according to an embodiment of the present invention. detailed description As shown in FIG. 1, a first structural diagram of a transaction resource usage end according to an embodiment of the present invention is shown. The transaction resource use terminal 1 uses the service provided by the transaction resource server through the transaction resource client 12. The transaction resource usage end 1 includes a transaction coordinator 11, a transaction resource client 12, a business operation request module 13, and a submission request module 14.

The transaction coordinator 11 is used to coordinate transaction resources and perform distributed transaction control, and the transaction resource user 1 starts the transaction through the transaction coordinator 11. The transaction resource client 12 has a one-to-one correspondence with the transaction resource server 2 (not shown), and is used for communicating with the corresponding transaction resource server 2, submitting a business operation request carrying the transaction identifier and submitting the request, implementing the transaction. The service call of resource server 2. The service operation requesting module 13 is configured to submit, by the transaction resource client 12, a service operation request carrying a transaction identifier, and the service operation includes adding, deleting, changing, checking, and publishing the data. After receiving the business operation request, each transaction resource client 12 registers with the transaction coordinator 11. The submit request module 14 is for initiating a commit request, the module sends a commit request to the transaction coordinator 11, and the transaction coordinator 11 sends a commit request to the transaction resource server 2 via the registered transaction resource client 12.

When the transaction involves multiple transaction resource clients, the business operation requesting module 13 may send the business operation request one by one to each transaction resource client 12 corresponding to the operation in the order of the operations included in the transaction, and each transaction resource client receives the service. The operation request is registered in the transaction coordinator 11, so that the transaction coordinator 11 can collectively manage a plurality of transaction resources.

This embodiment implements cross-system distributed transaction processing based on non-JCA architecture, and is applicable to various systems based on J2EE, J2SE, ++, and #.

As shown in FIG. 2, it is a schematic diagram of a first structure of a transaction resource server according to an embodiment of the present invention. The transaction resource server 2 is configured to provide a service resource for the transaction resource using terminal 1 (not shown) through the transaction resource client 12 (not shown), which includes the transaction mapping module 21, the resource manager 22, and the transaction. The manager 23 and the transaction adapter create module 24.

The transaction mapping module 21 is configured to find a transaction adapter corresponding to the transaction identifier, and the transaction mapping module 21 includes a transaction adapter 211, a lookup module 212, and a recording module 213. Transaction adapter 211 is used Receiving the submit request and forwarding the submit request to the registered resource manager, each transaction adapter 211 is used to manage the operation of a transaction in which the transaction resource server 2 participates, and when the transaction resource server 2 participates in multiple transactions, the transaction map Module 21 then includes a plurality of transaction adapters 211. The lookup module 212 is configured to look up the transaction adapter 211 corresponding to the transaction identifier. The recording module 213 is configured to record the correspondence between the transaction identifier and the transaction adapter.

The resource manager 22 is configured to perform the submission in accordance with the submission request, which supports the two-phase commit protocol. The transaction manager 23 is used to replace the current transaction with the registration and deregistration of the transaction adapter and the resource manager, and to manage transaction resources such as a physical database, an in-memory database that supports transactions, and an application system that supports the transaction interface. The transaction adapter creation module 24 is configured to create a transaction adapter 211. After receiving the business operation request, the transaction resource server 2 creates a transaction adapter 211 if the transaction identifier corresponding to the transaction identifier is not found, and the transaction adapter 211 and the corresponding transaction. The identification is saved to the recording module 213.

This embodiment implements cross-system distributed transaction processing based on non-JCA architecture. The transaction adapter is responsible for the management of one transaction operation. The transaction adapter as an interface is easy to use, and is suitable for J2EE, J2SE, ++, and #, etc. A variety of application systems.

As shown in FIG. 3, it is a schematic structural diagram of a distributed transaction processing system formed by a transaction resource use end and a transaction resource server according to an embodiment of the present invention. As can be seen from the figure, the transaction resource use terminal 1 is connected to the transaction resource service system 2 through the transaction resource client 12, and the transaction resource client 12 corresponds to the transaction resource monthly service system 2.

As shown in FIG. 4, it is a schematic diagram of a first structure of a transaction coordinator according to an embodiment of the present invention. The transaction coordinator 11 includes a registration module 112, a submission request forwarding module 113, a logout module 114, and a transaction proxy module 115.

The registration module 112 is configured to register the transaction resource client 12 participating in the current transaction and notify the transaction agent module 115 of the registration information. The transaction resource client 12 registers as a resource agent to the registration module 112. After receiving the submit request sent by the submit request module 14, the submit request forwarding module 113 submits the commit request carrying the transaction identifier through the transaction proxy module 115. Transaction proxy module 115 A transaction resource client 12 registered as a resource agent is managed in a transaction, which submits a commit request carrying a transaction identifier through the transaction resource client 12, and supports submitting the commit request in a two-phase commit manner. The logout module 114 is configured to log out the transaction resource client 12 of the current transaction after submitting the commit request, and notify the transaction proxy module 115 of the logout information.

The non-JCA-based transaction coordinator of the embodiment implements distributed transaction management across systems, and satisfies the data operation consistency requirements of multiple application systems based on J2EE, J2SE, C++, and #.

As shown in FIG. 5, the transaction coordinator of an embodiment of the present invention may further include a creation module 111 for creating a transaction proxy module 115 and generating a transaction identifier.

The two-phase commit is divided into two phases: commit preparation and commit operation. In the commit preparation phase, the transaction resource performs data modification and log record processing after receiving the request. After the processing is completed, the transaction status is changed to "can submit" and then returned. As a result, the report is ready. If all transaction resources are ready, enter the commit phase. During the commit phase, the transaction's "deliverable" status is changed to the "commit complete" status.

As shown in FIG. 6, it is a schematic diagram of a second structure of a transaction resource usage end according to an embodiment of the present invention. In this embodiment, the transaction coordinator 11 shown in FIG. 5 is applied to the transaction resource usage end embodiment 1 shown in FIG. 2, and the transaction proxy module 115 specifically includes a preparation request module 1151 and an operation request module 1152.

The preparation request module 1151 is configured to submit a submission preparation request carrying a transaction identifier; the operation request module 1152 is configured to continue to submit the submission operation request carrying the transaction identifier to the registered transaction resource client if the submission preparation is successful.

In this embodiment, the submission of the submission request adopts a two-stage manner, that is, the first phase is the submission preparation, and the second phase is the submission operation, so that the use terminal can effectively control the consistency of the data operation, thereby realizing the transaction unification across the transaction manager.

FIG. 7 is a schematic structural diagram of Embodiment 2 of a transaction resource server according to the present invention. The difference between the embodiment and the embodiment shown in FIG. 2 is that the transaction mapping module 21 further includes a deletion module 214. The transaction manager 23 specifically includes a transaction switching module 231, a resource registration module 232, and a resource logout module 233. The transaction switching module 231 is configured to replace the current transaction by the transaction manager 23 with the transaction identifier corresponding to the transaction identifier 211 after receiving the business operation request, and replace the current transaction with the transaction adapter 211 by the transaction adapter 211 after the commit is performed. The transaction of manager 23.

The resource registration module 232 is configured to register the resource manager 22 participating in the transaction to the transaction adapter 211 corresponding to the transaction identifier, whereby the transaction adapter 211 can forward the received submission request to the corresponding resource manager 22.

The resource logout module 233 is used to log out of the resource manager 22 from the transaction adapter 211 after the commit is performed.

The delete module 213 of the transaction mapping module 21 is configured to delete the transaction adapter 211 corresponding to the transaction identifier and the correspondence between the transaction identifier and the transaction adapter after the commit is performed, so that the space can be released in time.

As shown in FIG. 8, a first flowchart of a distributed transaction processing method for a transaction resource usage end according to an embodiment of the present invention includes the following steps:

Step A101: Registering a transaction resource client;

Step A102: Submit, by using the registered transaction resource client, a submit request carrying a transaction identifier to the transaction resource server;

Step A103: Unregister the transaction resource client.

This embodiment implements cross-system distributed transaction processing based on non-JCA architecture, and is applicable to J2SE-based, J2EE-based application systems and non-Java application systems based on C++ and C#.

As shown in FIG. 9, the first flowchart of the distributed transaction processing method of the transaction resource server in the embodiment of the present invention includes the following steps:

Step B101: Search for a transaction adapter corresponding to the transaction identifier according to the transaction identifier carried in the service operation request.

Step B102: Replace the current transaction with the transaction manager by the transaction manager; Step B103: Perform a business operation according to the service operation request, where the business operation includes adding, deleting, changing, checking, and publishing the data; Step B104: Register the resource manager to a transaction adapter corresponding to the transaction identifier.

Step B105: Forward the submit request to the corresponding transaction adapter according to the transaction identifier carried in the submit request, and the transaction adapter performs the commit through the registered resource manager.

This embodiment implements cross-system distributed transaction processing based on non-JCA architecture. It is applicable to J2SE-based or non-Java application systems. The transaction adapter is responsible for the management of one transaction operation, and the transaction adapter as an interface is easy to use.

As shown in FIG. 10, it is a second flowchart of a distributed transaction processing method for a transaction resource usage end according to an embodiment of the present invention. In this embodiment, the transaction coordinator manages the coordinated transaction operation through the transaction proxy module, and adopts a two-phase commit mode when submitting the submit request, so that the use terminal can effectively control the transaction unification. This embodiment includes the following steps:

Step A201: Create a transaction proxy module, and generate a transaction identifier.

Step A202: Send a service operation request to a transaction resource client participating in the transaction;

Step A203: registering the transaction resource client and notifying the transaction agent module of the registration information; Step A204: The transaction resource client submits a service operation request carrying the transaction identifier to the transaction resource server;

Step A205, determining whether the service operation request is successful, if step A206 is successfully executed;

Step A206: Submit a submit request to the transaction proxy module;

Step A207: The transaction proxy module submits a submission preparation request carrying the transaction identifier to the transaction resource server by using the registered transaction resource client;

Step A208, determining whether the submission preparation is successful, if step A209 is successfully executed;

Step A209: The transaction proxy module submits a submit operation request carrying the transaction identifier to the transaction resource server through the registered transaction resource client.

In this embodiment, the submission of the submission request adopts a two-phase submission mode, that is, the first phase submits the submission preparation request, and the second phase submits the submission operation request, so that the use end can effectively control the consistency of the data operation, thereby realizing the cross-transaction management. The affairs of the device are unified.

As shown in FIG. 11, the distributed transaction processing method of the transaction resource server is the first embodiment of the present invention. Second flow chart. In this embodiment, the two-phase submission mode of the transaction resource usage end includes the following steps: Step B201: Receive a service operation request, and search for a corresponding transaction adapter according to the transaction identifier carried in the service operation request.

Step B202: Replace the current transaction by the transaction manager with the transaction adapter; Step B203, perform a business operation;

Step B204: Register the resource manager to a transaction adapter corresponding to the transaction identifier;

Step B205: Receive a submission preparation request, and forward the submission preparation request to the corresponding transaction adapter according to the transaction identifier carried in the submission preparation request, and the transaction adapter performs the preparation of the submission through the registered resource manager and returns the execution result;

Step B206: Receive a submit operation request, and forward the submit preparation request to the corresponding transaction adapter according to the transaction identifier carried in the submit operation request, and the transaction adapter performs the submit operation by using the registered resource manager.

This embodiment implements non-JCA-based cross-system transaction coordination. By exposing the transaction manager's commit preparation interface, the transaction unification can be uniformly controlled by the transaction resource use end, and the upper layer of the transaction manager controls the transaction to realize the distributed transaction processing requirement. Atomicity, consistency, isolation and durability.

As shown in FIG. 12, it is a third flowchart of a distributed transaction processing method for a transaction resource usage end according to an embodiment of the present invention. In this embodiment, there are multiple transaction resources participating in the transaction. When creating a transaction, multiple transaction resource clients need to initiate service requests one by one, register them, and send submission requests and submit operation requests one by one. This embodiment includes the following steps:

Step A301: The transaction resource use end application starts a transaction by using a transaction coordinator;

Step A302: The transaction coordinator creates a transaction proxy module and generates a transaction identifier, where the transaction identifier may be a transaction serial number;

Step A303: The transaction resource use end application sends a service operation request to the transaction resource client participating in the transaction;

Step A304: The transaction resource client registers as a resource proxy to the transaction coordinator;

Step A305: The transaction coordinator notifies the transaction agent module of the registration information; Step A306: The transaction resource client submits a service operation request carrying the transaction identifier to the transaction resource server.

Step A307: Determine whether the service operation request is successful, if step A308 is successfully executed; for each transaction resource, the method for determining whether each service operation request is successful may be different, and some systems may return a response regardless of whether the execution succeeds or fails, and some systems return The response will only be returned when an exception occurs, which needs to be determined based on the specific definition of the system;

Step A308, determining whether all transaction resource clients participating in the transaction have been registered, and have sent a business operation request, and if yes, executing step A309, otherwise, performing step A303;

Step A309: The transaction resource use end application submits a submit request to the transaction coordinator;

Step A310: The transaction coordinator forwards the submit request to the transaction proxy module.

Step A311: The transaction proxy module submits a submission preparation request carrying the transaction identifier to the registered transaction resource client.

Step A312: The transaction resource client submits a submission preparation request carrying a transaction identifier to the transaction resource server.

Step A313: The transaction resource client receives the response returned by the transaction resource server.

Step A314: The transaction resource client forwards the response to the transaction proxy module.

Step A315, the transaction agent module determines whether the submission preparation is successful, if the step A316 is successfully executed; Step A316, determining whether the submission preparation request has been sent to the registered transaction resource clients, if yes, executing step A317, otherwise performing step A311;

Step A317: The transaction proxy module submits a submit operation request carrying the transaction identifier to the registered transaction resource client.

Step A318: The transaction resource client submits a submit operation request carrying the transaction identifier to the transaction resource server.

Step A319, the transaction coordinator cancels the transaction resource client;

Step A320: The transaction coordinator notifies the transaction agent module of the logout information;

Step A321: Determine whether a submit operation request has been sent to each registered transaction resource client. If no, go to step A317.

This embodiment implements non-JCA-based cross-system transaction coordination. By exposing the transaction manager's commit preparation interface, the transaction coordinator can actively control the transaction uniformity across the transaction manager, control the transaction at the upper layer of the transaction manager, and implement distributed The atomicity, consistency, isolation, and durability required for transaction processing.

FIG. 13 is a third flowchart of a distributed transaction processing method of a transaction resource server according to an embodiment of the present invention. The execution of the transaction in this embodiment involves multiple resource managers. When performing the business operation and executing the commit, the request is forwarded to each resource manager in turn, and after the transaction is executed, the resource managers are deleted and the transaction identifier is deleted. This embodiment specifically includes the following steps:

Step B301: The transaction resource server application receives the service operation request.

Step B302, the transaction resource server application sends a query request to the transaction mapping module; Step B303, the transaction mapping module looks up the transaction adapter corresponding to the transaction identifier; if found, proceeds to step B306, otherwise, step B304;

Step B304: The transaction resource server application creates a transaction adapter.

Step B305, the transaction resource server saves the transaction adapter and the transaction identifier; Step B306, the transaction resource server replaces the current transaction by the transaction manager transaction with the transaction identifier corresponding to the transaction identifier;

Step B307: The transaction resource server application performs a business operation;

Step B308: Calling multiple resource managers during a business operation;

Step B309: Each resource manager obtains a transaction;

Step B310, each resource manager is registered to the transaction adapter;

Step B311: The transaction resource server application receives the submission preparation request.

Step B312: The transaction resource server application queries the transaction mapping module for the transaction adapter corresponding to the transaction identifier.

Step B313: The transaction mapping module searches for a transaction adapter corresponding to the transaction identifier and returns a search result to the transaction resource server application. Step B314: The transaction resource server application forwards the submit preparation request to the transaction adapter corresponding to the transaction identifier.

Step B315, the transaction adapter sends a submit preparation request to the registered resource manager; Step B316, the resource manager performs the preparation of the submission, and returns the execution result to the transaction adapter; Step B317, the transaction adapter determines whether the submission preparation is successful, and if so, proceeds to step B318; Step B318, the transaction adapter determines whether the registered resource managers have performed the submission preparation, and if so, step B319 is performed, otherwise, step B315 is performed;

Step B319: The transaction adapter returns an execution result to the transaction resource server application.

Step B320: The transaction resource server application returns an execution result to the transaction resource client. Step B321: The transaction resource server application receives the submit operation request.

Step B322: The transaction resource server application queries the transaction mapping module for the transaction adapter corresponding to the transaction identifier.

Step B323: The transaction mapping module searches for a transaction adapter corresponding to the transaction identifier and returns a search result to the transaction resource server application.

Step B324: The transaction resource server application forwards the submit operation request to the transaction adapter corresponding to the transaction identifier;

Step B325, the transaction adapter sends a submit operation request to the registered resource manager; Step B326, the resource manager performs a commit operation; and the resource manager is logged out from the transaction adapter; Step B327, the transaction adapter determines whether each resource manager registered is Performing a submit operation, if yes, executing step B328, otherwise, performing step B325;

Step B328: The transaction resource server deletes the transaction adapter corresponding to the transaction identifier in the transaction mapping module.

Step B329, the transaction resource server will replace the current transaction by the transaction adapter with the transaction of the transaction manager.

This embodiment implements non-JCA-based multi-transaction resource coordination, by exposing the transaction manager's commit preparation interface, the transaction unification can be uniformly controlled by the transaction resource use end, on the transaction manager Layers control transactions, achieving atomicity, consistency, isolation, and persistence required for distributed transaction processing. The embodiment of the invention implements non-JCA-based transaction unification, satisfies the data operation consistency requirement of the J2EE, J2SE (Java 2 Standard Edition) based application system and the non-Java application system based on C++, C#, etc.; exposes the transaction manager The commit preparation interface is unified by the transaction controlling the transaction manager; the transaction is controlled at the upper level of the transaction manager, and the atomicity, consistency, isolation, and persistence required for distributed transaction processing are realized, and compared with the JCA architecture. The interface cartridge is easy to use.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A distributed transaction processing method for a transaction resource usage end, characterized in that the method comprises the following steps:

Register a transactional resource client;

Log out of the transaction resource client.

The method for processing a transaction resource usage end according to claim 1, wherein the step of registering a transaction resource client further comprises the steps of: creating a transaction proxy module; and generating a transaction identifier; A proxy module, configured to submit a submit request carrying a transaction identifier through a registered transaction resource client.

The distributed transaction processing method of the transaction resource usage end according to claim 2, wherein after the step of generating a transaction identifier, the distributed transaction processing method further comprises: transmitting, carrying, to the transaction resource client The step of the business operation request for the transaction identifier.

The distributed transaction processing method of the transaction resource usage end according to claim 2, wherein after the step of registering the transaction resource client, the method further comprises: the step of notifying the transaction information module of the registration information.

The transaction processing method of the transaction resource usage end according to claim 1, wherein the step of submitting the submission request carrying the transaction identifier to the transaction resource server by the registered transaction resource client is specifically: A two-phase commit method is used to submit a commit request carrying a transaction identifier to a transaction resource server through a registered transaction resource client.

The method for processing a transaction resource usage end according to claim 3, wherein the step of transmitting a service operation request to the transaction resource client is specifically: sequentially accessing a transaction resource client participating in the current transaction Send a business operation request.

The distributed transaction processing method according to any one of claims 1 to 6, wherein the step of registering a transaction resource client is specifically: sequentially registering events participating in the current transaction Resource client.

The distributed transaction processing method for a transaction resource usage end according to any one of claims 1 to 6, wherein the registered transaction resource client submits a submission request carrying a transaction identifier to a transaction resource server. The step is specifically: submitting a submitting preparation request carrying a transaction identifier to the plurality of registered transaction resource clients, and if successful, submitting a submit operation request carrying the transaction identifier to the plurality of transaction resource clients in sequence.

A distributed transaction processing method for a transaction resource server, the method comprising:

Finding a corresponding transaction adapter according to the transaction identifier carried in the service operation request;

Replace the current transaction with the transaction adapter;

Performing a business operation according to the business operation request;

Registering a resource manager to the transaction adapter;

Forwarding the submit request to the transaction adapter based on the transaction identifier carried in the submission request; and

The submission is performed by the resource manager.

The distributed transaction processing method of the transaction resource server according to claim 9, wherein after the step of searching for the corresponding transaction adapter according to the transaction identifier carried in the service operation request, if there is no corresponding transaction identifier The transaction adapter creates a transaction adapter and records the correspondence between the transaction ID and the transaction adapter.

The distributed transaction processing method of the transaction resource server according to claim 9, wherein after the commit is performed, the transaction adapter and the correspondence between the transaction identifier and the transaction adapter are deleted, and the current transaction is The transaction adapter is replaced with the transaction of the transaction manager.

The method for processing a distributed transaction processing of the transaction resource server according to claim 9, wherein the step of forwarding the submit request to the transaction adapter according to the transaction identifier carried in the submit request is specifically: The corresponding transaction adapter is found according to the transaction identifier carried in the submission request, and the submission request is forwarded to the transaction adapter.

A transaction coordinator, the transaction coordinator comprising: a transaction proxy module, configured to submit, by using a registered transaction resource client, a submit request carrying a transaction identifier;

a registration module, configured to register a transaction resource client participating in the current transaction, and notify the transaction proxy module of the registration information, where the transaction resource client is at least one;

Submitting a request forwarding module for forwarding a submit request to a transaction proxy module; and

The logout module, which is used to log off the transaction resource client of the current transaction, and notifies the transaction agent module of the logout information.

The transaction coordinator according to claim 13, wherein the transaction coordinator further comprises: a creation module, configured to create a transaction proxy module, and generate a transaction identifier.

The transaction coordinator according to claim 13 or 14, wherein the transaction proxy module specifically submits a transaction proxy module carrying a commit request with a transaction identifier in a two-phase commit manner.

The transaction coordinator according to claim 13 or 14, wherein the transaction proxy module specifically comprises:

a request preparation module, configured to submit a submission preparation request carrying a transaction identifier;

The operation request module is configured to submit a submit operation request carrying the transaction identifier to the registered transaction resource client.

A transaction resource usage end, wherein the transaction resource usage end comprises: a transaction coordinator, configured to coordinate transaction resources, and perform distributed transaction control; the transaction coordinator includes:

a transaction proxy module, configured to submit a submission request carrying a transaction identifier through a registered transaction resource client;

a registration module, configured to register a transaction resource client participating in the current transaction, and notify the transaction proxy module of the registration information; the transaction resource client is at least one;

Submitting a request forwarding module for forwarding a submit request to a transaction proxy module; and a logout module, used to cancel the transaction resource client of the current transaction, and notify the transaction agent module of the logout information;

a service operation request module, configured to submit, by the transaction resource client, a service operation request carrying a transaction identifier; and

Submit a request module for initiating a submit request;

The transaction resource usage end according to claim 17, wherein the transaction coordinator further comprises: a creation module, configured to create a transaction proxy module, and generate a transaction identifier.

The transaction resource usage end according to claim 17, wherein the transaction proxy module specifically submits a transaction proxy module carrying a submission request with a transaction identifier in a two-phase commit manner.

The transaction resource usage end according to claim 17, wherein the transaction proxy module specifically includes:

A transaction resource server, wherein the transaction resource server includes: a transaction mapping module, configured to search for a transaction adapter corresponding to the transaction identifier; the transaction mapping module includes:

a transaction adapter, configured to forward the submit request to the registered resource manager; a record module, configured to record a correspondence between the transaction identifier and the transaction adapter; and a lookup module, configured to find a transaction adapter corresponding to the transaction identifier;

a resource manager, configured to perform the submission according to the submit request; and A transaction manager that replaces the current transaction with the transaction adapter and the registration and deregistration of the resource manager.

The transaction resource server according to claim 21, wherein the transaction manager specifically comprises:

a transaction switching module, configured to replace the current transaction by the transaction manager's transaction with the transaction adapter corresponding to the transaction identifier, and replace the current transaction with the transaction manager by the transaction adapter after the commit is performed;

a resource registration module, configured to register a resource manager with a transaction adapter corresponding to the transaction identifier; and a resource logout module, configured to log the resource manager from the transaction adapter.

The transaction resource server according to claim 21 or 22, wherein the transaction mapping module further comprises: a deletion module, configured to delete the transaction adapter corresponding to the transaction identifier after performing the commit.