Message processing using dynamic load balancing queues in a messaging system

• US 9,807,015 B2
• Filed: 03/19/2014
• Issued: 10/31/2017
• Est. Priority Date: 03/19/2014
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Pathak, Anshuman, Srinivasan, Balasubramanian, Nagabushana, Gautham Devanga
• Primary Examiner(s): Srivastava, Vivek
• Assistant Examiner(s): Barker, Todd L
• Application Number:
  US14/219,771
• Publication Number:
  US 20150271256A1
• Time in Patent Office: 1,322 Days
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes
• CPC Class Codes: H04L 47/6225 Fixed service order, e.g. Round Robin

Abstract

A system, method, and computer-readable medium are disclosed for dynamically managing message queues to balance processing loads in a message-oriented middleware environment. A first source message associated with a first target is received, followed by generating a first dynamic load balancing message queue when a first message queue associated with the first target is determined to not be optimal. The first dynamic load balancing message queue is then associated with the first target, followed by enqueueing the first source message to the first dynamic load balancing message queue for processing by the first target.

Claims

1. A computer-implementable method for dynamically managing message queues in a dynamic message-oriented middleware environment, the dynamic message-oriented middleware environment comprising a plurality of message queues and a plurality of dynamic load balancing message queues, comprising:

receiving a first source message associated with a first target;

generating a first dynamic load balancing message queue when a first message queue is determined not to be optimal, the first message queue associated with the first target, the first message queue comprising a first application message queue and at least one of a respective first queue listener and a respective first application queue consumer;

associating the first dynamic load balancing message queue with the first target;

enqueueing the first source message to the first dynamic load balancing message queue for processing by the first target, the enqueueing the first source message being performed via a message queue router, the message queue router enqueueing the first source message according to routing rules;

receiving a second source message associated with a second target;

generating a second dynamic load balancing message queue when a second message queue is determined not to be optimal, the second message queue associated with the second target, the second message queue comprising a second application message queue and at least one of a respective second queue listener and a second application queue consumer, the generating the second dynamic load balancing message queue being performed when at least one of a predetermined message queue contention threshold is reached and when a predetermined message queue backlog value is reached;

associating the second dynamic load balancing message queue with the second target;

enqueueing the second source message to the second dynamic load balancing message queue for processing by the second target; and

,

performing a dynamic message queue management operation in the message-oriented middleware environment based upon the receiving the first source message, generating the first dynamic load balancing message queue, associating the first dynamic load balancing message queue, enqueueing the first source message, the receiving the second source message, generating the second dynamic load balancing message queue, associating the second dynamic load balancing message queue, and enqueueing the second source message, the dynamic message queue management operation being performed by a dynamic message queue management system, the dynamic message queue management system comprising a load balancer, the load balancer identifying and routing a message load to one of the first message queue, the second message queue, the first dynamic load balancing message queue and the second dynamic load balancing message queue, the load balancer comprising at least one of a business-specific load balancer and a domain-specific load balancer.

2. The method of claim 1, further comprising:

receiving a third source message associated with the first target;

generating a third dynamic load balancing message queue when the first message queue and the first dynamic load balancing message queue are determined to not be optimal;

associating the third dynamic load balancing message queue with the first target; and

enqueueing the third source message to the third dynamic load balancing message queue for processing by the first target.

3. The method of claim 2, further comprising:

receiving a fourth source message associated with the second target;

generating a fourth dynamic load balancing message queue when the second message queue and the second dynamic load balancing message queue are determined to not be optimal;

associating the fourth dynamic load balancing message queue with the second target; and

enqueueing the fourth source message to the fourth dynamic load balancing message queue for processing by the second target.

4. The method of claim 3, further comprising:

associating the third dynamic load balancing message queue with the second target when the third dynamic load balancing message queue is determined to be more optimal than the second message queue, the second dynamic load balancing message queue, and the fourth dynamic load balancing message queue; and

enqueueing the fourth source message to the third dynamic load balancing message queue for processing by the second target.

5. The method of claim 4, further comprising:

associating the fourth dynamic load balancing message queue with the first target when the fourth dynamic load balancing message queue is determined to be more optimal than the first message queue, the first dynamic load balancing message queue, and the third dynamic load balancing message queue; and

enqueueing the third source message to the fourth dynamic load balancing message queue for processing by the first target.

6. A system comprising:

a processor;

a data bus coupled to the processor; and

a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations for dynamically managing message queues in a dynamic message-oriented middleware environment, the dynamic message-oriented middleware environment comprising a plurality of message queues and a plurality of dynamic load balancing message queues and comprising instructions executable by the processor and configured for;

receiving a first source message associated with a first target;

generating a first dynamic load balancing message queue when a first message queue is determined not to be optimal, the first message queue associated with the first target, the first message queue comprising a first application message queue and at least one of a respective first queue listener and a respective first application queue consumer;

associating the first dynamic load balancing message queue with the first target;

enqueueing the first source message to the first dynamic load balancing message queue for processing by the first target; and

,

receiving a second source message associated with a second target;

generating a second dynamic load balancing message queue when a second message queue is determined not to be optimal, the second message queue associated with the second target, the second message queue comprising a second application message queue and at least one of a respective second queue listener and a second application queue consumer, the generating the second dynamic load balancing message queue being performed when at least one of a predetermined message queue contention threshold is reached and when a predetermined message queue backlog value is reached;

associating the second dynamic load balancing message queue with the second target;

