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 Java EE specification, do not support JTA user transactions, and are largely superseded by message-driven beans (MDBs), which are a required part of the Java EE specification.
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.
For more information about these session pool attributes, see Configuration Options.
For more information about these session pool attributes, see Configuration Options.