The message listener service is an extension to the JMS functions of the JMS provider. It provides a listener manager that controls and monitors one or more JMS listeners, which each monitor a JMS destination on behalf of a deployed message-driven bean.
This panel displays links to the Additional Properties pages for Listener Ports, Thread Pool, and Custom Properties for the message listener service.
To view this administrative console page, click Servers-> Application Servers-> application_server-> Message Listener Service
Adjust this parameter when multiple message-driven beans are deployed in the same application server and the sum of their maximum session values exceeds the default value of 10.
The thread pool is shared out based on demand, so if the thread pool size is equal to the number of listener ports, then there is no guarantee that one thread is available for each listener port. However, a listener port should not get blocked by busy threads because scheduling should be based on FIFO requests.
| Data type | Integer |
| Units | Not applicable |
| Default | Minimum: 10, maximum 50 |
| Range | Not applicable |
| Recommended | Set the minimum thread pool size to the expected low-load total message-driven
beans sessions. Set the maximum thread pool size to the expected high-load
total message-driven beans sessions. If the total number of sessions for all listener ports exceeds this maximum thread pool size, adjust the minimum and maximum to the appropriate size for JVM resource reuse, parallel processing of messages, and speed of delivery; for example:
|
You can use the Custom properties page to define the following properties for use by the message listener service.