System and method for supporting resource manager (RM) instance awareness in a transactional environment

• US 9,542,220 B2
• Filed: 12/31/2014
• Issued: 01/10/2017
• Est. Priority Date: 04/28/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Shen, Xugang, Zhang, Qingsheng, Little, Todd J., Jin, Yongshun
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US14/587,474
• Publication Number:
  US 20150309837A1
• Time in Patent Office: 741 Days
• Field of Search: 718100-108
• US Class Current: 1/1
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/467 Transactional memory G06F9/528 takes precedence
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A system and method can support transaction processing in a transactional environment. A transactional server operates to receive resource manager (RM) instance information from a data source that is associated with one or more RM instances, wherein the received instance information allows the transactional server to be aware of which RM instance that the transactional server is currently connected to. Furthermore, the transactional server operates to save the received instance information into one or more tables that are associated with the transactional server. Then, the transactional server can process a global transaction based on the instance information saved in the one or more tables.

Claims

1. A method for supporting transaction processing in a transactional system comprising:

a plurality of transactional servers including a plurality of transaction managers, and a plurality of resource manager (RM) instances for managing access to a plurality of databases, the method comprising;

providing a server table in a shared memory accessible from said plurality of transactional servers, said server table comprising a server table entry for each of said plurality of transactional servers and an instance identifier for each of said plurality of transactional servers,

receiving at each of the plurality of transactional servers RM instance information indicative of which RM instance of the plurality of RM instances said each of the plurality of transactional servers is currently connected to;

saving the received instance information from each of the plurality of transactional servers into the instance identifier associated with said each of the plurality of transactional servers in said server table in said shared memory accessible from said plurality of transactional servers;

allowing transactional servers participating in global transactions to access said server table to obtain instance information identifying which of the plurality of transactional servers are connected to which RM instance, and coordinate said global transactions based on said instance information; and

in response to changes in connections between said each of the plurality of transactional servers and said plurality of databases, updating the instance identifiers associated with said each of the plurality of transactional servers in said server table in said shared memory.

2. The method of claim 1, further comprising:

registering a call back operation with a particular RM instance of the plurality of RM instances when a particular transactional server of said plurality of transactional servers makes a connection with said particular RM instance, such that, when the call back operation is triggered, said particular RM instance transmits RM instance information to the particular transactional server.

3. The method of claim 2, further comprising:

registering the call back operation statically where an XA interface is used; and

registering the call back operation dynamically where a shared library function is used.

4. The method of claim 2, further comprising:

storing the received instance information at the particular transactional server in a context for said connection, and

enabling a flag, which indicates the receiving of the instance information.

5. The method of claim 4, further comprising:

checking the flag with the particular transactional server at one or more check points while performing the transaction, and

updating the instance information saved in the server table in a shared memory accessible from said plurality of transactional servers when the instance information is updated.

6. The method of claim 1, further comprising:

storing in said shared memory an RM table which stores a plurality of unique database names, an instance table which stores a plurality of RM instance names, and a service table which stores a plurality of database service names.

7. The method of claim 1, wherein:

each instance identifier comprises RM instance information, database information, and database service information identifying a database connection of one of said plurality of transactional servers.

8. The method of claim 1, wherein:

each instance identifier comprises a single integer comprising a plurality of RM instance information bits, a plurality of database information bits, and a plurality of database service information bits identifying a database connection of one of said plurality of transactional servers.

9. The method of claim 1, wherein:

each instance identifier comprises a 32-bit integer comprising 12 RM instance information bits, 8 database information bits, and 12 database service information bits identifying a database connection of one of said plurality of transactional servers.

10. A system for supporting transaction processing in a transactional environment, comprising:

a plurality of networked computer systems each comprising one or more microprocessor and memory;

a plurality of transactional servers operating on said plurality of networked computer systems, wherein said plurality of transactional servers include a plurality of transaction managers;

a database;

a plurality of resource manager (RM) instances for managing access to the database;

a server table stored in a shared memory accessible from said plurality of transactional servers, said server table comprising a server table entry for each of said plurality of transactional servers and an instance identifier for each of said plurality of transactional servers,

wherein the plurality of transactional server are configured to receive RM instance information indicative of which RM instance of the plurality of RM instances said each of the plurality of transactional servers is currently connected to;

wherein the plurality of transactional server are configured to save the received instance information into the instance identifier associated with said each of the plurality of transactional servers in said server table in said shared memory accessible from said plurality of transactional servers;

wherein transactional servers participating in global transactions are configured to access said server table to obtain instance information identifying which of the plurality of transactional servers are connected to which RM instance, and thereby coordinate said global transactions based on said instance information; and

wherein the plurality of transactional servers are configured to update the instance identifier associated with said each of the plurality of transactional servers in said server table in said shared memory in response to changes in connections between said plurality of transactional servers and said plurality of databases.

11. The system according to claim 10, wherein:

when a particular transactional server of said plurality of transactional servers makes a connection with said particular RM instance, the particular transactional server registers a call back operation with a particular RM instance of the plurality of RM instances such that, when the call back operation is triggered, said particular RM instance transmits RM instance information to the particular transactional server.

12. The system according to claim 11, wherein:

the particular transactional server registers the call back operation statically where an XA interface is used; and

the particular transactional server register the call back operation dynamically where a shared library function is used.

13. The system according to claim 11, wherein:

the particular transactional server is configured to store the received instance information in a context in the particular transactional server for said connection, and enable a flag, which indicates the receiving of the instance information.

14. The system according to claim 13, wherein:

the particular transactional server is configured to check the flag at one or more check points while performing the transaction, and update the instance information saved in the server table in a shared memory accessible from said plurality of transactional servers when the instance information is updated.

15. The system according to claim 10, further comprising, stored in said shared memory, an RM table which includes a plurality of unique database names, an instance table which includes stores a plurality of RM instance names, and a service table which includes a plurality of database service names.

16. The system according to claim 10, wherein each instance identifier comprises RM instance information, database information, and database service information identifying a database connection of one of said plurality of transactional servers.

17. The system according to claim 10, wherein each instance identifier comprises a single integer comprising a plurality of RM instance information bits, a plurality of database information bits, and a plurality of database service information bits identifying a database connection of one of said plurality of transactional servers.

18. A non-transitory machine readable storage medium having instructions stored thereon for supporting transaction processing in a transactional system comprising:

a plurality of transactional servers including a plurality of transaction managers, and a plurality of resource manager (RM) instances for managing access to a plurality of databases, which instructions, when executed, cause the transactional system to perform steps comprising;

providing a server table in a shared memory accessible from said plurality of transactional servers, said server table comprising a server table entry for each of said plurality of transactional servers and an instance identifier for each of said plurality of transactional servers,

receiving at each of the plurality of transactional servers RM instance information indicative of which RM instance of the plurality of RM instances said each of the plurality of transactional servers is currently connected to;

saving the received instance information from each of the plurality of transactional servers into the instance identifier associated with said each of the plurality of transactional servers in said server table in said shared memory accessible from said plurality of transactional servers;

allowing transactional servers participating in global transactions to access said server table to obtain instance information identifying which of the plurality of transactional servers are connected to which RM instance, and coordinate said global transactions based on said instance information; and

in response to changes in connections between said each of the plurality of transactional servers and said plurality of databases, updating the instance identifiers associated with said each of the plurality of transactional servers in said server table in said shared memory.