JMS Sender Session Pooling
When working in the non-transacted mode, you can create a pool of JMS sender sessions for each JMS channel in the project.
Each thread, that executes any of the JMS sending functions (such as, sendEvent, replyEvent, routeTo, and so on), takes a session from the pool. After utilizing the session and on completion of the send task, the thread returns the session to the pool. If max pool size is reached, threads wait for a session to become available and till then, do not create any new session.
By default, the pool is disabled and the sending functions share a single session per channel. To activate the pool set the value of the
be.channel.jms.sender.session.pool.maxsize
property, which identifies the maximum pool size, with minimum allowed value as
1.