You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/05/07 18:35:15 UTC

[jira] [Updated] (AMQ-4518) Expired Message check being done when its not really needed [Performance Issue]

     [ https://issues.apache.org/jira/browse/AMQ-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQ-4518:
------------------------------

    Issue Type: Improvement  (was: Bug)
    
> Expired Message check being done when its not really needed [Performance Issue]
> -------------------------------------------------------------------------------
>
>                 Key: AMQ-4518
>                 URL: https://issues.apache.org/jira/browse/AMQ-4518
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.8.0
>            Reporter: Timothy Bish
>            Priority: Minor
>
> There are cases now where we are checking for expired Messages and DLQ'ing then and sending advisories when we don't really need to.  One example is on destroy of a TempQueue we call purge in Queue which will end up removing all messages for the sake of freeing up their MemoryUsage but we end up processing expired Messages in this case which doesn't make a lot of sense since the destination is going away.  More generally a do we really want to process expired on a Purge call?
> These expired Messages lead to advisories and DLQ'd Message that might not really need to be done. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira