11:53:21 AM
3K50PHFRQ
It looks like you have a bunch of timeouts of requests happening...
Lots of timeouts can result in issues with the COM server availability in the thread pool in certain timing scenarios. When a Web Connection request times out, it will attempt to unload the COM server (which usually doesn't work because it's busy or hung) and if that doesn't work, it will kill the process. There's a tiny lag in the unload process that can cause problems when the next request gets this instance of a killed server which can cause the marshalling issue you're seeing. It's rare though - it's a micro timing issue.
The real problem however are the timeouts of the requests - the more failures you have due to timeouts or VFP crashes the more likely a thread pool 'miss' becomes, so addressing any requests that fail is very important.
Another option since you're running on IIS is to use the Web Connection .NET Handler which has a cleaner thread pool manager and overall is a little more efficient. It's a drop in replacement for the ISAPI dll...
+++ Rick ---
This is a WC 5.51 server, with COM, on IIS7, 64 bit, OS is W2008.
From time to time I'm getting this:
An error occurred during COM object invokation.
WC server instance not found (CoMarshalInterThreadInterfaceInStream). Err code = 800401fb: object is not registered.
Here's the relevant part of the wcerrors.txt:
2012.07.26 15:03:39:803 - 2460_E4C487873312 - Com Instance Retrieved. - /myapp/welcome.ids? - 1413 - 2460 - Com: 0-4216-3468
2012.07.26 15:03:40:812 - 2460_E4C487873312 - 2460_E4C487873312 - Request Completed (1014) - /myapp/welcome.ids? - 0 - 2460 - Com: 0-4216-3468
2012.07.26 15:14:28:437 - 2460_9EAD1568459E - 2460_9EAD1568459E - Request Started - /myapp/Welcome.ids? - 0 - 2460 - Com: -1-0-0
2012.07.26 15:14:28:444 - 2460_9EAD1568459E - Com Instance Retrieved. - /myapp/Welcome.ids? - 1413 - 2460 - Com: 1-7424-3468
2012.07.26 15:14:29:453 - Forced Release of Server - 0 - 2460
2012.07.26 15:14:30:242 - 2460_9EAD1568459E - Web Connection Request timed out. - /myapp/Welcome.ids? - 1008 - 2460 - Com: 1-7424-3468
2012.07.26 15:14:30:452 - 2460_9EAD1568459E - 2460_9EAD1568459E - Request Completed (2028) - /myapp/Welcome.ids? - 183 - 2460 - Com: 1-7424-3468
2012.07.26 15:15:50:910 - 2460_B69E96D26A52 - 2460_B69E96D26A52 - Request Started - /myapp/Welcome.ids? - 0 - 2460 - Com: -1-0-0
2012.07.26 15:15:50:917 - 2460_B69E96D26A52 - Com Instance Retrieved. - /myapp/Welcome.ids? - 1413 - 2460 - Com: 2-2120-3468
2012.07.26 15:15:51:925 - Forced Release of Server - 0 - 2460
2012.07.26 15:15:52:704 - 2460_B69E96D26A52 - Web Connection Request timed out. - /myapp/Welcome.ids? - 1008 - 2460 - Com: 2-2120-3468
2012.07.26 15:15:52:712 - 2460_B69E96D26A52 - 2460_B69E96D26A52 - Request Completed (1794) - /myapp/Welcome.ids? - 183 - 2460 - Com: 2-2120-3468
2012.07.26 15:17:22:439 - 2460_BD3855F91CED - 2460_BD3855F91CED - Request Started - /myapp/Welcome.ids? - 0 - 2460 - Com: -1-0-0
2012.07.26 15:17:22:451 - 2460_BD3855F91CED - Com Instance Retrieved. - /myapp/Welcome.ids? - 1413 - 2460 - Com: 0-4216-3468
2012.07.26 15:17:23:458 - Forced Release of Server - 0 - 2460
2012.07.26 15:17:24:245 - 2460_BD3855F91CED - Web Connection Request timed out. - /myapp/Welcome.ids? - 1008 - 2460 - Com: 0-4216-3468
2012.07.26 15:17:24:252 - 2460_BD3855F91CED - 2460_BD3855F91CED - Request Completed (1809) - /myapp/Welcome.ids? - 183 - 2460 - Com: 0-4216-3468
2012.07.26 15:18:03:738 - 2460_DC2D9DA05524 - 2460_DC2D9DA05524 - Request Started - /myapp/Welcome.ids? - 0 - 2460 - Com: -1-0-0
2012.07.26 15:18:03:746 - 2460_DC2D9DA05524 - Com Instance Retrieved. - /myapp/Welcome.ids? - 1413 - 2460 - Com: 1-1044-2460
2012.07.26 15:18:04:621 - 2460_DC2D9DA05524 - 2460_DC2D9DA05524 - Request Completed (889) - /myapp/Welcome.ids? - 0 - 2460 - Com: 1-1044-2460
2012.07.26 15:18:22:000 - 3468_321584408D91 - 3468_321584408D91 - Request Started - /myapp/login.ids? - 0 - 3468 - Com: -1-0-0
The server with PID 2460 was forced to release three times, but it didn't, and its serving of the welcome page timed out, with the strange message above. Just a minute later, the same instance serves that same page without any problem. And that being the welcome page, it is the same for all, nothing user specific (so it can't be pulling different sets of data).
Looking at the log, I've seen this (three attempts to unload a server, timing out, then working properly a minute later) a few times in the log, but since this is a new site and the log is only a couple of days old, can't be sure it's a regular occurrence.
For the time being, I've set the app pool to recycle every 45 minutes, see if that helps.
BTW, the VFP runtimes there are 9.0 (no SP) while the app is compiled under SP2. I know that may lead to some errors, but don't see how would those happen only sometimes - it's always the welcome page that has the problem (but got that on admin/display log as well)... and then later it works.
West Wind Technologies
Making waves on the Web
from Hood River, Oregon
