[
https://issues.apache.org/jira/browse/ARTEMIS-2451?focusedWorklogId=296973&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-296973
]
ASF GitHub Bot logged work on ARTEMIS-2451:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Aug/19 01:00
Start Date: 19/Aug/19 01:00
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on issue #2800: ARTEMIS-2451
eliminate knownDestinations cache
URL: https://github.com/apache/activemq-artemis/pull/2800#issuecomment-522376248
@jbertram Can I ask you to add a test with this PR?
One that shows users doing this anti pattern:
```java
int N = 100; // or any arbitrary number > 1
for (int i = 0; i < N; i++) {
Queue queue = session.createQueue("myQueue");
MessageProducer prod = session.createProducer(queue);
prod.send(....);
prod.close();
}
```
If an user did such anti-pattern, it should suffer the consequences of the
extra roundtrip of course, and we should not optimize for it.
I just want to make sure it wouldn't fail for any reason.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 296973)
Time Spent: 6h (was: 5h 50m)
> 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
> 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)
