You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (Created) (JIRA)" <ji...@apache.org> on 2011/11/28 15:28:39 UTC

[jira] [Created] (AMQ-3609) Turn inactivity monitor thread off by default

Turn inactivity monitor thread off by default
---------------------------------------------

                 Key: AMQ-3609
                 URL: https://issues.apache.org/jira/browse/AMQ-3609
             Project: ActiveMQ
          Issue Type: Improvement
    Affects Versions: 5.5.0
            Reporter: Dejan Bosanac
             Fix For: 5.6.0


By default schedulePeriodForDestinationPurge is set to run every 5 second, checking every destination if it needs to be checked or deleted. That can put a lot of stress on brokers with many destinations. As for it to actually work properly what it need to do, the separate destination policy changes must be set, so keeping this on by default doesn't make much sense.

We should keep it off by default (0) and set it explicitly if the check is needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (AMQ-3609) Turn inactivity monitor thread off by default

Posted by "Gary Tully (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-3609.
-----------------------------

    Resolution: Fixed

fix in http://svn.apache.org/viewvc?rev=1207239&view=rev

updated doc: https://cwiki.apache.org/confluence/display/ACTIVEMQ/Delete+Inactive+Destinations
                
> Turn inactivity monitor thread off by default
> ---------------------------------------------
>
>                 Key: AMQ-3609
>                 URL: https://issues.apache.org/jira/browse/AMQ-3609
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.5.0
>            Reporter: Dejan Bosanac
>            Assignee: Gary Tully
>             Fix For: 5.6.0
>
>
> By default schedulePeriodForDestinationPurge is set to run every 5 second, checking every destination if it needs to be checked or deleted. That can put a lot of stress on brokers with many destinations. As for it to actually work properly what it need to do, the separate destination policy changes must be set, so keeping this on by default doesn't make much sense.
> We should keep it off by default (0) and set it explicitly if the check is needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (AMQ-3609) Turn inactivity monitor thread off by default

Posted by "Gary Tully (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully reassigned AMQ-3609:
-------------------------------

    Assignee: Gary Tully
    
> Turn inactivity monitor thread off by default
> ---------------------------------------------
>
>                 Key: AMQ-3609
>                 URL: https://issues.apache.org/jira/browse/AMQ-3609
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.5.0
>            Reporter: Dejan Bosanac
>            Assignee: Gary Tully
>             Fix For: 5.6.0
>
>
> By default schedulePeriodForDestinationPurge is set to run every 5 second, checking every destination if it needs to be checked or deleted. That can put a lot of stress on brokers with many destinations. As for it to actually work properly what it need to do, the separate destination policy changes must be set, so keeping this on by default doesn't make much sense.
> We should keep it off by default (0) and set it explicitly if the check is needed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira