Managing High Concurrent Connections from a single Service Account

Overview
In some environments, a single application or service account can open a large number of concurrent connections to the server, sometimes exceeding one hundred connections at a time. This article explains expected behavior, configuration options, and recommended troubleshooting steps when such connections appear not to close as expected.

Symptoms
You may observe one or more of the following:

• A single account showing 100+ concurrent connections.
• Hundreds of total connections distributed across multiple nodes in the cluster.
• Monitoring alerts for high connection counts, even when CPU and memory utilization remain normal.

Possible causes
High concurrent connections for a single account are usually related to how the calling application manages its connections. Common patterns include:

• The application opens many parallel sessions (for example, scheduled jobs or background tasks) using the same account.
• The application does not properly close connections, leaving them open longer than intended.
• Recent configuration changes on the application side (new jobs, changed schedules, or new integrations) increase the volume of concurrent connections.

Can the server force-close active connections?
It is not possible to explicitly close active, in-use connections for a specific account using a parameter or the administrative user interface. The platform can only automatically close idle connections based on connection pooling configuration.

Idle Timeout and connection pooling
Idle connections are controlled by the Idle Timeout setting in the connection pool configuration.

• The default Idle Timeout is 5 minutes, which is the maximum time an idle connection is kept in the pool before being closed.
• This setting can typically be adjusted in the main control panel under Settings → Server Backend → Connection Pooling.

Adjusting Idle Timeout helps ensure idle connections are cleaned up, but it does not terminate active connections that are still in use by the application.

Recommended actions
To address or prevent high concurrent connections from a single account:

• Review recent changes in the calling application (for example, new or modified jobs, workflows, or integrations) that could increase connection usage.
• Work with the application or integration team to:
  • Ensure connections are properly closed when no longer needed.
  • Implement efficient connection pooling and reuse on the application side.
• Monitor per-node and overall connection counts to confirm that changes on the application side reduce and stabilize connection usage.

If connection counts remain unexpectedly high after these checks and adjustments, gather connection data (for example, current connections export and relevant logs) and contact support for further analysis.