CODEWITHSUNDEEP
performancequeuejmsconsumer
wqt
wqt

Reputation: 1

JMS queue consumer: synchronous receive() or single-threaded onMessage()

I need to consume from a Q, and stamp a sequence key on each message to indicate the ordering. i.e. the consumption needs to be sequential. From performance/throughput point of view, would I be better off using a blocking receive() method, or an async listener with a single-threaded configuration on the onMessage() method?

Thanks.

Upvotes: 0

Views: 699

Answers (1)

Calanais
Calanais

Reputation: 1580

There are many aspects that will affect the performance and throughput; in pure JMS terms it's not really possible to state that the sync or async model of getting messages will be any less or more efficient. It will depend on a large number of factors from how the application is written, other resources it's using, implementation of your chosen messaging provider and other factors such as machine performance and configuration of both client and server machines.

This discussion, Single vs Multi-threaded JMS Producer, covered some of these topics.

To the sequence, if you are single threaded, with a single session the JMS specification gives some assurances on message ordering; best to review the spec to see if it matches your overall requirements.

Often people will insert an application sequence number at message production time; the consumer can therefore check they are getting the correct message in order. Adding a sequence number at consumption time won't specifically help that consumer.

Keep in mind that the stricter the requirement for messaging ordering the more restrictive the overall architecture gets and the harder it is to implement horizontal scalabilty.

Upvotes: 1

Related Questions