Very slow performance when connecting to a broker that is configured for nio+ssl:// transport

Solution In Progress - Updated -

Environment

  • JBoss Fuse 6.1

Issue

The ActiveMQ broker is configured to use the nio+ssl: transport as in this example:

<transportConnector name="openwire" uri="nio+ssl://0.0.0.0:61617?"/>

A very slow performance for both producer and consumer is observed when dealing with slightly larger messages (in the range < 2MB). It takes more than 20x longer to send messages over this transport compared to using plain nio:// or plain ssl:// transport.

Resolution

Because of bug AMQ-5144 don't use the combination of nio+ssl on the broker's transport connector.
This bug is fixed in JBoss Fuse 6.2 and Apache ActiveMQ 5.10.

Root Cause

This slow performance is caused by bug AMQ-5144 and only happens when combining the transports NIO and SSL on the broker.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.