DELIVERY ACKNOWLEDGMENT IN EVENT STREAM PROCESSING

• US 20140280986A1
• Filed: 08/02/2013
• Published: 09/18/2014
• Est. Priority Date: 03/12/2013
• Status: Active Grant

• Current Assignee: SAS Institute Incorporated
• Original Assignee: SAS Institute Incorporated
• Inventors: Deters, Vincent L., Baulier, Gerald Donald, Kolodzieski, Scott J.
• Granted Patent: US 10,102,028 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A method of acknowledging receipt of an event block object is provided. First connection information for connecting to an event stream processing (ESP) engine executing at a first computing device is received. A first connection to the ESP engine is established using the received first connection information. Second connection information for connecting to a publishing client executing at a second computing device is received. A second connection to the publishing client is established using the received second connection information, wherein the first connection differs from the second connection. An event block object is received from the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object. Successful processing of the event block object is determined. Responsive to the successful processing determination, an acknowledgment message including the unique identifier is sent to the publishing client using the established second connection.

Claims

1. A computer-readable medium having stored thereon computer-readable instructions that when executed by a computing device cause the computing device to:

receive first connection information for connecting to an event stream processing (ESP) engine executing at a first computing device;

establish a first connection to the ESP engine using the received first connection information;

receive second connection information for connecting to a publishing client executing at a second computing device;

establish a second connection to the publishing client using the received second connection information, wherein the first connection differs from the second connection;

receive an event block object from the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object;

determine that the event block object is successfully processed; and

responsive to the determination, send an acknowledgment message to the publishing client using the established second connection, wherein the acknowledgement message includes the unique identifier.

2. The computer-readable medium of claim 1, wherein the first computing device and the second computing device are the same computing device.

3. The computer-readable medium of claim 1, wherein the first computing device and the computing device are the same computing device.

4. The computer-readable medium of claim 1, wherein the second computing device and the computing device are the same computing device.

5. The computer-readable medium of claim 1, wherein the first connection information includes a host identifier and a port number.

6. The computer-readable medium of claim 1, wherein the second connection information includes a host identifier and a port number.

7. The computer-readable medium of claim 1, wherein the second connection information is received from an instance of a subscription application.

8. The computer-readable medium of claim 7, wherein the determination that the event block object is successfully processed is performed by the instance of the subscription application.

9. The computer-readable medium of claim 7, wherein the computer-readable instructions further cause the computing device to:

forward the received event stream to the instance of the subscription application; and

receive an indicator that the event block object was successfully processed from the instance of the subscription application, wherein the determination is based on the received indicator.

10. The computer-readable medium of claim 7, wherein the second connection information is received by reading a configuration file identified by the instance of the subscription application.

11. The computer-readable medium of claim 1, wherein the event block object further includes third connection information and the computer-readable instructions further cause the computing device to select the established second connection based on a comparison between the received second connection information and the third connection information.

12. A computer-readable medium having stored thereon computer-readable instructions that when executed by a computing device cause the computing device to:

receive first connection information for connecting to an event stream processing (ESP) engine executing at a first computing device;

establish a first connection to the ESP engine using the received first connection information;

establish a second connection to a subscribing client executing at a second computing device, wherein the first connection differs from the second connection;

publish an event block object to the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object; and

receive an acknowledgment message from the subscribing client through the established second connection, wherein the acknowledgement message includes the unique identifier.

13. The computer-readable medium of claim 12, wherein the first computing device and the second computing device are the same computing device.

14. The computer-readable medium of claim 12, wherein the first computing device and the computing device are the same computing device.

15. The computer-readable medium of claim 12, wherein the second computing device and the computing device are the same computing device.

16. The computer-readable medium of claim 12, wherein the first connection information includes a host identifier and a port number.

17. The computer-readable medium of claim 12, wherein the second connection information includes a host identifier and a port number.

18. The computer-readable medium of claim 12, wherein the computer-readable instructions further cause the computing device to:

increment a counter to determine a number of acknowledgement messages received;

compare the number of acknowledgement messages received to a number of acknowledgement messages specified for the unique identifier;

determine if the number of acknowledgement messages received equals the number of acknowledgement messages specified for the unique identifier; and

execute a successful callback function if the number of acknowledgement messages received equals the number of acknowledgement messages specified for the unique identifier.

