International Business Machines Corporation

Matthew J Sykes

Stephen Joseph Kinder

Timothy D Kaczynski

Rohit Dilip Kelapure

Colette Manoni

Daniel S Gritter

James William Stopyro

Barry P Gower

Junjie Cai

David Andrew Booz

David A Follis

Jeffrey Alan Frey

Edward E Mezarina

A system and method that performs retrofitting and autowiring of service bindings by generating a plurality of retrofitted references from a plurality of resource references and autowiring the plurality of retrofitted references into an application. The system and method deploys the application to an environment in response to the autowiring of the plurality of retrofitted references.

Autowiring location agnostic services into application software

A method, system and computer program for dynamically updating code managed by an authorized agent. The method includes executing multiple versions of agent code in system memory. One version of the agent code is executed as an active version and another version of the agent code is executed as an inactive version. Version numbers of the active and inactive versions of the agent code are stored in a reloadable module vector. Client instances previously bound to the inactive version of the agent code are bound to the active version of the agent code after comparing the version numbers of the active version of the agent code and the inactive version of the agent code. A portion of the system memory used by the inactive version of the agent code is deallocated when no client instances are bound to the inactive version of the agent code.

Dynamically updating code without requiring processes to restart

Nested recovery scope management systems and methods for a multiple process computer system having a dynamic multiple address space server are disclosed. Stateless recovery agents are employed, under the control of a supervisory program called Recovery Director, during initialization or restart of servers to restore recoverable data in response to identified failures or other abnormal termination. The Director controls the recovery of protected resources in a systematic manner. The Director is initialized when a first address space of a first server is started. Then, as each instance of a recoverable component is initialized, the component registers with the Director by providing a reference to a stateless recovery agent that can later perform recovery functions for it if needed. As part of the registration, a token representing the current failure scope of the registration is generated and provided to the recoverable component by the Director.

Nested recovery scope management for stateless recovery agents

Managing shared data objects to share data between computer processes, including a method for executing a plurality of independent processes on an application server, the processes including a first process and a second process. A shared memory utilized by the plurality of independent processes is provided. A single copy of the data and metadata are stored in the shared memory. The metadata includes an address of the data. The first process initiates the storing of the data in the shared memory. An address of the metadata is transferred from the first process to the second process to notify the second process about the data. The second process determines the address of the shared memory by reading the metadata. The data in the shared memory is accessed by the second process.

Managing shared data objects to provide visibility to shared memory

A system for sharing data between computer processes. The system includes a processor configured to implement a method that includes executing a plurality of independent processes on an application server, the processes including a first process and a second process. A shared memory utilized by the plurality of independent processes is provided. A single copy of the data and metadata are stored in the shared memory. The metadata includes an address of the data. The first process initiates the storing of the data in the shared memory. An address of the metadata is transferred from the first process to the second process to notify the second process about the data. The second process determines the address of the shared memory by reading the metadata. The data in the shared memory is accessed by the second process.

One or more transaction managers are automatically selected from a plurality of transaction managers for use in processing a transaction. The selection is based on types of resources used by the transaction and supported resource types of the transaction managers. 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.

Selection of transaction managers based on transaction metadata

A histogram, or resource status history table, for multiple resources is created and maintained. A transaction or resource manager arranges and/or reorders various resources into a sequence based on the histogram such that read-only resources are prepared first and a sole non-read-only resource need not be prepared, but only committed. The transaction manager heuristically determines the order that resources are driven to achieve last-agent optimization. The histogram is kept related to context, based on runtime and applications context to ensure that usage patterns by context are optimized without the need for the installation to know any usage patterns.

Method, system, and storage medium for dynamically reordering resource participation in two-phase commit to heuristically optimize for last-agent optimization

Resources used by components are aggressively reclaimed, in order to enable those resources to be available to other components. To aggressively reclaim one or more resources of a component, the component is forced to transition from one state to a reclaim state, and at the reclaim state, the resources are reclaimed, if necessary.

Growing community of inventors

Poughkeepsie, NY, United States of America

Matthew J Sykes