[
https://issues.apache.org/jira/browse/ARTEMIS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023841#comment-16023841
]
ASF subversion and git services commented on ARTEMIS-1179:
----------------------------------------------------------
Commit 373803a85d0b6da47e0dee8a4f2deb1a68caa8c8 in activemq-artemis's branch
refs/heads/master from [~michael.andre.pearce]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=373803a ]
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)
