Watchdoc - soap_request.xml becomes huge

Wed, 09 Sep 2015 10:53:06 +0000

Hello,

Be aware that the WatchDoc can crash any server if a file that needs to be uploaded to Efficy is bigger than the IIS "Maximum allowed content length" (default : 28.61 Mb).

Here is the problem :

1/ When a scan/Fax is made, it goes to a specific folder
2/ The watchdoc service is watching this folder, and every time a document comes in, it upload it to Efficy (using SOAP) and then move this document to an ‘uploaded’ folder.
3/ By default, IIS is configured to accept request with a maximum of 30000000 bytes (= 28.61 Megabytes).
4/ If the document is heavier than 28.61 Megabytes, the Watchdoc fail to upload it to Efficy, and log the request (which contain the document that has been base64 encoded) in soap_request.xml.
5/ This file is growing every time the WatchDoc is launched, and for one customer it has reached 130GB !

The solution is very simple : increase the “Maximum allowed content length” in IIS. To do so :

1/ Open IIS
2/ Click on the website that is running Efficy
3/ Click on the icon “Request Filtering”
4/ On the right panel, click on “Edit Feature Settings…”
5/ Increase the “Maximum allowed content length” value (for instance, setting it to 209715200 will allow files up to 200mo to be uploaded).

Geoffrey

Efficy Overflow Q&A - Recent questions tagged watchdoc

Watchdoc - soap_request.xml becomes huge