[JAMES-3070] RabbitMQ MailQueue should not share Receiver for several purpose

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Queue
• Assignee: Unassigned
• Reporter: Matthieu Baechler
• Created: 19/Feb/20 15:55
• Updated: 18/Jun/20 19:50
• Resolved: 18/Jun/20 19:50

Description

"spool" MailQueue is used in several places in James code.

The usage pattern is quite different in those different places.

While trying to control accurately the rate of James dequeue, we found that sharing a single RabbitMQ Receiver can prevent from passing it specific parameters at construction.

We should try make James work without the MailQueue sharing for RabbitMQ.