ZorDesign

Stopping WPE does not stop web publishing

Discussion created by ZorDesign on Feb 9, 2017
Latest reply on Feb 9, 2017 by CamelCase_data

Product and version FileMaker Server 15.0.3 (2 machine deployment)

OS and version Windows Server 2012R2

 

Description

When FileMaker WPE is stopped from the Status page of the admin console on the master machine, it shows that it is stopped but keeps responding.

This is a problem as being able to enable/disable some services without having to take the whole server down is useful during maintenance work or data updates run on server but without access for other systems accessing FileMaker through XML while maintenance work is carried out.

No errors were shown attempting to stop the server and the status page in the admin console updates to show that the service has indeed stopped. Which doesn't seem to keep it from responding.

 

How to replicate

Master machine setup like this:

 

Run a query like this:

http://172.16.0.204/fmi/xml/fmresultset.xml?-dbnames

 

for the following response (trimmed at the end):

<fmresultset xmlns="http://www.filemaker.com/xml/fmresultset" version="1.0">

 

<error code="0"/>

 

<product build="10/27/2016" name="FileMaker Web Publishing Engine" version="15.0.3.308"/>

<datasource database="DBNAMES" date-format="" layout="" table="" time-format="" timestamp-format="" total-count="5"/>

 

<metadata>

 

 

<field-definition auto-enter="no" four-digit-year="no" global="no" max-repeat="1" name="DATABASE_NAME" not-empty="yes" numeric-only="no" result="text"time-of-day="no" type="normal"/>

 

</metadata>

 

<resultset count="5" fetch-size="5">

 

 

<record mod-id="0" record-id="0">

 

 

<field name="DATABASE_NAME">

 

 

<data>DIS_Data</data>

 

</field>

</record>

 

<record mod-id="0" record-id="0">

 

 

...

 

Workaround

Stopping the IIS process on the worker machine should ensure that no web pages are published as would probably a redeployment of the server. But that shouldn't be necessary and it would be helpful to disable/enable subsets of web services (PHP, XML, WebDirect) without a "all or nothing" approach.

Outcomes