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 clarify JmsTemplate warning

This commit is contained in:
Justin Bertram 2022-07-16 14:52:27 -05:00
parent 0f5bd28e23
commit a0fb174c8f
No known key found for this signature in database
GPG Key ID: F41830B875BB8633
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -217,13 +217,13 @@ from other providers (e.g. IBM or JRockit)
> **Note:** > **Note:**
> >
> Some popular libraries such as the Spring JMS Template are known to use > Spring's `JmsTemplate` is known to use this anti-pattern. It can only
> these anti-patterns. If you're using Spring JMS Template and you're getting > safely be used with a connection pool (e.g. in a Java EE application server
> poor performance you know why. Don't blame Apache ActiveMQ Artemis! The > using JCA), and even then it should only be used for sending messages. It
> Spring JMS Template can only safely be used in an app server which caches > cannot be safely be used for synchronously consuming messages, even with
> JMS sessions (e.g. using JCA), and only then for sending messages. It > a connection pool. If you need a connection pool take a look at
> cannot be safely be used for synchronously consuming messages, even in an > [this](https://github.com/messaginghub/pooled-jms) which was forked from the
> app server. > ActiveMQ code-base into its own project with full support for JMS 2.
- Avoid fat messages. Verbose formats such as XML take up a lot of space on the - Avoid fat messages. Verbose formats such as XML take up a lot of space on the
wire and performance will suffer as result. Avoid XML in message bodies if wire and performance will suffer as result. Avoid XML in message bodies if