Granted Patent B2

US 12,554,535 · App. 18/219,926 · Granted Feb 17, 2026

Inventors: Andrea Cosentino (Rome, IT); Paolo Antinori (Novara, IT)

Assignee: Red Hat, LLC

G06F9/4881

Abstract

Claims (60)

1 . A computer-implemented method comprising:

receiving, by an event broker, an event message from a producer device, the event message having a payload and a key;

storing, by the event broker, the event message in an event queue based on the key;

transmitting, by a sender node of the event broker, the event message to an event consumer that is subscribed to receive event messages from the event queue; and

subsequent to transmitting the event message to the event consumer:

causing, by the event broker, the sender node to enter an idle state;

receiving, by the event broker, an error message from the event consumer while the sender node is in the idle state;

in response to receiving the error message, waking, by the event broker, the sender node from the idle state; and

subsequent to waking from the idle state, initiating, by the sender node, a retry process involving iteratively re-transmitting the event message to the event consumer until either a threshold number of retry attempts have been performed or until an acknowledgement message is received from the event consumer.

2 . The computer-implemented method of claim 1 , further comprising:

receiving, by the event broker, a notification from the event consumer, the notification indicating a transmission status of the event message; and

based on receiving the notification, modifying, by the event broker, a transmission status indicator in a lookup table to indicate the transmission status of the event message, the lookup table corresponding to the event queue.

3 . The computer-implemented method of claim 2 , further comprising:

determining, by the event broker and based on the transmission status indicator in the lookup table, that the event message was not transmitted to the event consumer successfully; and

transmitting, by the event broker, the event message to a third-party device that is configured to transmit the event message to the event consumer.

4 . The computer-implemented method of claim 2 , wherein a dispatcher module of the event broker wakes the sender node in response to receiving the error message.

5 . The computer-implemented method of claim 1 , wherein the event broker, the sender node, and the producer device are edge-computing devices in an edge network.

6 . The computer-implemented method of claim 1 , wherein the event broker includes the producer device.

7 . The computer-implemented method of claim 1 , further comprising:

removing, by the event broker and in response to determining that the event message has been successfully transmitted to the event consumer, the event message from the event queue.

8 . A non-transitory computer-readable medium comprising instructions that are executable by one or more processing devices of an event broker for causing the event broker to:

receive an event message from a producer device, the event message having a payload and a key;

store the event message in an event queue based on the key;

transmit, by a sender node of the event broker, the event message to an event consumer that is subscribed to receive event messages from the event queue; and

subsequent to transmitting the event message to the event consumer:

cause the sender node to enter an idle state;

receive an error message from the event consumer while the sender node is in the idle state;

in response to receiving the error message, wake the sender node from the idle state; and

subsequent to waking from the idle state, initiate, by the sender node, a retry process involving iteratively re-transmitting the event message to the event consumer until either a threshold number of retry attempts have been performed or until an acknowledgement message is received from the event consumer.

9 . The non-transitory computer-readable medium of claim 8 , further comprising instructions that are executable by the one or more processing devices for causing the event broker to:

receive a notification from the event consumer, the notification indicating a transmission status of the event message; and

modify a transmission status indicator in a lookup table to indicate to the transmission status of the event message, the lookup table corresponding to the event queue.

10 . The non-transitory computer-readable medium of claim 9 , further comprising instructions that are executable by the one or more processing devices for causing the event broker to:

determine, based on the transmission status indicator in the lookup table, that the event message was not transmitted to the event consumer successfully; and

transmit the event message to a third-party device that is configured to transmit the event message to the event consumer.

11 . The non-transitory computer-readable medium of claim 9 , wherein a dispatcher module of the event broker is configured to wake the sender node from the idle state in response to receiving the error message.

12 . The non-transitory computer-readable medium of claim 8 , wherein the event broker, the sender node, and the producer device are edge-computing devices in an edge network.

13 . The non-transitory computer-readable medium of claim 8 , wherein the event broker includes the producer device.

14 . The non-transitory computer-readable medium of claim 8 , further comprising instructions that are executable by the one or more processing devices for causing the event broker to:

in response to determining that the event message has been successfully transmitted to the event consumer, remove the event message from the event queue.

15 . A system comprising:

one or more processing devices associated with an event broker; and

one or more memories having instructions that are executable by the one or more processing devices for causing the event broker to:

receive an event message from a producer device, the event message having a payload and a key;

store the event message in an event queue based on the key;

transmit, by a sender node of the event broker, the event message to an event consumer that is subscribed to receive event messages from the event queue; and

subsequent to transmitting the event message to the event consumer:

cause the sender node to enter an idle state;

receive an error message from the event consumer while the sender node is in the idle state;

in response to receiving the error message, wake the sender node from the idle state; and

subsequent to waking from the idle state, initiate, by the sender node, a retry process involving iteratively re-transmitting the event message to the event consumer until either a threshold number of retry attempts have been performed or until an acknowledgement message is received from the event consumer.

16 . The system of claim 15 , further comprising instructions that are executable by the one or more processing devices for causing the event broker to:

receive a notification from the event consumer, the notification indicating a transmission status of the event message; and

modify a transmission status indicator in a lookup table to indicate to the transmission status of the event message, the lookup table corresponding to the event queue.

17 . The system of claim 16 , further comprising instructions that are executable by the one or more processing devices for causing the event broker to:

determine, based on the transmission status indicator in the lookup table, that the event message was not transmitted to the event consumer successfully; and

transmit the event message to a third-party device that is configured to transmit the event message to the event consumer.

18 . The system of claim 16 , wherein a dispatcher module of the event broker is configured to wake the sender node from the idle state in response to receiving the error message.

19 . The system of claim 15 , wherein the event broker, the sender node, and the producer device are edge-computing devices in an edge network.

20 . The system of claim 15 , wherein the event broker includes the producer device.

Assignments (1)

Continuity (1)

References Cited (28)