Troubleshooting the Alfresco Connector

Failure to Crawl Content

If the crawl fails with the error: "A connection was forcibly closed by remote host" it means the Alfresco Content Services connection has timed out.

Tomcat server timeouts must be configured.

How to Configure Timeouts

Use the following instructions to set this configuration.

1. Navigate to <Alfresco Content Services install location>/tomcat/conf/server.xml
   
   
2. Edit the following line:
   
   <Connector port="8080" URIEncoding="UTF-8" protocol="HTTP/1.1" 
connectionTimeout="20000" 
redirectPort="8443" maxHttpHeaderSize="32768" keepAliveTimeout="20000" />
   
   
3. Set the connectionTimeout and keepAlliveTimeout properties to -1 (for no timeout) or a greater value than is set.

Web.config File

Timeouts for Rest API calls can also be extended in the file web.config, found in the SmartHub root directory.

  <appSettings>
    <add key="CallTimeoutInMinutes" value="5"/>
  </appSettings>