[ 
https://issues.apache.org/jira/browse/ARTEMIS-2451?focusedWorklogId=294922&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-294922
 ]

ASF GitHub Bot logged work on ARTEMIS-2451:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Aug/19 18:33
            Start Date: 14/Aug/19 18:33
    Worklog Time Spent: 10m 
      Work Description: jbertram commented on issue #2796: ARTEMIS-2451 remove 
need for knownDestination Cache
URL: https://github.com/apache/activemq-artemis/pull/2796#issuecomment-521365341
 
 
   At first glance this looks like a clever solution and better than the one I 
came up with. Let me review it in more detail.
 
----------------------------------------------------------------
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: 294922)
    Time Spent: 2h 50m  (was: 2h 40m)

> 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: 2h 50m
>  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)

Reply via email to