[
https://issues.apache.org/jira/browse/ARTEMIS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023491#comment-16023491
]
ASF GitHub Bot commented on ARTEMIS-1179:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1288
see it now you point it out, annoying as build shows end output as success
when watching console
https://builds.apache.org/job/ActiveMQ-Artemis-PR-Build/3081/console
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 14:13 min
[INFO] Finished at: 2017-05-24T19:11:19+00:00
[INFO] Final Memory: 433M/6315M
[INFO]
------------------------------------------------------------------------
> 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)
