Dynamic message retrieval by subdividing a message queue into sub-queues

• US 9,049,164 B2
• Filed: 05/30/2013
• Issued: 06/02/2015
• Est. Priority Date: 03/20/2012
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Colar, Gerald D., Diggs, Melanie R., White, Terrence E., Young, Charles K.
• Primary Examiner(s): Barry, Lance L
• Application Number:
  US13/906,102
• Publication Number:
  US 20130254318A1
• Time in Patent Office: 733 Days
• Field of Search: 709213-215, 710 52- 57
• US Class Current: 1/1
• CPC Class Codes: H04L 47/622 Queue service order
• CPC Class Codes: H04L 47/6235 Variable service order
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes

Abstract

Exemplary embodiments provide methods and systems for dynamically changing a message retrieval scheme during runtime in a client/server electronic messaging system in which the server executes a message retrieval component and incoming messages received from the client is stored in a message queue. Aspects of the exemplary embodiment include accessing messaging business rules from a memory by a message retrieval component at runtime, wherein the messaging business rules define a primary retrieval scheme and a secondary retrieval scheme, and wherein a value provided for each of the primary retrieval scheme and the secondary retrieval scheme are selected from a combination of different message retrieval types including: First In First Out (FIFO), Last In First Out (LIFO), and random. The message retrieval component subdivides the message queue into sub-queues based on at least one of a message quantity limit and a message received time limit specified in the business rules. Each of the sub-queues is then accessed using the value of the secondary retrieval scheme; and messages from each of the sub-queues are retrieved using the value of the primary retrieval scheme.

Claims

1. A method for dynamically changing a message retrieval scheme during runtime in a client/server electronic messaging system in which the server executes a message retrieval component and incoming messages received from the client is stored in a message queue, the method comprising:

accessing messaging business rules from a memory by the message retrieval component at runtime, wherein the messaging business rules define a primary retrieval scheme and a secondary retrieval scheme, and wherein a value provided for each of the primary retrieval scheme and the secondary retrieval scheme are selected from a combination of different message retrieval types including;

First In First Out (FIFO), Last In First Out (LIFO), and random;

subdividing the message queue into sub-queues based on at least one of a message quantity limit and a message received time limit specified in the messaging business rules;

accessing each of the sub-queues using the value of the secondary retrieval scheme; and

retrieving messages from each of the sub-queues using the value of the primary retrieval scheme.

2. The method of claim 1 wherein accessing messaging business rules further comprises accessing a calendar entry value and at least one of a quantity limit value and a time limit value.

3. The method of claim 2 wherein the message retrieval component uses the calendar entry value to set different retrieval schemes based on calendar dates for multiple time periods.

4. The method of claim 2 wherein the message retrieval component uses the quantity limit value along with the primary and secondary retrieval schemes to set different retrieval schemes based a number of messages received.

5. The method of claim 2 wherein the message retrieval component uses the time limit along with the primary and secondary retrieval schemes to set different retrieval schemes based a number of messages received in a given amount of time.

6. The method of claim 1 wherein possible values for the secondary retrieval scheme include the FIFO, the LIFO, and the random message retrieval types, and NONE.

7. The method of claim 1 further comprising:

accessing by the message retrieval component, a current date timestamp of the server upon startup.

8. The method of claim 7 further comprising:

retrieving by the message retrieval component, a calendar entry from the messaging business rules that is valid for the current date timestamp.

9. The method of claim 7 further comprising:

in response to determining that a value for the secondary retrieval scheme is not available, instructing the messaging system to retrieve messages from the message queue according to the value set for the primary retrieval scheme.

10. The method of claim 1 further comprising:

periodically accessing the messaging business rules to check for updated values.