A JMS session pool enables
an application to process messages concurrently. Once you have defined a
JMS server, optionally, you can configure one or more session pools for
each JMS server:
Note: Session pools are now used rarely, as they are not a
required part of the J2EE specification, do not support JTA user
transactions, and are largely superseded by message-driven beans (MDBs),
which are a required part of the J2EE specification.
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
Administration Console, expand Services > Messaging
and select JMS Servers.
On the Summary of JMS Servers page, click
the JMS server you want to configure with a session pool.
Session Pools tab.
JMS Session Pools page, click
Note: Once you create a JMS session pool, you cannot
rename it. Instead, you must delete it and create another one that
uses the new name.
Create a New JMS Session Pool page, define the
general session pool options:
In Name, enter a name for the JMS
In Listener Class, enter the listener
class that will be used by the JMS session pool, which is used to
receive and process messages concurrently.