Connection reset

Error Description

Multiple instances of "SocketException: Connection reset" are appearing in the logs related to API calls, particularly when attempting to connect to ".betradar.com." "Related to API call" signifies that the first line above the stack trace, which corresponds to the associated exception, indicates a failed call to ".betradar.com."

What It Means

The "Connection reset" message indicates that the socket connection being utilized was forcibly closed, either by the remote server or by an intermediary device in the network path. This can occur due to various reasons, including:

• The remote server crashing or restarting, leading to the termination of existing connections.

• A network device (e.g., router or firewall) between the client and server terminating the connection due to a timeout or configuration rule.

• Limitations on the number of concurrent connections at the remote server, resulting in the forced closure of connections.

Applies to

All integrations using Unified Odds Feed (including SDKs and direct integrations)

Symptoms

A relatively high volume of requests to the Sports API is resulting in "SocketException: Connection reset", with customer concerns arising when this occurrence rate reaches 0.1% to 0.5% of requests over several hours.

When It Happens

This exception can arise at different stages of network communication, such as during connection establishment, data transmission, or idle connection maintenance, depending on the underlying cause of the "connection reset."

In any scenario, it is essential to handle SocketException and implement robust error recovery mechanisms to ensure reliability and performance, particularly in distributed environments susceptible to network-related issues.

Resolution

When investigating network-related issues, the recommended approach involves inspecting each router along the path from the client to the server to identify and resolve potential connectivity or configuration issues.