Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

NO-JIRA fix JMS destination cache doc

This commit is contained in:
Justin Bertram 2018-06-12 10:34:31 -05:00
parent 83d363de62
commit ed095a0523
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/user-manual/en/perf-tuning.md
View File

@ -139,7 +139,7 @@ some tuning:
then you can avoid some unnecessary copying.
- If using frameworks like Spring, configure destinations permanently broker
side and enable `destinationCache` on the client side. See the [Setting The
side and enable `cacheDestinations` on the client side. See the [Setting The
Destination Cache](using-jms.md) for more information on this.
## Tuning Transport Settings

2
docs/user-manual/en/using-jms.md
View File

@ -393,7 +393,7 @@ valuable bandwidth. This can be configured on the connection factory via the
Many frameworks such as Spring resolve the destination by name on every
operation, this can cause a performance issue and extra calls to the broker, in
a scenario where destinations (addresses) are permanent broker side, such as
they are managed by a platform or operations team. using `destinationCache`
they are managed by a platform or operations team. using `cacheDestinations`
element, you can toggle on the destination cache to improve the performance and
reduce the calls to the broker. This should not be used if destinations
(addresses) are not permanent broker side, as in dynamic creation/deletion.