[
https://issues.apache.org/jira/browse/ARTEMIS-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903222#comment-16903222
]
ASF subversion and git services commented on ARTEMIS-2449:
----------------------------------------------------------
Commit 9d44c40037cf299e77e19993a5dbd422fcff16e9 in activemq-artemis's branch
refs/heads/master from Justin Graham Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9d44c40 ]
ARTEMIS-2449 limit size of producer details
The core server session tracks details about producers like what
addresses have had messages sent to them, the most recent message ID
sent to each address, and the number of messages sent to each address.
This information is made available to users via the
listProducersInfoAsJSON method on the various management interfaces
(JMX, web console, etc.). However, in situations where a server session
is long lived (e.g. in a pool) and is used to send to many different
addresses (e.g. randomly named temporary JMS queues) this info can
accumulate to a problematic degree. Therefore, we should limit the
amount of producer details saved by the session.
> Limit size of producer details
> ------------------------------
>
> Key: ARTEMIS-2449
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2449
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.9.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The core server session tracks details about producers like what addresses
> have had messages sent to them, the most recent message ID sent to each
> address, and the number of messages sent to each address. This information is
> made available to users via the {{listProducersInfoAsJSON}} method on the
> various management interfaces (JMX, web console, etc.). However, in
> situations where a server session is long lived (e.g. in a pool) and is used
> to send to many different addresses (e.g. randomly named temporary JMS
> queues) this info can accumulate to a problematic degree. Therefore, we
> should limit the amount of producer details saved by the session.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
