ASF GitHub Bot logged work on ARTEMIS-2451:

                Author: ASF GitHub Bot
            Created on: 14/Aug/19 19:26
            Start Date: 14/Aug/19 19:26
    Worklog Time Spent: 10m 
      Work Description: jbertram commented on pull request #2796: ARTEMIS-2451 
remove need for knownDestination Cache
URL: https://github.com/apache/activemq-artemis/pull/2796#discussion_r314044316

 File path: 
 @@ -227,45 +228,6 @@ public void testForTempQueueCleanerUpperLeak() throws 
Exception {
-   @Test
 Review comment:
   These tests are still valid and shouldn't be removed. They are testing the 
server-side accumulation of address info. The changes in this PR are for the 
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:

Issue Time Tracking

    Worklog Id:     (was: 294959)
    Time Spent: 3h  (was: 2h 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: 3h
>  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

Reply via email to