International Business Machines Corporation

Jon K Franks

Lap Thiet Huynh

Dinakaran B Joseph

Sivaram Gottimukkala

Barry Mosakowski

Jason P Hawrysz

Gregory M Callis

Christopher N Freeman

Maria Elena Smith

Donald Fred Ault

Ernest Scott Bender

Diane Iupe Shannon

David Yu Pin Yang

Loan Nguyen

Wesley McMillan Devine

John Arthur Helmbold

Alan George Packett

Steven Walkowiak

Embodiments include method, systems and computer program products for an interactive, multi-level failsafe capability. In some embodiments, a failed count indicative of a number of failed attempts to launch an application may be received. A failsafe mode level corresponding to the failed count may be determined. The failsafe mode level may be initialized in response to determining the failsafe mode level corresponding to the failed count. The failsafe mode level may determine the functionality that may be enabled. Users may perform interactive debugging by editing configuration settings and manually enabling functionality.

Interactive multi-level failsafe enablement

Embodiments of the present invention address deficiencies of the art in respect to connectivity management in a heterogeneous network and provide a method, system and computer program product for resilient and reliable end-to-end connectivity in a heterogeneous network. In one embodiment of the invention, a method for resilient and reliable end-to-end connectivity in a heterogeneous network environment can be provided. The method can include creating an instance of an abstracted network resource model (NRM) for a heterogeneous network environment of different network resource nodes. The method further can include binding an application endpoint in the instance of the abstracted NRM with a connectivity endpoint for a first of the different network resource nodes. The method yet further can include detecting an outage in the first of the different network resource nodes. Finally, the method can include re-binding the application endpoint to a second of the different network resource nodes in response to detecting the outage.

Reliable and resilient end-to-end connectivity for heterogeneous networks

Embodiments of the present invention address deficiencies of the art in respect to connectivity management in a heterogeneous network and provide a method, system and computer program product for resilient and reliable end-to-end connectivity in a heterogeneous network. In one embodiment of the invention, a method for resilient and reliable end-to-end connectivity in a heterogeneous network environment can be provided. The method can include creating an instance of an abstracted network resource model (NRM) for a heterogeneous network environment of different network resource nodes. The method further can include binding an application endpoint in the instance of the abstracted NRM with a connectivity endpoint for a first of the different network resource nodes. Finally, the method can include re-binding the application endpoint to a second of the different network resource nodes in response to detecting the outage.

In response to the detection of an external event by the first thread, the first thread sends a quiesce event to each additional thread of the application and suspends execution. The quiesce event may be either a suspension event requesting suspension of the additional threads or a termination event requesting termination of the additional threads. Each additional thread, upon receiving the quiesce event, checks its environment to determine whether it is holding any critical system resource. If the additional thread determines that is not holding any critical system resource and that it is therefore safe to quiesce, the additional thread quiesces. Before quiescing, the last additional thread to quiesce resumes the first thread, which is now free to perform critical operations without interference from the additional threads. If the quiesce type is suspension, the first thread resumes the additional threads upon completing its critical operations, whereupon the application resumes its normal operation.

Quiensce termination/suspension in a multithreaded enviroment

Methods, systems and computer program products according to embodiments of the present invention provide distributing workload between a plurality of data processing systems in a cluster of data processing systems, wherein each of the plurality of data processing systems is executing an instance of an application which communicates over a network such that a connection request to the application may be distributed to any one of the plurality of data processing systems. Such workload distribution may be provided by defining a subset of the plurality of data processing systems which are to receive connection requests to the application having at least one predefined characteristic. A request for a connection to the application is received over the network and it is determined if the request has a characteristic corresponding to the characteristic associated with the subset of the plurality of data processing systems. The request is distributed to a data processing system in the subset of the plurality of data processing systems if the request has a characteristic corresponding to the predefined characteristic.

Methods, systems and computer program products for policy based distribution of workload to subsets of potential servers

Embodiments of the present invention include methods, systems and computer program products which provide for processing an event having a classification based on associated policy rules where the policy rules are conditioned on the classification. A policy rules hash table is provided including a plurality of policy rule entries, each policy rule entry being associated with a hash index. A hash index is generated using a classification hash length based on the classification of the event, the classification having an associated length at least equal to the classification hash length. A policy rule entry in the policy rules hash table is identified that corresponds to the generated hash index. It is determined if a classification field length associated with the identified policy rule corresponds to the classification hash length. The identified policy rule entry is executed if the hash length associated with the identified policy rule corresponds to the classification hash length.

Methods systems and computer program products for processing an event based on policy rules using hashing

Embodiments of the present invention include methods, systems and computer program products which provide for a complex policy rule structured in a plurality of levels wherein the complex policy rule selects an action for execution based on a plurality of individual policy conditions. An event is received having an associated value defining a point in a space covered by the individual policy conditions. The following operations are performed if the complex policy rule is a CNF policy rule. A plurality of summary conditions are generated, each of the summary conditions being associated with one of the levels. The associated value of the received event is compared to a selected one of the summary conditions to determine if the selected one of the summary conditions is met. Operations repeat for others of the summary conditions and individual policy conditions until either one of the summary conditions is not met or all individual policy conditions for one of the levels are not met, allowing the policy rule to be skipped, or until at least one of the individual policy conditions for each level is met. DNF policy rule processing is also provided.

Methods systems and computer program products for processing complex policy rules based on rule form type

A method of controlling the execution of the threads of a first application such as a user application from a second application such as a debugger application running in a different address space. After initializing trace mode for the user application, the debugger waits for an event to occur on one of the threads of the user application. Upon the occurrence of an event on one of the user application threads, an event handler obtains control of the thread execution. The event handler suspends execution of the remaining threads in the application, posts the debugger and then suspends its own execution. When the debugger application has completed its debugging operations, it posts the event handler, which resumes execution of the suspended threads and returns control to the thread on which the event occurred. If a subsequent event occurs on one thread while a previous event on another thread is being processed, the event handler for the subsequent event places it in a deferred event queue for deferred processing. Events consisting of breakpoints are redriven rather than being placed on the deferred queue. The debugger application may hold selected threads in a suspended state following resumption of the remaining threads by setting hold flags associated with those threads.

Growing community of inventors

Apex, NC, United States of America

Jon K Franks