Message listener service

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.

Servers-> application_server-> Message Listener Service

 

Name

The name by which the message listener service is known for administrative purposes.

Data type	String
Default	MsgLService

 

Description

A description of the message listener service, for administrative purposes

Data type	String
Default	Null

 

Thread pool  

Controls the maximum number of threads the Message Listener Service is allowed to run. Select this link to display the service thread pool properties.

Adjust this parameter when multiple message-driven beans are deployed in the same appserver and the sum of their maximum session values exceeds the default value of 10.

Data type	Integer
Units	Not applicable
Default	Minimum: 10, maximum 50
Range	Not applicable
Recommended	Set the minimum to the sum of all message-driven beans maximum session values. Set the maximum to anything equal or greater than the minimum.

 

Custom Properties

Custom properties of the message listener service.The JMS server has two modes of operation, Application Server Facilities (ASF) and non-Application Server Facilities. ASF is meant to provide concurrency and transactional support for applications. Non-ASF bypasses that support to streamline the path length.

Use Non-ASF if:

• Message order is a strict requirement

• Concurrent PTP messages are desired

• The property non.asf.receive.timeout exists and has a value greater than 0

Do not use Non-ASF if concurrent publications and subscriptions messages are desired because ASF provides better throughput.

Data type	Integer
Units	Milliseconds
Default	ASF mode (custom property not created)
Range
Recommended	The value is the number of milliseconds it takes for a message to be delivered. If a timeout occurs, it must recycle causing extra work. This should be set to lower than the transaction timeout, but close to it with several (10 or more) seconds to spare. The seconds to spare should be more if under extreme loads in which threads are waiting long periods of time to get CPU cycles.

---

Configure the message listener service
Message listener port collection
Tuning parameter index

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.