JMS Server: JMS Session Pools
Column Display Related Tasks Related Topics
Session pools enable an application to process messages concurrently. 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.
This page summarizes the session pools that have been created for the current JMS server.
Deprecated. 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.
You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.
The following table lists all of the data points that you can display in columns on this page.
Name Description Name
The name of this JMS session pool.
The acknowledge mode used by non-transacted sessions within this JMS session pool.
For transacted sessions, messages are acknowledged automatically when the session is committed and this value is ignored.
The name of the server-side listener class for this JMS session pool, which is used to receive and process messages concurrently.
The maximum number of sessions allowed for this JMS session pool. A value of
-1indicates that there is no maximum.
This attribute is dynamically configurable; however, it does not take effect until the session pool is restarted.
Indicates whether this JMS session pool creates transacted sessions.
The JNDI name of the connection factory for this JMS session pool. Connection factories are used to create connections with predefined attributes.