The api.dw.serviceTimeoutNotSet quota in B2C Commerce

Background
The api.dw.serviceTimeoutNotSet quota notifies you for any FTP, SFTP, HTTP and webservice calls that don't have a timeout configured or are set to 30 seconds or greater.

An example of what a violation of this quota looks like is below:
Quota api.dw.serviceTimeoutNotSet (not enforced, limit 0): limit exceeded

Why?
When waiting on outbound requests that never arrive, the default timeout is set to 30 seconds for calls to remote services can delay the page from loading until the underlying system gives up. However, by the time the call finally returned, it would run into the pipeline and/or script timeouts.

In addition, there are other scenarios are even worse than just tying up a single request thread. An example of is when an operation runs a database transaction with manual transaction control, the platform resources are held until the "Commit" or "Rollback" transaction completes. If such a transaction includes a remote call, the thread may end up blocking other user activities from completing e.g. login, search or checkout.

This means that having proper timeouts configured is crucial to the health of your site. Therefore when you receive a notification about this new quota, please do the following:

• Add a setTimeout() call for your specific client as outlined in the HTTPClient documentation.
• If you already use the Service framework, take a moment to configure your webservice via the Business Manager. You can (and should!) take advantage of the framework's capabilities to configure a Circuit Breaker, too.
• You may notice that SFTPClient still produces quota warnings if you set the timeout to the default of 30 seconds. This is an implementation artifact and setting your timeout to anything lower will avoid the warning.
• Detailed information about what caused the violation is available in the quota logs. Among others it contains type of request, site, pipeline name and other parameters.
• You can access the logs in Business Manager: Administration > Site Development > Development Setup > WebDAV Access section > Log files.