Reply-Queue Aggregation for Efficient Timeout Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing integration environments face computational workload and time inefficiencies during timeout processing for aggregation messaging due to the aggregation of response messages at intermediate queues, which increases CPU intensity and reduces the speed of response delivery to requesting applications.
Innovation Solution
The response messages are aggregated at the reply queue rather than the intermediate queue, with the timeout process and release controlled by the messaging system, allowing parallel execution and reducing computational workload.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If response messages are aggregated at an intermediate queue, then message routing and delivery can be controlled, but computational workload increases and time to provide responses to requesting applications increases
Solution Approach 1:
The patent extracts the aggregation function from the intermediate queue and moves it to the reply queue. The messaging system directly aggregates response messages at the reply queue, eliminating the need to hold and process messages at the intermediate queue level, thus reducing computational workload while maintaining routing control.
Solution Approach 2:
The patent introduces a timeout process as an intermediary mechanism that mediates between message arrival and response delivery. This timeout process automatically manages the aggregation and release of messages based on time conditions, reducing manual computational intervention while ensuring reliable message routing.
2Ease of operation
If aggregation is performed at an intermediate queue, then message flow can be managed, but CPU intensity increases during timeout processing
Solution Approach 1:
The messaging system performs self-service by automatically aggregating and managing response messages at the reply queue without requiring external intervention. The timeout process autonomously handles message release when conditions are met, eliminating CPU-intensive manual aggregation operations while maintaining ease of message flow management.
Solution Approach 2:
The system performs preliminary aggregation of response messages at the reply queue before timeout occurs. By pre-positioning messages in the reply queue with aggregation identifiers, the system avoids CPU-intensive operations during timeout processing, as the messages are already organized and ready for release.
3Measurement precision
If messages are held in the reply queue until timeout expiration, then response accuracy is improved, but time to deliver responses increases
Solution Approach 1:
The patent implements dynamic message release based on timeout conditions. Messages are held in the reply queue only for the necessary duration to ensure accurate aggregation, then automatically released when the timeout process expires or expected responses are received. This dynamic approach balances accuracy requirements with time efficiency.
Data Source
AI summary
A method includes: receiving an initial request message in a request queue of the messaging system; receiving an aggregation reply message in a reply queue of the messaging system, wherein the aggregation reply message is received from an integration system that processes the initial request message, and wherein the aggregation reply message includes an aggregation identifier associated with the initial request message; in response to receiving the aggregation reply message, starting a timeout process; monitoring the timeout process; holding one or more messages that are in the reply queue and that include the aggregation identifier until the timeout process expires or an expected number of responses has been received; and making available the one or more messages that are in the reply queue and that include the aggregation identifier based on the timeout process expiring or the expected number of responses having been received.