[
https://issues.apache.org/jira/browse/ARTEMIS-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911437#comment-16911437
]
ASF subversion and git services commented on ARTEMIS-2451:
----------------------------------------------------------
Commit 2fe565f378be904a352db71cf45ed32f704db747 in activemq-artemis's branch
refs/heads/master from Justin Graham Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=2fe565f ]
ARTEMIS-2451 eliminate knownDestinations 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: 6h 20m
> 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)
