[
https://issues.apache.org/jira/browse/ARTEMIS-2451?focusedWorklogId=295313&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-295313
]
ASF GitHub Bot logged work on ARTEMIS-2451:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Aug/19 08:41
Start Date: 15/Aug/19 08:41
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2796:
ARTEMIS-2451 remove need for knownDestination Cache
URL: https://github.com/apache/activemq-artemis/pull/2796#issuecomment-521563091
@jbertram
re:
> BTW, the issue I saw wasn't a leak, per se. It was simply unwanted
accumulation based on the way it was designed.
Won't we get similar issue on the tempoary queue set thats used to track
temp queues in connection? I guess that could probably move into the session
object, so theyre cleaned up as a session is closed, which is anyhow the
lifetime of a temporary queue anyhow.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 295313)
Time Spent: 5h (was: 4h 50m)
> Limit size of destination 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: 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)
