Set the message listener service

Use this task to configure the properties of the message listener service for an appserver, to support message-driven beans deployed against listener ports.

To use message-driven beans with a messaging provider that does not have a JCA 1.5 resource adapter, we cannot use activation specifications and therefore configure the beans against a listener port. There are also a few scenarios in which, although you could use activation specifications, we might still choose to use listener ports.

See about when to use listener ports rather than activation specifications, see Administer activation specifications and listener ports for message-driven beans.

The message listener service is an extension to the JMS functions of the JMS provider and provides a listener manager, which controls and monitors one or more JMS listeners. Each listener monitors either a JMS queue destination (for point-to-point messaging) or a JMS topic destination (for publish/subscribe messaging). For more information, see Message-driven beans - listener port components.

When you deploy an enterprise application to use message-driven beans with listener ports, we can browse or change the configuration of the message listener service for a given appserver.

 

1. Display the listener service settings page:

   1. In the navigation pane, select Servers > Server Types > WebSphere application servers.

   2. In the content pane, click the name of the application server.

   3. Under Communications, click Messaging > Message Listener Service.

2. Browse or change the value of properties for the message-driven bean thread pool.

   1. Click Thread Pool

   2. Change the following properties, to suit the needs:

      Minimum size

      The minimum number of threads to allow in the pool.

      Maximum size

      The maximum number of threads to allow in the pool.

      Thread inactivity timeout

      The number of milliseconds of inactivity that should elapse before a thread is reclaimed. A value of 0 indicates not to wait and a negative value (less than 0) means to wait forever.

      The admin console does not allow us to set the inactivity timeout to a negative number. To do this modify the value directly in the config.xml file.

      Allow thread allocation beyond maximum thread size

      Select this check box to enable the number of threads to increase beyond the maximum size configured for the thread pool.

   3. Click OK.

3. Specify any of the following optional properties that we need, as Custom properties of the message listener service:

   NON.ASF.RECEIVE.TIMEOUT, MQJMS.POOLING.TIMEOUT, MQJMS.POOLING.THRESHOLD, MAX.RECOVERY.RETRIES, and RECOVERY.RETRY.INTERVAL.

   See about these custom properties, see Custom Properties.

   To browse or change the properties...

   1. Click Custom properties

   2. For each custom property, specify a value to suit the needs. If we have not specified a property before:

      1. Click New.

      2. Type the name of the property.

      3. Type the value of the property.

      4. Click OK.

4. Save the changes to the master configuration.

5. To have the changed configuration take effect, stop then restart the appserver.

Message listener service

 

Related concepts

Message-driven beans - listener port components

 

Related tasks

Administer listener ports
Set message listener resources for message-driven beans