- SDL Web administrator sees issues which indicates the default core service timeouts need to be extended, such as below error message in the Windows Event Viewer of CM (Content Management) server.
The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'- Timeouts seen when bulk publishing. - Timeouts seen when importing large files or complex transactions via Content Porter. |
Typically the default timeout settings are adequate and it is not necessary to extend timeouts. However it is sometimes necessary to extend the core service timeouts, such as when: - there is an inordinate amount of data with unpurged versions, completed workflow activities, or a high volume of item associations https://gateway.sdl.com/CommunitySearchResults#q=purge&d=sdlWeb - When database maintenance (index rebuilding, update statistics) is not regularly done https://gateway.sdl.com/CommunitySearchResults#q=statistics&d=SDLTridionSites There is no disadvantage to proactively extending the core service timeouts to mitigate application issues. Take a backup of the original file(s) first as a precaution as the setting change could be easily not entered correctly or the .config is made mal-formed for some reason. Screenshots are from an Web 8.5/Windows Server 2012 R2 environment **before** the modifications are made.
|
Addendum - SDL Support does not have specific values which we recommend when extending timeouts, this will be implementation specific and administrators should test to determine a reasonable value for environments. - It is usually necessary to extend core service timeouts when moving large files via Content Porter, as discussed in KB article Content Porter import of large packages fails with the error "An error (The request was aborted: The request was canceled.) occurred while transmitting data over the HTTP channel." - Also see KB article SDL Web 8.5 Content Porter takes a long time to export even individual items using an Oracle database - Also see KB article Cannot upload large binary files into a MultiMedia component: "The request channel timed out attempting to send after 00:01:00" Previous version of this document attached for reference. **Note that copy/pasting from the PDF may result in the incorrect left quotation mark/right quotation marks being pasted in (U201C, U201D). The correct quotation marks which should be used are 0022.** |