activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1179) Add Optional Client JMS Destination Cache
Date Wed, 24 May 2017 17:03:04 GMT


ASF GitHub Bot commented on ARTEMIS-1179:

Github user michaelandrepearce commented on the issue:
    As in we don't hold any remote resource (which typically close methods are for, so if
no longer referenced GC would clear it out

> Add Optional Client JMS Destination Cache
> -----------------------------------------
>                 Key: ARTEMIS-1179
>                 URL:
>             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

View raw message