AQ JMS scales poorly when there are many threads waiting for messages on the same queue. When a message arrives all threads wake up and compete for it, consuming CPU in the database. It is much better to sleep on the client side between polling attempts when a receive returned without a message. That way it is possible to use a large number of threads/sessions without overloading the server. Other JMS providers may have the same problem.
I have signed and agree to the terms of the Spring Individual Contributor License Agreement.
Issue: SPR-14225
Comment From: pivotal-issuemaster
@erik-wramner Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-issuemaster
@erik-wramner Thank you for signing the Contributor License Agreement!