19. The computer-readable medium of claim 18, wherein the computer-readable instructions further cause the computing device to:

determine if the number of acknowledgement messages received is less than the number of acknowledgement messages specified for the unique identifier;

responsive to determining that the number of acknowledgement messages received is less than the number of acknowledgement messages specified for the unique identifier, determine if a timeout period has expired; and

responsive to determining that the timeout period has expired, execute an unsuccessful callback function.

20. The computer-readable medium of claim 12, wherein the third connection information is received by reading a configuration file identified by an instance of a publishing application.

21. A system comprising:

a first computing device comprising

a first processor; and

a first computer-readable medium operably coupled to the first processor, the first computer-readable medium having first computer-readable instructions stored thereon that, when executed by the first processor, cause the first computing device to

receive first connection information for connecting to an event stream processing (ESP) engine executing at a second computing device;

establish a first connection to the ESP engine using the received first connection information;

receive second connection information for connecting to a publishing client executing at a third computing device;

establish a second connection to the publishing client using the received second connection information, wherein the first connection differs from the second connection;

receive an event block object from the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object;

determine that the event block object is successfully processed; and

responsive to the determination, send an acknowledgment message to the publishing client using the established second connection, wherein the acknowledgement message includes the unique identifier; and

the second computing device, which comprises

a second processor; and

a second computer-readable medium operably coupled to the second processor, the second computer-readable medium having second computer-readable instructions stored thereon that, when executed by the second processor, cause the second computing device to

receive an initial event block object from the publishing client;

process the initial event block object to form the event block object; and

send the formed event block object to the first computing device using the established first connection.

22. The system of claim 21, wherein the event block object further includes third connection information and the first computer-readable instructions further cause the first computing device to select the established second connection based on a comparison between the received second connection information and the third connection information.

23. The system of claim 21, further comprising the third computing device, which comprises:

a third processor; and

a third computer-readable medium operably coupled to the third processor, the third computer-readable medium having third computer-readable instructions stored thereon that, when executed by the third processor, cause the third computing device to

receive third connection information for connecting to the ESP engine executing at the second computing device;

establish a third connection to the ESP engine using the received third connection information wherein the third connection differs from the first connection and the third connection differs from the second connection;

publish the event block object to the ESP engine using the established third connection; and

receive the acknowledgment message through the established second connection.

24. The system of claim 23, wherein the third computer-readable instructions further cause the third computing device to:

increment a counter to determine a number of acknowledgement messages received;

compare the number of acknowledgement messages received to a number of acknowledgement messages specified for the unique identifier;

determine if the number of acknowledgement messages received equals the number of acknowledgement messages specified for the unique identifier; and

execute a successful callback function if the number of acknowledgement messages received equals the number of acknowledgement messages specified for the unique identifier.

25. The system of claim 24, wherein the third computer-readable instructions further cause the third computing device to:

determine if the number of acknowledgement messages received is less than the number of acknowledgement messages specified for the unique identifier;

responsive to determining that the number of acknowledgement messages received is less than the number of acknowledgement messages specified for the unique identifier, determine if a timeout period has expired; and

responsive to determining that the timeout period has expired, execute an unsuccessful callback function.

26. A method of acknowledging receipt of an event block object, the method comprising:

receiving first connection information for connecting to an event stream processing (ESP) engine executing at a first computing device;

establishing a first connection to the ESP engine using the received first connection information;

receiving second connection information for connecting to a publishing client executing at a second computing device;

establishing a second connection to the publishing client using the received second connection information, wherein the first connection differs from the second connection;

receiving an event block object from the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object;

determining that the event block object is successfully processed; and

responsive to the determination, sending an acknowledgment message to the publishing client using the established second connection, wherein the acknowledgement message includes the unique identifier.

27. A method of confirming receipt of an event block object, the method comprising:

receiving first connection information for connecting to an event stream processing (ESP) engine executing at a first computing device;

establishing a first connection to the ESP engine using the received first connection information;

establishing a second connection to a subscribing client executing at a second computing device, wherein the first connection differs from the second connection;

publishing an event block object to the ESP engine using the established first connection, wherein the event block object includes a unique identifier for the event block object; and

receiving an acknowledgment message from the subscribing client through the established second connection, wherein the acknowledgement message includes the unique identifier.