Message delivery in messaging networks
US-9021038-B2 · Apr 28, 2015 · US
US9647972B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9647972-B2 |
| Application number | US-201514641113-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 6, 2015 |
| Priority date | Jan 25, 2008 |
| Publication date | May 9, 2017 |
| Grant date | May 9, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In response to receipt of a request message from a requester, a reply message is created. The reply message includes a message identifier of the request message copied from the received request message. The reply message is published to each of a group of replicated message queues. The reply message is identifiable by the requester using the copied message identifier of the request message on any one of the group of replicated message queues prior to being consumed by the requester.
Opening claim text (preview).
What is claimed is: 1. A method for message delivery in messaging networks, comprising: creating, by a backend messaging manager system executing on one or more processors, a reply message in response to receipt of a request message from a requester via a first one of a plurality of front end messaging manager systems; copying into the reply message, by the backend messaging manager system, a unique message identifier of the request message from the received request message; publishing, by, the backend messaging manager system, the reply message to each of a plurality of replicated message queues, wherein the reply message is received by the requester on any one of the plurality of replicated message queues and wherein the reply message is identifiable by the requester using the copied unique message identifier of the request message on any one of the plurality of replicated message queues prior to being consumed by the requester, and wherein the requester receives the reply message via a second one of the plurality of front end messaging manager systems; determining that the reply message is consumed by the requester via a first replicated message queue of the plurality of replicated message queues; and sending a notification message to the plurality of the replicated message queues, other than the first replicated message queue, wherein the reply message is deleted from each of the plurality of replicated message queues based on receiving the notification message. 2. The method of claim 1 , where publishing the reply message to each of the plurality of replicated message queues comprises sending the reply message to each of a plurality of message managing systems in association with which the plurality of replicated message queues are defined. 3. The method of claim 1 , where the plurality of replicated message queues comprise a first plurality of replicated request message queues and a second plurality of replicated reply message queues, and further comprising: wherein the request message from the requester is received from one of the first plurality of replicated request message queues; and wherein publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of the second plurality of replicated reply message queues. 4. The method of claim 1 , where the request message further comprises a replicated reply-to message queue name identifier that specifies a plurality of replicated reply message queues, and where publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of a plurality of replicated reply message queues named as specified by the replicated reply-to message queue name identifier. 5. The method of claim 1 , where publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of a plurality of queue managers that each host one of the plurality of replicated message queues. 6. The method of claim 1 , where: the plurality of replicated message queues comprise a messaging network with a configured number of replicated message queues; and publishing the reply message to each of the plurality of replicated message queues provides redundant publication of the reply message that facilitates delivery of the reply message to the requester in an event of a failure of message managing systems that host all but one of the configured number of replicated message queues of the messaging network. 7. An apparatus for message delivery in messaging networks, comprising: a communication interface; and a processor programmed to perform operations comprising: creating a reply message, in response to receipt of a request message from a requester via a first one of a plurality of front end messaging manager systems; copying into the reply message, a message identifier of the request message from the received request message; publishing, via the communication interface, the reply message to each of a plurality of replicated message queues, wherein the reply message is received by the requester on any one of the plurality of replicated message queues and wherein the reply message is identifiable by the requester using the copied message identifier of the request message on any one of the plurality of replicated message queues prior to being consumed by the requester, and wherein the requester receives the reply message via a second one of the plurality of front end messaging manager systems; determining that the reply message is consumed by the requester via a first replicated message queue of the plurality of replicated message queues; and sending a notification message to the plurality of the replicated message queues, other than the first replicated message queue, wherein the reply message is deleted from each of the plurality of replicated message queues based on receiving the notification message. 8. The apparatus of claim 7 , where, publishing the reply message to each of the plurality of replicated message queues comprises sending the reply message to each of a plurality of message managing systems in association with which the plurality of replicated message queues are defined. 9. The apparatus of claim 7 , where the plurality of replicated message queues comprise a first plurality of replicated request message queues and a second plurality of replicated reply message queues, and where the operations further comprise: receiving the request message from the requester from one of the first plurality of replicated request message queues; and wherein publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of the second plurality of replicated reply message queues. 10. The apparatus of claim 7 , where the request message further comprises a replicated reply to message queue name identifier that specifies a plurality of replicated reply message queues, and where publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of a plurality of replicated reply message queues named as specified by the replicated reply-to message queue name identifier. 11. The apparatus of claim 7 , where, publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of a plurality of queue managers that each host one of the plurality of replicated message queues. 12. The apparatus of claim 7 , where: the plurality of replicated message queues comprise a messaging network with a configured number of replicated message queues; and publishing the reply message to each of the plurality of replicated message queues provides redundant publication of the reply message that facilitates delivery of the reply message to the requester in an event of a failure of message managing systems that host all but one of the configured number of replicated message queues of the messaging network. 13. A non-transitory computer readable storage medium having computer readable program code embodied therewith, where the computer readable program code when executed on a computer causes the computer to perform operations comprising: creating a reply message, in response to receipt of a request message from a requester via a first one of a plurality of front end messaging manager systems; copying into the reply message, a message identifier of the request message from the received request message; publishing the reply message to each of a plurality of replicated message queues, wherein t
Message adaptation to terminal or network requirements · CPC title
Real-time or near real-time messaging, e.g. instant messaging [IM] · CPC title
Buffering arrangements · CPC title
Electricity · mapped topic
Electricity · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.