Message listener service thread pool

 

Each listener port defined on an appserver's message listener service will have a maximum number of sessions that it can process at the same time. Each session requires one message listener thread to be able to operate. The listener service thread pool must have enough threads available at any one time to allow all the listener ports sessions defined under it to start. This means that if there are four listener ports defined, and between them the maximum sessions settings add up to 20, then the maximum size for the thread pool should be no less than 20.

Component:	Message Listener
Applies to specific messaging topologies:	No - as long as using MDBs
Requires specific usage of JMS in application:	No
Location of setting:	Servers | Application Servers | <MyAppServer> | Message Listener Service | Thread Pool

The minimum size and thread inactivity time-out should be used together to balance how much JVM resource and heap is taken up by the inactive threads versus the performance impact of having to start up new threads. Depending on your priorities this could mean setting the minimum size to the same as the maximum size to remove the overhead of creating threads. It could mean setting it to 1 and using a large inactivity time-out so that thread pool does not use system resources until threads are needed, but during a busy time the overhead of the threads being created only impacts the first messages to arrive.

 Prev | Next

 

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.