Managing workload for JMS through configuration
A Java appserver's ability to handle multiple threads of work allows an application to perform well when the workload requires dealing with simultaneous requests. In a Web application, simultaneous user requests will be serviced by Web container threads. If the Web application makes use of JMS, then the JMS components will also be required to handle simultaneous requests.
For applications which have MDBs, the workload also arrives via the messaging system. In this situation it might also be optimal to have messages processed in parallel.
All the workload that is arriving to do with JMS, either from MDBs or from other requests, needs to be efficiently handled within the bounds of the physical resources available to the appserver and the underlying messaging system (and also any back end applications accessed through messaging).
There are settings within each of the JMS components that allow controls to be placed on that workload to create a balance that provides the best throughput and response times for the physical hardware the application is running on.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.