Queuing Connector for Message Integrity and Error Tracing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current message queuing systems, such as IBM's MQ SERIES, face issues like message loss due to server failures, performance degradation from increased polling, and complex error tracing across multiple queues, especially when using trigger initialized messaging techniques and lack of efficient administrative tools for diagnosing problems.
Innovation Solution
A queuing connector system that utilizes a publication/subscription notification architecture, coupled with a wrapper process to translate between different notification types, reduces the load on business components by managing message delivery and error tracking through a standardized Java Message Service (JMS) interface, and logs records for error analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If trigger initialized message queuing is used to notify server processes, then message delivery efficiency is improved, but message loss occurs during server failures
Solution Approach 1:
The system establishes a trigger flag in advance that remains dormant until needed. When server failure is detected, this pre-positioned trigger initiates a compensatory action by sending a test message to verify queue integrity, thus cushioning against message loss without affecting normal efficient operation.
Solution Approach 2:
The system implements a feedback mechanism where the server process sends test messages to the queue and waits for acknowledgment. This feedback loop allows the system to detect and respond to queue failures, ensuring message integrity while maintaining the efficiency of trigger-initialized messaging during normal operation.
2Reliability
If polling is increased to detect queue messages, then message delivery reliability is improved, but performance degradation occurs
Solution Approach 1:
Instead of continuous or frequent polling, the system uses periodic action by only initiating queue verification when specific triggers occur (such as server failure detection). This approach maintains reliability by checking message integrity when needed while avoiding the performance degradation associated with continuous polling during normal operation.
Solution Approach 2:
The server process performs self-verification by sending test messages to its own queue and checking for acknowledgment. This self-service approach eliminates the need for external polling mechanisms, maintaining reliability through autonomous verification while preserving system performance by avoiding additional polling overhead.
3Adaptability or versatility
If multiple queues are used for message routing, then message processing versatility is improved, but error tracing complexity increases
Solution Approach 1:
The test message mechanism serves multiple functions: it verifies queue integrity, detects server failures, traces message routing paths, and validates the trigger-initialized messaging system. This universal approach allows the system to handle multiple queues for versatile message processing while using a single unified verification method to simplify error tracing across all queues.
Data Source
AI summary
A system for delivering messages to a business component is provided. A Java Message Service (JMS) enabled connector from a first JMS enabled queue, and from a second queue, a file based queue using a polling notification type of architecture, which will act as a JMS enabled queue with a publication/subscription notification type of architecture through the use of a JMS enabled wrapper which acts on the second queue. The JMS enabled connector serves as the interface to the business component, and is operable to transform the message, and further operable to record, in a standard format, information about messages delivered from the first queue and from the second queue. A method for delivering messages to a business component is also provided.