JMS session pooling

The Sterling Order Management System Software application can be customized or extended through user exits to send messages into queues.

For example, the createOrder API can be configured to send a message to a queue that is picked up later by an email agent to notify customers that the order has been created.

For performance and scalability, the JMS sends should reuse JMS sessions across transactions. Doing so will reduce the overhead of setting up and shutting down sessions. For the Sterling Order Management System Software agents and integration servers, you should set yfs.jms.session.disable.pooling=N to enable the JMS session pooling. The Sterling Order Management System Software, however, uses the JMS session pooling provided by the application servers. As a result, you should set yfs.jms.session.disable.pooling=Y to disable the Sterling Order Management System Software JMS session pooling mechanism so that it does not conflict with the application servers’ session pools. If you are using IBM® MQ and fscontext, use connection pooling at the application server layer and set yfs.jms.session.disable.pooling=N.