You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2015/06/11 12:53:01 UTC

[jira] [Resolved] (AMQ-3565) Timeout JMSXGroupID (ie. automatic close of group)

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

Gary Tully resolved AMQ-3565.
-----------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 6.0.0)
                   5.9.0

Note the org.apache.activemq.broker.region.group.CachedMessageGroupMapFactory

where groups are in an LRU that can get evicted.

> Timeout JMSXGroupID (ie. automatic close of group)
> --------------------------------------------------
>
>                 Key: AMQ-3565
>                 URL: https://issues.apache.org/jira/browse/AMQ-3565
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: all, Linux most desired
>            Reporter: Roger Fischer
>              Labels: features
>             Fix For: 5.9.0
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> In some cases it is not practical to explicitly close a message group. It would be convenient if the message group were automatically closed after a time with no messages in the group.
> Essentially this creates the usage pattern: load balancing with time-limited affinity.
> PS: I have no idea what effort would be required, but cannot enter "unknown" in "Original Estimate".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)