ASF GitHub Bot logged work on ARTEMIS-2451:

                Author: ASF GitHub Bot
            Created on: 15/Aug/19 15:30
            Start Date: 15/Aug/19 15:30
    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-521683921
   It's *possible* that `tempQueues` could grow like `knownDestinations`. 
However, entries are only added to `tempQueues` for temporary destinations that 
the client actually creates and entries from `tempQueues` get removed when the 
corresponding temporary destination is deleted from the broker. An entry is 
added to `knownDestinations` for every unique destination to which a client 
sends a message and those entries *never* get removed unless they are temporary 
destinations which the client itself deletes. In my mind these facts make the 
pathological growth much less likely.
   Also, in JMS terms the lifetime of a temporary destination is actually the 
lifetime of the *connection* that created it, not the session. The temporary 
destinations need to be tracked somehow so that the client implementation can 
delete them implicitly when the connection is closed in the case that the 
application doesn't delete them explicitly.
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: 295497)
    Time Spent: 5h 10m  (was: 5h)

> 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 10m
>  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