Loading

TLS Session Resumption Can Cause Intermittent Connection Failure

Fecha de publicación: Jun 16, 2026
Descripción

Intermittent connectivity issue between client and MuleSoft DLB. The client received an error indicating the requests were reset by DLB during TLS handshake.

This is caused when the client tries to resume a TLS session to DLB worker A, but is making the connection against DLB worker B. The DLB will reject this connection.

Solución

1. Run a packet capture (on client and DLB) while reproducing the issue.

2. Examine the Client Hello packet to check if TLS session cache is used. In TLSv1.2, this will be visible in the Session ID field. In TLSv1.3, this will be visible in the PSK extension.

3. If TLS session caching is used on the client side, check if the client has persistence configured. If the client tries to resume a cached TLS session, but sends this request to the "other" DLB worker node (because there is no persistence configured), the connection will be rejected by DLB.

4. To resolve, disable TLS session caching at the client side, or enable persistence.

Número del artículo de conocimiento

005387162

 
Cargando
Salesforce Help | Article