Methods and systems for efficient queue propagation using a single protocol-based remote procedure call to stream a batch of messages

• US 20060056413A1
• Filed: 09/14/2004
• Published: 03/16/2006
• Est. Priority Date: 09/14/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Meiyyappan, Krishnan, Liang, Chao, Gollapudi, Sreenivas, Ahluwalia, Ashwinder Singh, Ikeda, Nancy Reiko, Chldambaran, Lakshminarayanan
• Granted Patent: US 7,546,613 B2
• Time in Patent Office: Days
• US Class Current: 370/392
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

A computer-implemented method of streaming a plurality of messages from a source queue to at least one destination queue over a computer network. The method may include steps of generating a remote procedure call, the remote procedure being configured to encapsulate at least header data, message data for each of the plurality of messages and an end of batch token, the header data being common to each of the plurality of messages and including an identification of the at least one destination queue, the end of batch token signaling that no further message data follows; sending the generated remote procedure call over the computer network to the destination queue identified in the header data, and dequeueing at least the message data for each of the plurality of messages from the source queue and streaming the dequeued messages over the network, and successively enqueueing each streamed message data into the at least one destination queue identified by the header data until the end of batch token is received.

Claims

1. A computer-implemented remote procedure call configured to enable a stream of a plurality of messages to be sent from a source queue accessible by a first computer application to one or more selected remote destination queues accessible to a second computer application over a computer network, the remote procedure call comprising:

a first message header indicator, the first message header indicator being configured to signal that an identity of a first destination queue for messages to be streamed follows;

first header data configured to identify the first destination queue;

a first message body indicator, the first message body indicator being configured to signal that a first message to be streamed to the first destination queue follows;

first message data, the first message data including the first message to be streamed to the first destination queue identified by the first header data;

a second message body indicator, the second message body indicator being configured to signal that a second message to be streamed follows;

second message data, the second message data including the second message to be streamed, and

an end of batch token, the end of batch token signaling the end of the stream of the plurality of messages.

2. The computer-implemented remote procedure call of claim 1, wherein the remote procedure call is configured to stream the second message to the first destination queue.

3. The computer-implemented remote procedure call of claim 1, wherein the remote procedure call is configured to stream the second message to a second destination queue.

4. The computer-implemented remote procedure call of claim 3, further comprising:

a second message header indicator, the second message header indicator being disposed between the first message data and the second message body indicator, the second message header indicator being configured to signal a change in destination queue for the second message, and

second header data configured to identify the second destination queue to which the second message is to be streamed.

5. The computer-implemented remote procedure call of claim 1, further comprising:

a second message header indicator disposed before the end of batch token, the second message header indicator being configured to signal a change in destination queue for messages to follow;

second header data configured to identify a second destination queue;

a same message indicator, the same message indicator indicating that an immediately preceding message data is to be streamed to the second destination queue identified by the second header data.

6. A machine-readable medium having data stored thereon representing sequences of instructions which, when executed by a computing device, causes the computing device to generate a remote procedure call configured to enable a stream of a plurality of messages to be sent from a source queue accessible by a first computer application to one or more selected remote destination queues accessible to a second computer application over a computer network, the remote procedure call comprising:

a first message header indicator, the first message header indicator being configured to signal that an identity of a first destination queue for messages to be streamed follows;

first header data configured to identify the first destination queue;

a first message body indicator, the first message body indicator being configured to signal that a first message to be streamed to the first destination queue follows;

first message data, the first message data including the first message to be streamed to the first destination queue identified by the first header data;

a second message body indicator, the second message body indicator being configured to signal that a second message to be streamed follows;

second message data, the second message data including the second message to be streamed, and

an end of batch token, the end of batch token signaling the end of the stream of the plurality of messages.

7. The machine-readable medium of claim 6, wherein the remote procedure call is configured to stream the second message to the first destination queue.

8. The machine-readable medium of claim 6, wherein the remote procedure call is configured to stream the second message to a second destination queue.

9. The machine-readable medium of claim 8, further comprising:

a second message header indicator, the second message header indicator being disposed between the first message data and the second message body indicator, the second message header indicator being configured to signal a change in destination queue for the second message, and

second header data configured to identify the second destination queue to which the second message is to be streamed.

10. The machine-readable medium of claim 6, further comprising:

a second message header indicator disposed before the end of batch token, the second message header indicator being configured to signal a change in destination queue for messages to follow;

second header data configured to identify a second destination queue, and

a same message indicator, the same message indicator indicating that an immediately preceding message data is to be streamed to the second destination queue identified by the second header data.

11. A computer-implemented method of streaming a plurality of messages from a source queue to at least one destination queue over a computer network, each of the plurality of messages including metadata and message data, the method comprising the steps of:

generating a remote procedure call, the remote procedure being configured to encapsulate at least header data, message data for each of the plurality of messages and an end of batch token, the header data being common to each of the plurality of messages and including an identification of the at least one destination queue, the end of batch token signaling that no further message data follows;

sending the generated remote procedure call over the computer network to the destination queue identified in the header data, and

beginning execution of the remote procedure call by invoking a SQL engine and initiating a single insert statement to enqueue each of the streamed message data into the at least one destination queue identified by the header data, and

dequeueing at least the message data for each of the plurality of messages from the source queue and streaming the dequeued messages over the network, and successively enqueueing each streamed message data into the at least one destination queue identified by the header data until the end of batch token is received.

12. The computer-implemented method of claim 11, further comprising a step of configuring the remote procedure call so as to include only one copy of a message data that is to be sent to more than one destination queue.

14. The computer-implemented method of claim 11, wherein the streaming step is carried out only after the SQL engine has been invoked and the single insert statement initiated.

15. The computer-implemented method of claim 11, further including executing a callback to carry out a row insert for each streamed message data, a memory holding each streamed message data being a SQL insert memory.

16. The computer-implemented method of claim 11, wherein a number of message data streamed to the destination is unknown to the destination queue until the end of batch token is received.

13. The computer-implemented method 11, further comprising a step of configuring the remote procedure call such that a message header indicator and header data precedes each group of message data to be streamed to a same destination queue.