SELECTION OF TRANSACTION MANAGERS BASED ON RUNTIME DATA

• US 20100146033A1
• Filed: 12/10/2008
• Published: 06/10/2010
• Est. Priority Date: 12/10/2008
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mezarina, Edward E., Kaczynski, Timothy D., Sykes, Matthew J.
• Application Number:
  US12/332,020
• Publication Number:
  US 20100146033A1
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06Q 10/04 Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" market predictions or forecasting for commercial activities G06Q30/0202
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• 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

One or more transaction managers are automatically selected from a plurality of transaction managers for use in processing a transaction. This selection is based on the types of resources used by the transaction and runtime data of the transaction managers able to support one or more of those resource types. The selection of the one or more transaction managers enables less than all of the transaction managers of an application server to be used in transaction commit processing, thereby improving performance.

Claims

1. A method of facilitating selection of transaction managers for use in transactional processing, said method comprising:

obtaining, by a component of a transactional environment, runtime statistics for a plurality of transaction managers of a transactional environment, said runtime statistics for a transaction manager of the plurality of transaction managers including real-time data relating to commit processing performed by the transaction manager; and

selecting by the component one or more transaction managers from the plurality of transaction managers to use in completing a transaction of the transactional environment, wherein the selecting is based on the obtained runtime statistics.

2. The method of claim 1, wherein the selecting comprises selecting the one or more transaction managers from a subset of transaction managers, said subset of transaction managers being selected from the plurality of transaction managers based on one or more resource types used by the transaction, wherein each transaction manager of the subset of transaction managers supports at least one resource type of the one or more resource types.

3. The method of claim 2, wherein the selecting comprises selecting the one or more transaction managers from the subset of transaction managers based on optimal runtime statistics.

4. The method of claim 1, wherein the selecting comprises selecting the one or more transaction managers from a subset of transaction managers, said subset of transaction managers being selected from the plurality of transaction managers based on one or more resource types used by the transaction, wherein each transaction manager of the subset of transaction managers supports the one or more resource types used by the transaction.

5. The method of claim 1, wherein the runtime statistics are maintained in a histogram accessible by the component.

6. The method of claim 1, wherein the selecting is further based on one or more resource types used by the transaction.

7. The method of claim 6, further comprising assigning one or more resource types to each of the transaction managers of the plurality of transaction managers.

8. The method of claim 1, wherein the component comprises an application server of the transactional environment.

9. The method of claim 1, wherein the obtaining runtime statistics for a transaction manager of the plurality of transaction managers comprises performing by the transaction manager one or more commits and recording real-time data relating to the one or more commits.

10. The method of claim 9, wherein the real-time data include at least one of CPU time for the one or more commits, elapsed time for the one or more commits, average bytes of network I/O for the one or more commits, and average bytes of disk I/O for the one or more commits.

11. The method of claim 1, wherein completing the transaction comprises performing one of a commit or a rollback.

12. A system of facilitating selection of transaction managers for use in transactional processing, said system comprising:

at least one processor of a transactional environment to perform a method, said method comprising;

obtaining, by a component of a transactional environment, runtime statistics for a plurality of transaction managers of a transactional environment, said runtime statistics for a transaction manager of the plurality of transaction managers including real-time data relating to commit processing performed by the transaction manager; and

selecting by the component one or more transaction managers from the plurality of transaction managers to use in completing a transaction of the transactional environment, wherein the selecting is based on the obtained runtime statistics.

13. The system of claim 12, wherein the selecting comprises selecting the one or more transaction managers from a subset of transaction managers, said subset of transaction managers being selected from the plurality of transaction managers based on one or more resource types used by the transaction, wherein each transaction manager of the subset of transaction managers supports at least one resource type of the one or more resource types.

14. The system of claim 12, wherein the selecting is further based on one or more resource types used by the transaction.

15. The system of claim 12, wherein the obtaining runtime statistics for a transaction manager of the plurality of transaction managers comprises performing by the transaction manager one or more commits and recording real-time data relating to the one or more commits.

16. An article of manufacture comprising:

at least one computer readable medium having computer readable program code logic to facilitate selection of transaction managers for use in transactional processing, said computer readable program code logic when executing performing the following;

obtaining, by a component of a transactional environment, runtime statistics for a plurality of transaction managers of a transactional environment, said runtime statistics for a transaction manager of the plurality of transaction managers including real-time data relating to commit processing performed by the transaction manager; and

selecting by the component one or more transaction managers from the plurality of transaction managers to use in completing a transaction of the transactional environment, wherein the selecting is based on the obtained runtime statistics.

17. The article of manufacture of claim 16, wherein the selecting comprises selecting the one or more transaction managers from a subset of transaction managers, said subset of transaction managers being selected from the plurality of transaction managers based on one or more resource types used by the transaction, wherein each transaction manager of the subset of transaction managers supports at least one resource type of the one or more resource types.

18. The article of manufacture of claim 16, wherein the selecting is further based on one or more resource types used by the transaction.

19. The article of manufacture of claim 16, wherein the obtaining runtime statistics for a transaction manager of the plurality of transaction managers comprises performing by the transaction manager one or more commits and recording real-time data relating to the one or more commits.

20. The article of manufacture of claim 19, wherein the real-time data include at least one of CPU time for the one or more commits, elapsed time for the one or more commits, average bytes of network I/O for the one or more commits, and average bytes of disk I/O for the one or more commits.