Connector Pool Configuration

Introduction

App Designer pools Connector handler instances and caps the size of that pool. This page covers the setting that sets the cap and how to supply it for each deployment method. For how pooling works, see Connector Pooling.

Configuration Key

The cap is a single App Designer application setting:

Key	Default	Description
xmpro:appDesigner:connectorPool:globalCap	128	Maximum number of pooled Connector handlers retained per App Designer deployment. Must be a positive integer. Values below 1 turn pooling off, so every Connector loads cold.

The default of 128 suits most deployments. Adjust it only when there is a demonstrated need, for example if the Connector Pool Report shows the pool consistently at capacity. If your deployment appears to need a substantially higher cap, contact your XMPro representative.

Supplying the Setting

The key is the same everywhere, but how you supply it depends on how XMPro is deployed.

Kubernetes With Helm

Set the value in your values file:

ad:
  connectorPool:
    globalCap: 128

The chart renders this into the App Designer deployment as an environment variable, so no further configuration is needed.

Environment Variable

Deployments that configure App Designer directly, such as Docker, can set the equivalent environment variable:

XM__XMPRO__APPDESIGNER__CONNECTORPOOL__GLOBALCAP=128

Terraform

The XMPro Terraform modules deploy App Designer with the default cap of 128. The ad_connector_pool_global_cap variable is declared on the inner application modules, but it is not passed through the site application layer that deployments are run from, so setting it in your terraform.tfvars has no effect.

To use a different value on a Kubernetes deployment, override ad.connectorPool.globalCap in the Helm release.

---

Last modified: September 23, 2026