[
https://issues.apache.org/jira/browse/ARTEMIS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022467#comment-16022467
]
ASF GitHub Bot commented on ARTEMIS-1179:
-----------------------------------------
GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/activemq-artemis/pull/1287
ARTEMIS-1179: Add Optional Client JMS Destination Cache
Add topic and queue cache maps in Session.
Add configuration to use cache or not with defaulting to false, which keeps
existing behaviour as the default.
Add documentation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/michaelandrepearce/activemq-artemis
ARTEMIS-1179
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1287.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1287
----
commit 9b2a6590bcd1197ea005b7e25ef7a2ee167d97d0
Author: Michael Andre Pearce <[email protected]>
Date: 2017-05-24T07:33:19Z
ARTEMIS-1179: Add Optional Client JMS Destination Cache
Add topic and queue cache maps in Session.
Add configuration to use cache or not with defaulting to false, which keeps
existing behaviour as the default.
----
> Add Optional Client JMS Destination Cache
> -----------------------------------------
>
> Key: ARTEMIS-1179
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1179
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Michael Andre Pearce
>
> Some frameworks, constantly resolve the destination by name on every send,
> rather than caching this.
> Spring is one such very popular framework, but we have seen this
> unfortunately else where (no doubt replicating springs logic at some point of
> history)
> This causes a performance issue, and obviously extra calls to the broker as
> currently the artemis jms client calls the broker to check the address.
> In some enterprise/platform setups where destinations excluding temporary
> destinations, destinations/address's are created permanently broker side, as
> such the destination once resolved on the client can be permanently cached
> thus avoiding the above mentioned performance and extra calls to the broker.
> The default should keep the existing behaviour, but users should be able to
> opt in to this benefit.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
