[QPID-2638] Add topic configuration processing to allow Slow Consumer Detection to be configurable per topic

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Later
• Fix Version/s: JIRA Cleanup
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Martin Ritchie
• Created: 02/Jun/10 13:17
• Updated: 05/Sep/11 21:46
• Resolved: 05/Sep/11 21:46

Description

Currently there is no way to configure topics this presents a problem for the configuration of the slow consumer detection for topics.

Following the desing documented here:
https://cwiki.apache.org/confluence/display/qpid/Topic+Configuration+Design

The plan is to implement simply add the <topic> section to the configuration and a TopicConfiguration class that will process start the processing of that configuration. The additional items described in the overal topic configuration design are not in scope for this change.

The TopicConfiguration will be hierarchical just as as the topic version is so the configuration will load in the following strucutre.

NamedQueue->NamedTopic->GeneralTopic->GeneralQueue

This means that you can have a configuration for a given topic but if you specify configuration for a specific durable subscription through the named queue configuration this will take presidence.