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.

Procedure

  1. In the Test Navigator, browse to the schedule and double-click it. The schedule is displayed.
  2. Select a schedule. In the VU Schedule Details area, click the Advanced tab and under Protocol-specific options, click Edit Options.
  3. In JMS/MQ connections scope, select the scope of the connections.
  4. Use the following options to control the underlying MQ Connection Manager to create only the specified number of connections. These options are generally used by the MQ expert:
    1. In Maximum quantity of connections, specify a number to ensure that a certain number of connections are open at a time only for MQ Java.
    2. In Maximum quantity of unused connections, specify the maximum number of connections that should be unused among the open connections.
    3. In Connection timeout (ms), specify a time after which there is no attempt to establish the connection.

Results

When you run a schedule, the JMS/MQ connections are reused.
Feedback