You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2019/08/16 13:23:00 UTC
[jira] [Updated] (ARTEMIS-2451) eliminate knownDestinations cache
[ https://issues.apache.org/jira/browse/ARTEMIS-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-2451:
------------------------------------
Summary: eliminate knownDestinations cache (was: Limit size of destination cache)
> eliminate knownDestinations cache
> ---------------------------------
>
> Key: ARTEMIS-2451
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2451
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> This is the client-side version of ARTEMIS-2449. Simply put, there is no limit on the destination cache for a core JMS client. For a long-lived connection sending to lots of different destinations (e.g. in a request-reply use-case involving temporary queues) this can present a significant problem.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)