[ https://issues.apache.org/jira/browse/ARTEMIS-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Andre Pearce closed ARTEMIS-1179. ----------------------------------------- > 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 > Assignee: Michael Andre Pearce > Fix For: 2.2.0 > > > 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)