All our workflows and the print tool stop working suddenly,
All our workflows and the print tool stop working suddenly, 
From time to time, we get errors in all the workflow tools and the print tool in all our sites (Attached an example), and we figure out that if we restart the World Wide Web Publishing Service (wwps) (attached), the issue disappears and all the workflows return to work normally.
then why all this story is happening from time to time? why the solution is in restarting the wwps? What is the major effect of this issue? Any suggestion may help.
Thank you in advance.
Best,
Majdoleen
0
-
Many thanks guys for the input.
I need to refer to the statement “I would look at migrating as many as possible to Workflow 5 which is unaffected by this handler bug”. But how about the built-in tools (like print) that have this problem?0 -
Hi Jamal,
You are correct, both printing and Workflow 4 workflows cause the issue. Removing the old workflows would likely be enough to avoid the issue. More relief will be coming with Printing and Reporting 5, which will be released very soon.
Regards,
Wayne Richard
Latitude Geographics Group Ltd.
Head Office: 300 – 1117 Wharf Street Victoria, BC Canada V8W 1T7
Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com
Developers of Geocortex web-based mapping software | www.geocortex.com
An Esri Platinum Business Partner0 -
So, LatGeo can probably explain this better, but there is a bug in IIS when using .NET. Essentially, there is a finite number of memory handlers within the App Pool. These are allocated by Workflow 4 each time a workflow is executed. This is why this issue is seen on sites that use lots of Workflows.
Windows being Windows is not the greatest at letting the App Pool know that the Workflow is complete and to release the handler. Recycling the App Pool, resets all the handlers so they are available again. Printing and exporting also utilize the App Pool, when you recycle the App Pool, you are effectively doing a hard reset. If one of those processes are running, they are killed during the recycle event.
The reason that Workflow 5 resolves this is that it executes the workflows client-side in JavaScript, whereas, Workflow 4 is a server-side technology executing .NET/WPF code.
Hopefully that explains it a little better.0 -
Great explanation Tom, thanks for providing that. The only other thing I would add is that recycling the App Pools is not the only solution, Amanda details an additional step in her January 3, 2018 post above. There is a setting to force clean up.
Regards,
Wayne Richard
Latitude Geographics Group Ltd.
Head Office: 300 – 1117 Wharf Street Victoria, BC Canada V8W 1T7
Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com
Developers of Geocortex web-based mapping software | www.geocortex.com
An Esri Platinum Business Partner0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
34 kommentarer