enqueueing the second source message to the second dynamic load balancing message queue for processing by the second target; and

,

performing a dynamic message queue management operation in the message-oriented middleware environment based upon the receiving the first source message, generating the first dynamic load balancing message queue, associating the first dynamic load balancing message queue, enqueueing the first source message, the receiving the second source message, generating the second dynamic load balancing message queue, associating the second dynamic load balancing message queue, and enqueueing the second source message, the dynamic message queue management operation being performed by a dynamic message queue management system, the dynamic message queue management system comprising a load balancer, the load balancer identifying and routing a message load to one of the first message queue, the second message queue, the first dynamic load balancing message queue and the second dynamic load balancing message queue, the load balancer comprising at least one of a business-specific load balancer and a domain-specific load balancer.

7. The system of claim 6, further comprising:

receiving a third source message associated with the first target;

generating a third dynamic load balancing message queue when the first message queue and the first dynamic load balancing message queue are determined to not be optimal;

associating the third dynamic load balancing message queue with the first target; and

enqueueing the third source message to the third dynamic load balancing message queue for processing by the first target.

8. The system of claim 7, further comprising:

receiving a fourth source message associated with the second target;

generating a fourth dynamic load balancing message queue when the second message queue and the second dynamic load balancing message queue are determined to not be optimal;

associating the fourth dynamic load balancing message queue with the second target; and

enqueueing the fourth source message to the fourth dynamic load balancing message queue for processing by the second target.

9. The system of claim 8, further comprising:

associating the third dynamic load balancing message queue with the second target when the third dynamic load balancing message queue is determined to be more optimal than the second message queue, the second dynamic load balancing message queue, and the fourth dynamic load balancing message queue; and

enqueueing the fourth source message to the third dynamic load balancing message queue for processing by the second target.

10. The system of claim 9, further comprising:

associating the fourth dynamic load balancing message queue with the first target when the fourth dynamic load balancing message queue is determined to be more optimal than the first message queue, the first dynamic load balancing message queue, and the third dynamic load balancing message queue; and

enqueueing the third source message to the fourth dynamic load balancing message queue for processing by the first target.

11. A non-transitory, computer-readable storage medium embodying computer program code for dynamically managing message queues in a dynamic message-oriented middleware environment, the dynamic message-oriented middleware environment comprising a plurality of message queues and a plurality of dynamic load balancing message queues, the computer program code comprising computer executable instructions configured for:

receiving a first source message associated with a first target;

generating a first dynamic load balancing message queue when a first message queue is determined not to be optimal, the first message queue associated with the first target, the first message queue comprising a first application message queue and at least one of a respective first queue listener and a respective first application queue consumer;

associating the first dynamic load balancing message queue with the first target;

enqueueing the first source message to the first dynamic load balancing message queue for processing by the first target; and

,

receiving a second source message associated with a second target;

generating a second dynamic load balancing message queue when a second message queue is determined not to be optimal, the second message queue associated with the second target, the second message queue comprising a second application message queue and at least one of a respective second queue listener and a second application queue consumer, the generating the second dynamic load balancing message queue being performed when at least one of a predetermined message queue contention threshold is reached and when a predetermined message queue backlog value is reached;

associating the second dynamic load balancing message queue with the second target;

enqueueing the second source message to the second dynamic load balancing message queue for processing by the second target; and

,

performing a dynamic message queue management operation in the message-oriented middleware environment based upon the receiving the first source message, generating the first dynamic load balancing message queue, associating the first dynamic load balancing message queue, enqueueing the first source message, the receiving the second source message, generating the second dynamic load balancing message queue, associating the second dynamic load balancing message queue, and enqueueing the second source message, the dynamic message queue management operation being performed by a dynamic message queue management system, the dynamic message queue management system comprising a load balancer, the load balancer identifying and routing a message load to one of the first message queue, the second message queue, the first dynamic load balancing message queue and the second dynamic load balancing message queue, the load balancer comprising at least one of a business-specific load balancer and a domain-specific load balancer.

12. The non-transitory, computer-readable storage medium of claim 11, further comprising:

receiving a third source message associated with the first target;

generating a third dynamic load balancing message queue when the first message queue and the first dynamic load balancing message queue are determined to not be optimal;

associating the third dynamic load balancing message queue with the first target; and

enqueueing the third source message to the third dynamic load balancing message queue for processing by the first target.

13. The non-transitory, computer-readable storage medium of claim 12, further comprising:

receiving a fourth source message associated with the second target;

generating a fourth dynamic load balancing message queue when the second message queue and the second dynamic load balancing message queue are determined to not be optimal;

associating the fourth dynamic load balancing message queue with the second target; and

enqueueing the fourth source message to the fourth dynamic load balancing message queue for processing by the second target.

14. The non-transitory, computer-readable storage medium of claim 13, further comprising:

associating the third dynamic load balancing message queue with the second target when the third dynamic load balancing message queue is determined to be more optimal than the second message queue, the second dynamic load balancing message queue, and the fourth dynamic load balancing message queue; and

enqueueing the fourth source message to the third dynamic load balancing message queue for processing by the second target.

15. The non-transitory, computer-readable storage medium of claim 14, further comprising:

associating the fourth dynamic load balancing message queue with the first target when the fourth dynamic load balancing message queue is determined to be more optimal than the first message queue, the first dynamic load balancing message queue, and the third dynamic load balancing message queue; and

enqueueing the third source message to the fourth dynamic load balancing message queue for processing by the first target.