Discussion  - 
What could happen if consuming a JMS message requires 30 second of hard work on databases e application logic, and I send 100 messages? JMS would
consume these 100 messages in 100 threads, and the result could be that the server is no more responging to new HTTP requests (if you have
webservices and web application to serve).

Is it possible to limit consumer concurrency just by administration console, or do I need to implement some lock mechanisms on the MessageBean?
Barry van Someren's profile photoAdrian Meredith's profile photoAlberto Gori's profile photo
As mentioned above gf uses a thread pool and the default size is 16 i believe,all configurable in admin console
Thanks to all. I was successfull on limiting the concurrency of a specific consumer (MDB) setting the property "Maximum Active Consumers" in JMS Physical Destination page.
Add a comment...