Managing JMS/MQ connections in a service test
When you run a service test that includes JMS or MQ protocol, the socket connections are
created and closed in the background. When you include multiple tests in a compound test or a Schedule,
multiple connections are created and closed. Starting from 9.2, when you run service tests in a
schedule, you can select a pooling strategy for these JMS/MQ connections so that when the
connections are created, they do not close and are reused subsequently for the other JMS/MQ calls,
if required.
About this task
You can set the scope of JMS/MQ connections to a test, compound test, or schedule. When you set the scope to test, existing behavior comes into play wherein duplicate connections could be created and closed. When you set the scope to a compound test or a schedule, the connections are reused for JMS/MQ calls within a compound test or a schedule.