Message-Recovery File Log Locating and Monitoring
USPTO
April 25, 2026
A method, system, and medium are provided for monitoring the data volume in a file log associated with a program (e.g., a queue manager) in a failover computing environment. A failover computing environment includes pairs of programs capable of performing the same functions. One program in the pair is the primary program and the other is the backup program. Only one of the two programs is active at any given time. Embodiments of the present invention may identify the file directory for each program installed on a computing device. The location of each file log may be determined by accessing a core-configuration file in the file directory associated with the program. The program only has access to the core-configuration file when the program is active. Once the file log is located, the file usage may be ascertained and compared with a threshold usage.
See publication
Tags: Transformation
Application Transaction Wait Time
USPTO
April 25, 2026
A transaction server. The transaction server comprises a processor, a non-transitory memory, and an application stored in the non-transitory memory. When executed by the processor, the application transmits a plurality of transaction requests to at least one backend server, where the backend server performs processing on the transaction, determines that a transaction request timeout occurs when a transaction response has not been received from the at least one backend server within a timeout time period after transmitting the associated transaction request, and adjusts the timeout time period based on the transaction request timeouts without restarting.
See publication
Tags: Transformation
Dynamic Telemetry Client Message Routing
USPTO
April 25, 2026
A dynamic telemetry client message routing system is provided. The system comprises a provisioning application stored in a memory of a computer system that, when executed by the processor of the computer system, receives a request from a telemetry client to register for message routing services; the request comprising a client identity. The provisioning application creates an entry in a data store associating the client identity with a broker group identity and a queue manager alias and a time to live value. The provisioning application sends a request to a route builder to configure the queue manager alias into the broker group. The route builder sends a message to the broker group to configure the queue manager alias. The message broker receives a request to send a message to the telemetry client and transmits the message and the queue manager alias of the broker group accessed from the data store.
See publication
Tags: IT Strategy
Re-Routing Messages to Parallel Queue Instances
USPTO
April 25, 2026
A method, system, and medium are provided for re-routing messages from a particular parallel queue instance that is experiencing below normal message throughput by lowering the priority setting of the particular queue instance. The messages are re-routed to the other parallel queue instances by a load balancing algorithm that transfers messages to queue instances having a higher priority setting. A series of determinations are made, prior to lowering the priority setting, to confirm that lowering the priority setting for the queue instance is the preferred response to the decreased throughput for the queue instance.
See publication
Tags: IT Strategy
Managing Queue Capacity in a Messaging Queue
USPTO
April 25, 2026
A method and system for automatically managing alarms in an environment where a period of time could pass before the cause of the alarm is addressed is explained herein. The method includes automatically increasing the maximum depth of a queue (i.e. the maximum capacity of a queue to store data) in response to an indication that the current depth of the queue exceeds a high-level alarm setting. Upon determining that the depth of the queue has fallen below the original high-level alarm setting, the maximum depth of the queue is automatically returned to the original maximum setting. In addition, a low-level alarm may be disabled in conjunction with increasing the maximum depth and reactivated upon returning the maximum queue depth to the original setting.
See publication
Tags: IT Strategy
Problem Management for Outsized Queues
USPTO
April 25, 2026
A system is provided for problem management for outsized queues. The system includes a computer readable storage medium comprising a management component stored as a set of computer instructions executable by a processor. The management component stops transmission of inbound messages for a queue managed by a first queue manager. The management component provides a copy of the queue to a second queue manager and recreates the queue as an empty queue for the first queue manager. The management component restarts the inbound messages for the recreated queue and enables the second queue manager to manage the copy of the queue. The management component enables an application that retrieved messages from the queue to retrieve messages from at least one of the recreated queue and the copy of the queue and to promote outputting data for a requesting user application to a user interface.
See publication
Tags: IT Strategy
System and method of maintaining an enqueue rate of data messages into a set of queues
USPTO
April 25, 2026
A system comprises a component which receives an initial status message, from a primary queue manager, comprising a rate of data messages moving into a primary queue. The component detects that a primary queue rate is below a predetermined range based on the received initial status message. The component increases the weight of the primary queue in response to detecting that the primary queue rate provided by the initial status message is below the predetermined range. The component receives a subsequent status message, from the primary queue manager, comprising the rate of data messages moving into the primary queue. The component detects that the primary queue has a rate below the predetermined range based on the received subsequent status message. The component activates a secondary queue in response to detecting that the primary queue rate provided by the subsequent status message is below the predetermined range.
See publication
Tags: IT Strategy
Automatic Queue Size Determination and Tuning
USPTO
April 25, 2026
Methods, systems, and media are provided for automatically determining a preferred queue size for an individual queue based on message traffic. Embodiments include referencing a plurality of queue data sets for one queue. One or more high-activity queue data sets are identified as having a large number of messages compared to other queue data sets in the plurality. Thereafter, a target size for a queue is determined based on an average message size generated using one or more of the high-activity queue data sets. The current size of the queue is adjusted to reflect the target size. In further aspects, the queue data sets may be collected over time intervals that are dynamically modified based on message traffic.
See publication
Tags: IT Strategy
Messaging Middleware Processing
USPTO
April 25, 2026
A message queuing system implemented by at least one computer. The system comprises a performance queue to keep event status related to performance of non-performance queues, threads, which are sequences of programmed instructions, launched by the queue managers to transmit and receive messages over connections between individual queues, and an external monitoring application or a monitoring application within a queue manager. The monitoring application monitors threads, channels, and events in the message queuing system, polls the performance queue periodically and counts the number of threads in the case of the external monitoring application, directly gathers current event information in the case of the monitoring application within the queue manager, determines whether both the thread/threads and channel have failed when all threads of an application are missing, and restarts channels that failed after determining that both channels and all threads have failed.
See publication
Tags: IT Strategy
Method of Assessing Restart · US Patent 8,898,520
USPTO
April 24, 2026
See publication
Tags: Transformation
Fake Agile: Why Most Organizations Reduce Agility to a Compliance Exercise
LinkedIn Newsletter
March 09, 2025
Agile Done Right Is a Competitive Advantage—Fake Agile Undermines Market Position
Agile is not just a process; it is a strategic differentiator when implemented correctly. Companies that embed Agile into their business strategy can outlearn, outmaneuver, and outperform competitors. However, many organizations reduce Agile to a compliance exercise, confining it to IT and reinforcing rigid structures that slow them down.
The real reason Agile fails is not team execution—it is leadership misalignment. Without executive alignment, Agile collapses into a delivery mechanism that prioritizes outputs over outcomes.
Common Symptoms of Fake Agile:
Agile teams exist, but decision-making remains centralized.
Success is measured in velocity rather than market impact.
Scaling frameworks amplify dysfunction instead of fixing governance issues.
The Cost of Fake Agile:
Organizations that fall into this trap lose market responsiveness, erode team engagement, and waste millions on Agile transformations that do not deliver meaningful business impact.
What Real Agile Looks Like:
Align Agile to business strategy, not just IT execution.
Redesign governance for adaptive decision-making.
Shift from output-driven metrics to business impact metrics.
Fix leadership alignment before scaling Agile.
Agile is a leadership transformation, not just a team initiative. If leadership refuses to change, agility will remain an illusion. The key question is: Will we lead the transformation, or will we be the reason it fails?
See publication
Tags: Agile, Business Strategy, GRC
The Influence Engine: Method 6 — Why Force Is Usually a Signal Failure
Messaging Middleware Processing 
