We have been using the Web Publishing Engine to serve XML responses via Apache for about a year now. It works fine except that about once a week it just stops serving. The FM Server is still happily serving data to FM clients and the web admin interface still works too (although it says that the module is not running).

The process appears to be running on the system, but parhaps just not in a happy state. Sometimes restarting the service works (although the times that it doesn't work may be a timing issue - ie not waiting long enough to see if it worked). By restarting the service, I mean issuing the following command:

sudo SystemStarter restart "FileMaker Web Publishing"

So my question is, has anyone heard of the web publishing engine being unreliable and needing a restart every week or so, and has anyone heard of a fix? As I write this I am applying the v3 and v4 patches to see if it makes any difference, but I won't know for sure until it runs for a couple of weeks without dying.

Filemaker Server Advanced 7

Happens to us all the time, a lot more than once a week.

Basically, Ive created a batch file that restarts the service, and created a scheduled task to run it every day. But we are running on a Windows Box.

Thanks for the idea, we've considered that ourselves.

But guess what, I just found the answer on the FileMaker Knowledge Base, amazing what happens when you look in the right place.

http://filemaker.custhelp.com/cgi-bin/filemaker.cfg/php/enduser/std_adp.php?p_faqid=5303

Basically Server Advanced 7 has a problem with multi-CPU systems or windows machines with hyperthreading (which is like a simulation of multiple CPUs). Fixed in version 8, ordering now...