AnsweredAssumed Answered

Custom XML Web Publishing Engine needs a longer timeout

Question asked by jbarnum on Jun 4, 2015
Latest reply on Jul 5, 2017 by steve.winter

Summary

Custom XML Web Publishing Engine needs a longer timeout

Product

FileMaker Server

Version

14.2

Operating system version

Mac OS X 10.10.3

Description of the issue

XML Web Publishing Engine requests fail if it takes more than 60 seconds to return a result.

This is a big problem when reading or writing large batches of records, or when calling scripts that take a long time to run.

Steps to reproduce the problem

On a hosted file, create a new script called 'wait'. It should contain a single script step: Pause 70 seconds.

From an OS X client machine, use curl to trigger an HTTP request to run this script and find any record, like this:

curl -I -u username:password "http://serverAddress/fmi/xml/FMPXMLRESULT.xml?-db=TestDatabase&-lay=TestLayout&-script=wait&-findany"

Expected result

I would expect that after 70 seconds, I would get an XML result for a random record from TestLayout.

Actual result

After exactly 60 seconds, a 502 (bad gateway) error results.

Exact text of any error message(s) that appear

HTTP/1.1 502 Bad Gateway
Date: Fri, 05 Jun 2015 01:23:19 GMT
Server: Apache/2.4.9 (Unix) OpenSSL/0.9.8za
Vary: accept-language,accept-charset
Content-Length: 401
Content-Type: text/html; charset=utf-8
Content-Language: en

Workaround

Edit the file at /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_proxy.conf

Change this line:
ProxyPass /fmi/ http://127.0.0.1:16021/fmi/

to this:
ProxyPass /fmi/ http://127.0.0.1:16021/fmi/ timeout=600

Stop and start Apache by using fmsadmin.

A similar problem exists on Windows servers, but I have not come up with a workaround yet.

Outcomes