Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More

MuleSoft Salesforce Connector: Unexpected processing delays caused by Connection Pool exhaustion when concurrent requests exceed Max Entries

Publish Date: Jul 7, 2026
Description

Symptom

You see following symtom with using MuleSoft Salesforce Connector:

  • Salesforce Connector operations take longer than expected to complete (several seconds to tens of seconds)
  • No errors or timeouts are thrown; processing eventually completes successfully
  • More likely to occur under high load or during parallel flow execution
  • When DEBUG logging is enabled (Ref [1]), the following messages are observed (the time gap between them corresponds to the delay):
DEBUG [...] org.mule.extension.salesforce.internal.connection.pooling.ConnectionPool: Awaiting a connection to become free.
...
DEBUG [...] org.mule.extension.salesforce.internal.connection.pooling.ConnectionPool: There is a free connection available. Arguments: {connection=com.sforce.soap.partner.PartnerConnection@...}
 

Cause

The Salesforce Connector's Connection Pool has a maximum number of simultaneous connections defined by Max Entries (default: 10). When the number of concurrent requests exceeds this limit, requests are queued until a connection becomes available, resulting in processing delays.

Resolution

Increase the "Max Entries" value in the Salesforce Config Connection Pool settings (Ref[2]) to accommodate the number of concurrent requests.

Reference

[1] How to Enable Debug Logging for Salesforce Connector in Mule 4
[2] Salesforce Connector Reference
Please see "Max Entries" in Connection types

Additional Resources

Because DEBUG logging is disabled by default in normal operations, the root cause can be difficult to identify without explicitly enabling it during investigation

Knowledge Article Number

005388602

 
Loading
Salesforce Help | Article