How to calculate number of connections TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ needs

How to calculate number of connections TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ needs

book

Article ID: KB0081846

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for IBM MQ 7.6.0

Description

An MQ plug-in application may throw the MQRC_MAX_CONNS_LIMIT_REACHED error when the number of pooling max connection is not big enough. Follow the resolution below to calculate the number of connections an MQ plug-in application needs. The max connections should be set larger than it. This should address the issue due to the MQ plug-in client set. Note that the settings in MQ server can also cause this error. Refer to article 000030416 for details.

Issue/Introduction

How to calculate the number of connections TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ needs.

Resolution

You can calculate the connections your MQ plug-in application needs as follows.

For example, your project has a process that has MQ activities (listener, put, get). First you will need to know how many MQ activities in this process. For example, if you have a listener, a put, and a get, this process will need 3 connections for one job instance. If the MQ listener is a starter activity and has 5 instances configured, then you could have 5 instances running in parallel and you will need 3 * 5 =  15 connections. The connections needed for one BW application of this project is 15. If you deploy your application to 2 instances then the total connections will be 15* 2 = 30. This is the way to figure out how many connections your application needs. Note that if you have more than one process you will need to sum up the connections of all the processes. 
 
Once you know the connections your application needs, then you can set the Max connections in the connection resource and Max instances per client in the server connection channel larger than the connections your application needs. The Max instance on the connection channel is a sum of all the clients as you may have other applications other than TIBCO using the channel.