[
https://issues.apache.org/jira/browse/ARTEMIS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023439#comment-16023439
]
ASF GitHub Bot commented on ARTEMIS-1179:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/1288
oh yeay sevntu not available again....
[ERROR] Unresolveable build extension: Plugin
org.apache.felix:maven-bundle-plugin:3.3.0 or one of its dependencies could not
be resolved: Could not find artifact
org.apache.felix:maven-bundle-plugin:jar:3.3.0 in sevntu-maven
(http://sevntu-checkstyle.github.io/sevntu.checkstyle/maven2) @
On a serious note, it seem this tool in the repo, isn't reliable, this
isn't the first time I've seen this issue or others have. How much real value
is it adding?
> 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)
