Dynamic Transaction Log Resource Enlistment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional transaction processing systems face challenges in accurately tracking and recovering resources that are dynamically enlisted during runtime, especially in distributed systems where resources represented by proxies are not preconfigured, leading to errors and inefficiencies.

Innovation Solution

A method and apparatus that dynamically enlist resources during transaction execution and store information about each resource in a transaction log, including their state, to facilitate complete recovery, even if resources are unknown before execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If resources are preconfigured and stored in the transaction log at the beginning, then the transaction log structure is simple and easy to manage, but resources that are dynamically enlisted during runtime cannot be tracked

Engineering Contradiction:

Improveresource information trackingVSAvoidtransaction log structure

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The transaction log structure is made dynamic by allowing resources to be enlisted and recorded at runtime rather than requiring all resources to be preconfigured. The system dynamically adds resource information to the transaction log as resources are enlisted during transaction execution, enabling tracking of both preconfigured and dynamically discovered resources.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system performs preliminary configuration of the transaction log structure to accommodate dynamic resource enlistment. By preparing the log structure in advance to accept dynamic entries, the system enables runtime resource tracking without requiring complete resource knowledge beforehand, resolving the contradiction between information completeness and structural simplicity.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If all resources are explicitly configured before transaction execution, then resource management is straightforward, but the system cannot handle dynamically enlisted resources that are unknown prior to execution

Engineering Contradiction:

Improvedynamic resource enlistmentVSAvoidresource configuration

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system transitions from static resource configuration to dynamic resource enlistment. Resources can be discovered and enlisted during runtime based on actual transaction needs, allowing the system to adapt to varying transaction requirements without requiring all resources to be predetermined and manually configured.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The transaction log serves as an intermediary structure that bridges preconfigured resources and dynamically enlisted resources. It maintains a unified record of all resources involved in a transaction, whether known beforehand or discovered during execution, simplifying the management complexity while enabling dynamic adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If the transaction log only records preconfigured resources, then the log size is minimized, but recovery cannot accommodate dynamically enlisted resources

Engineering Contradiction:

Improvetransaction recoveryVSAvoidtransaction log size

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The transaction log dynamically adjusts its content based on actual resource enlistment during transaction execution. Rather than recording only preconfigured resources or all possible resources, the log selectively records resources that are actually enlisted, ensuring accurate recovery information without unnecessary data bloat.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of resource knowledge from static (known beforehand) to dynamic (determined at runtime). This allows the transaction log to contain only the necessary resource information for recovery, optimizing the balance between log size and recovery reliability by recording exactly what is needed rather than what is possible.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS8041690B2Storing information for dynamically enlisted resources in a transaction

Publication Date: 2011.10.18 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A method, apparatus and program product dynamically enlist a plurality of resources to be committed by a transaction during execution of the transaction and store information about each enlisted resource in the plurality of resources with the transaction in a transaction log, including information about a state of each resource, to facilitate recovery of the transaction. Enlisting and storing may be performed during the execution of the transaction, and the resources to be committed by the transaction may be unknown prior to execution of the transaction. By doing so, a more complete record of all the resources that were enlisted during runtime may be maintained.