AnsweredAssumed Answered

FMS 10 Web Publishing (fmswpc.exe) CPU Hit

Question asked by Gordie on Aug 27, 2010
Latest reply on Aug 28, 2010 by Gordie


FMS 10 Web Publishing (fmswpc.exe) CPU Hit

Your post

Hi there,

Sometimes once a week, sometimes once a day the process fmswpc.exe will spike the CPU's load to 100% and stay there indefinitely.  I have to first end the process via the task manager, then I must stop and restart Web Publishing via the Admin Console.  During the time of the spike, all database usage (e.g. PHP access or Client access) comes to a near standstill and most of my client connections lose communication with the server).  This becomes extremely problamatic if I am not monitoring the CPU load and don't catch the problem right away, or if I'm away from a computer.

The Admin Console itself does not report a problem during the spikes.

Similar to the problem, most all requests (especially  "addRecordCommand" via the API for php) will put the CPU to 100%  via  the fmswpc.exe for the duration of the call.  If it's a find  command,  this could take a number of seconds in which the rest of the  database  slows completely.  The problem with this is, if I'm monitoring the task manager's performance graph and I see the CPU load hit 100%, I have to wait to see if it's just a request ending or if it's truly the error rearing its head.

Visually, durning the error the task manager shows a perfectly flat line at the top of the graph.  When the server "normally" gets hit to 100% during a fmswpc.exe call it will be a jagged line at the top of the graph, although sometimes a "normal" 100% call produces a flat line at the top as well.  I've attached an image to show what I see.

We're running Windows Server 2003 R2 on an Intex Xeon 2.66GHz with 1.6 GB RAM.

Our server is FMS v10.0.2.206

On average we have about 50 clients using the system and one or two CWP (but we have had as many as 50).  The number of CWP connections doesn't seem to cause the CPU error, but if multiple CWP connections perform a task at the same time the 100% CPU hit does render the system very slow until their operations conclude.

Thank you for any help!