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/20 15:03:00 UTC

[jira] [Resolved] (ARTEMIS-2451) eliminate knownDestinations cache

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

Justin Bertram resolved ARTEMIS-2451.
-------------------------------------
    Fix Version/s: 2.10.0
       Resolution: Fixed

> 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
>             Fix For: 2.10.0
>
>          Time Spent: 6.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
(v8.3.2#803003)