Tidy up housekeeping configuration option for scheduling frequency:
expiredMessageCheckPeriod vs checkPeriod
------------------------------------------------------------------------------------------------------------
Key: QPID-3266
URL: https://issues.apache.org/jira/browse/QPID-3266
Project: Qpid
Issue Type: Task
Components: Java Broker
Affects Versions: 0.10
Reporter: Keith Wall
Assignee: Robbie Gemmell
Priority: Minor
QPID-430 renamed the configuration option controlling the frequency of the
housekeeping thread from expiredMessageCheckPeriod to checkPeriod to reflect
that fact that the Housekeeping thread had acquired more responsibilities.
Unfortunately it appears that there difficulties during a merge and we are now
left with different configuration names at different levels within the
configuration.
At <broker/housekeeping> we have:
<checkPeriod/>
and
<expiredMessageCheckPeriod/> (supported as a synonym of checkPeriod)
whereas at <virtualhost/housekeeping> we support only:
<expiredMessageCheckPeriod/>
The task is to clean up the configuration classes. I suggest that we
standardise on <checkPeriod/> and issue a clear warning if the old option is
encountered.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
