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 2018/08/15 15:04:00 UTC

[jira] [Created] (AMQ-7035) Memory usage incorrectly increases when selectors are used in JMX operations

Gary Tully created AMQ-7035:
-------------------------------

             Summary: Memory usage incorrectly increases when selectors are used in JMX operations
                 Key: AMQ-7035
                 URL: https://issues.apache.org/jira/browse/AMQ-7035
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMX
    Affects Versions: 5.15.0
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.16.0


The default MessageEvaluationContext does referencing counting and requires a usage pattern that ends in a call to clear(), this pattern has not been applied in a few places in error. The fix for AMQ-6465 works around the non use of the pattern.

The JMX operations that use a selector do not use that pattern and hence can leak a reference count.

The NonCachedMessageEvaluation context does away with the reference count and this is used in most places. I think it should be used everywhere, the whole selector cache idea never got completed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)