[
https://issues.apache.org/jira/browse/AMQ-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581224#comment-16581224
]
ASF subversion and git services commented on AMQ-7035:
------------------------------------------------------
Commit 50d27e7e545d30bc0d35f8dd8baf15b33522c33a in activemq's branch
refs/heads/master from gtully
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=50d27e7 ]
AMQ-7035 - use NonCachedMessageEvaluationContext in place of
MessageEvaluationContext to avoid unnecessary reference count management and
subsequent leaks. Rework AMQ-6465 with additional JMX related tests
> 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
> Priority: Major
> 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)
