You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2011/05/19 16:36:48 UTC

[jira] [Created] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod

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:dev-subscribe@qpid.apache.org


[jira] [Updated] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall updated QPID-3266:
-----------------------------

    Attachment: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch

> 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: Keith Wall
>            Priority: Minor
>         Attachments: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch
>
>
> 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:dev-subscribe@qpid.apache.org


[jira] [Updated] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall updated QPID-3266:
-----------------------------

    Attachment:     (was: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch)

> 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: Keith Wall
>            Priority: Minor
>         Attachments: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch
>
>
> 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:dev-subscribe@qpid.apache.org


[jira] [Assigned] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall reassigned QPID-3266:
--------------------------------

    Assignee: Keith Wall  (was: Robbie Gemmell)

> 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: Keith Wall
>            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:dev-subscribe@qpid.apache.org


[jira] [Updated] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall updated QPID-3266:
-----------------------------

    Attachment: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch

Proposed patch to resolve this Jira.

> 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: Keith Wall
>            Priority: Minor
>         Attachments: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch
>
>
> 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:dev-subscribe@qpid.apache.org


[jira] [Resolved] (QPID-3266) Tidy up housekeeping configuration option for scheduling frequency: expiredMessageCheckPeriod vs checkPeriod

Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Wall resolved QPID-3266.
------------------------------

    Resolution: Fixed

Patch applied.

> 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: Keith Wall
>            Priority: Minor
>         Attachments: 0001-QPID-3266-Tidy-up-housekeeping-configuration-option-.patch
>
>
> 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:dev-subscribe@qpid.apache.org