SYSTEM AND METHOD FOR SUPPORTING TRANSACTION AFFINITY BASED ON RESOURCE MANAGER (RM) INSTANCE AWARENESS IN A TRANSACTIONAL ENVIRONMENT

• US 20170153910A1
• Filed: 02/09/2017
• Published: 06/01/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: ZHANG, QINGSHENG, LITTLE, TODD J, JIN, YONGSHUN, SHEN, XUGANG
• Granted Patent: US 9,977,694 B2
• Time in Patent Office: Days
• 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 system operates to route a request to a transactional server, wherein the transactional server is connected to a resource manager (RM) instance. Furthermore, the transactional system can assign an affinity context to the transactional server, wherein the affinity context indicates the RM instance that the transactional server is associated with, and the transactional system can route one or more subsequent requests that are related to the request to the transactional server based on the affinity context.

Claims

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

routing a request to a transactional server, wherein the transactional server is connected to a resource manager (RM) instance;

assigning an affinity context to the transactional server, wherein the affinity context indicates the RM instance that the transactional server is associated with; and

routing one or more subsequent requests that are related to the request to the transactional server based on the affinity context.

2. The method of claim 1, further comprising:

allowing said RM instance to be an instance in a clustered database.

3. The method of claim 1, further comprising:

allowing said request and said one or more subsequent requests to be associated with a global transaction.

4. The method of claim 3, further comprising:

using an affinity routing policy to route the one or more subsequent requests, wherein the affinity routing policy is based on a RM name, an instance name, and a service name.

5. The method of claim 1, further comprising:

allowing said request and said one or more subsequent requests to be associated with a client context.

6. The method of claim 1, further comprising:

including, via the transactional server, the affinity context in a message before sending the message.

7. The method of claim 1, further comprising:

updating the affinity context in the transactional server based on a message received from another transactional server.

8. The method of claim 1, further comprising:

using an affinity context string to transfer the affinity context from a transactional domain to another transactional domain.

9. The method of claim 1, further comprising:

using a connector to transfer the affinity context from a transactional system to an application server.

10. The method of claim 1, further comprising:

using a connector to receive an affinity context from an application server.

11. A system for supporting processing a global transaction in a transactional middleware environment, comprising:

one or more microprocessors;

a transactional system, running on the one or more microprocessors, wherein the transactional system operates to perform the steps comprising

routing a request to a transactional server, wherein the transactional server is connected to a resource manager (RM) instance;

assigning an affinity context to the transactional server, wherein the affinity context indicates the RM instance that the transactional server is associated with; and

routing one or more subsequent requests that are related to the request to the transactional server based on the affinity context.

12. The system according to claim 11, wherein:

said RM instance is an instance in a clustered database.

13. The system according to claim 11, wherein:

said request and said one or more subsequent requests are associated with a global transaction.

14. The system according to claim 13, wherein:

the transactional system operates to use an affinity routing policy to route the one or more subsequent requests, wherein the affinity routing policy is based on a RM name, an instance name, and a service name.

15. The system according to claim 11, wherein:

said request and said one or more subsequent requests are associated with a client context.

16. The system according to claim 11, wherein:

the transactional system operates to include the affinity context in a message before sending the message.

17. The system according to claim 11, wherein:

the transactional system operates to update the affinity context in the transactional server based on a message received from another transactional server.

18. The system according to claim 11, wherein:

the transactional system operates to use an affinity context string to transfer the affinity context from a transactional domain to another transactional domain.

19. The system according to claim 11, wherein:

the transactional system operates to use a connector to at least one of

transfer the affinity context from a transactional system to an application server, and

receive an affinity context from an application server.

20. A non-transitory machine readable storage medium having instructions stored thereon that when executed cause a system to perform the steps comprising:

routing a request to a transactional server, wherein the transactional server is connected to a resource manager (RM) instance;

assigning an affinity context to the transactional server, wherein the affinity context indicates the RM instance that the transactional server is associated with; and

routing one or more subsequent requests that are related to the request to the transactional server based on the affinity context.