Chapter 37. Avoiding Anti-Patterns

  • Reuse connections, sessions, consumers, and producers where possible.

    The most common messaging anti-pattern is the creation of a new connection, session, and producer for every message sent or consumed. These objects take time to create and may involve several network round trips, so it is a poor use of resources. Always reuse them.

    Note

    Some popular libraries such as the Spring JMS Template use these anti-patterns. If you are using the Spring JMS Template, you may see poor performance. The Spring JMS Template can only safely be used in an application server which caches JMS sessions, for example, using JCA, and only then for sending messages. It cannot safely be used for synchronously consuming messages, even in an application server.

  • Avoid fat messages.

    Verbose formats such as XML take up a lot of space on the wire and performance suffers as result. Avoid XML in message bodies if you can.

  • Do not create temporary queues for each request.

    This common anti-pattern involves the temporary queue request-response pattern. With the temporary queue request-response pattern, a message is sent to a target, and a reply-to header is set with the address of a local temporary queue. When the recipient receives the message, they process it, and then send back a response to the address specified in the reply-to header. A common mistake made with this pattern is to create a new temporary queue on each message sent, which drastically reduces performance. Instead, the temporary queue should be reused for many requests.

  • Do not use message driven beans unless it is necessary.

    Using MDBs to consume messages is slower than consuming messages using a simple JMS message consumer.