RabbitMQ JMS Client Performance Tuning

Jerry Yu

unread,

Sep 9, 2019, 3:09:45 PM9/9/19

to rabbitmq-users

Hello,

Wondering if anybody here can kindly advice on how to tune the performance of RabbitMQ JMS Client (rabbitmq-jms-client). We have an application using ActiveMQ currently, with Spring Integration (<int-jms:outbound-channel-adapter> and DefaultMessageListenerContainer), but would like to switch to RabbitMQ. We did some performance tests, and found out that the producer throughput of RabbitMQ is much lower than that of ActiveMQ. This is the connection factory code:

private ConnectionFactory connectionFactory() throws Exception {

int channelsQos = 100;

RMQConnectionFactory factory = new RMQConnectionFactory();

factory.setHost(host);

factory.setVirtualHost(vhost);

factory.setPort(port);

factory.setUsername(user);

factory.setPassword(pass);

factory.setChannelsQos(channelsQos);

return new SingleConnectionFactory(factory);

}

Any suggests/comment would be appreciated!

Jerry

Wesley Peng

unread,

Sep 9, 2019, 11:52:27 PM9/9/19

to rabbitm...@googlegroups.com

Hi

on 2019/9/10 3:09, Jerry Yu wrote:
> Wondering if anybody here can kindly advice on how to tune the
> performance of RabbitMQ JMS Client (rabbitmq-jms-client). We have an
> application using ActiveMQ currently, with Spring Integration
> (<int-jms:outbound-channel-adapter> and
> DefaultMessageListenerContainer), but would like to switch to RabbitMQ.
> We did some performance tests, and found out that the producer
> throughput of RabbitMQ is much lower than that of ActiveMQ. This is the
> connection factory code:

You can setup queue content to memory only, and don't use an
username/password for authentication. Also rabbitmq cluster would have
the ability to improve the throughput.

regards.

Arnaud Cogoluègnes

unread,

Sep 10, 2019, 5:40:35 AM9/10/19

to rabbitm...@googlegroups.com

More information about your benchmark would be helpful. Ideally a
project with broker settings and steps to run would help us to help
you.

On another note, I'd advice to get rid of JMS altogether in this case
and use Spring Integration AMQP adapters. One of Spring Integration's
goals is to isolate application code from infrastructure like JMS or
AMQP, so switching from JMS to AMQP should have minimal impact on your
application code and would allow for fairer comparison between those
technologies.

> --
> You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/df6a858e-a903-4397-a9a4-3c1e67a8d8a1%40googlegroups.com.

Jerry Yu

unread,

Sep 10, 2019, 9:46:58 AM9/10/19

to rabbitmq-users

Thanks Wesley! Authentication is required for the application. The ActiveMQ server that we compared for our tests is also having the authentication.

The RMQ is also already on a cluster.

Jerry Yu

unread,

Sep 10, 2019, 4:24:34 PM9/10/19

to rabbitm...@googlegroups.com

Thanks Arnaud! I may try the Spring Integration's AMQP Adapter later. But right now, it's not the goal for me to replace JMS in the application. Followings are some details I found which may have caused the performance issue.

For example, when I sent 2 messages all together to a queue via Spring Integration <int-jms:outbound-channel-adapter>. With logging enabled, I can see that followings happened for EACH message to be sent.

Create Producer,

Declare queue destination and exchange,

exchange and queue binding,

close producer,

close session.

I am wondering how to set spring integration to share the producer without closing the producer and session when sending each messages. Would like the messages to be send in batch.

Log snippet for message 1:

[com.rabbitmq.jms.client.RMQSession] [#631] create producer for destination 'RMQDestination{destinationName

[com.rabbitmq.jms.client.RMQSession] [#829] declare RabbitMQ queue for destination 'RMQDestination{destinationName

[com.rabbitmq.jms.client.RMQSession] [#857] declare RabbitMQ exchange for queue destinations 'RMQDestination{destinationName

[com.rabbitmq.jms.client.RMQSession] [#876] declare RabbitMQ queue name, durable(true), exclusive(false), auto-delete(false), properties(null)

[com.rabbitmq.jms.client.RMQSession] [#893] bind queue name to exchange(jms.durable.queues)

[com.rabbitmq.jms.client.RMQMessageProducer] [#263] send/publish message(com.rabbitmq.jms.client.message.RMQObjectMessage@1f) to destination(RMQDestination deliveryMode(2), priority(4), timeToLive(0)

[com.rabbitmq.jms.client.RMQMessageProducer] [#212] close producer for destination 'RMQDestination{destinationName

[com.rabbitmq.jms.client.RMQConnection] [#480] internal:sessionClose(com.rabbitmq.jms.client.RMQSession)

[com.rabbitmq.jms.client.RMQSession] [#497] close session com.rabbitmq.jms.client.RMQSession

Got same log snippet for message 2:

Log snippet for message 1