Never experienced "page pool errors" exactly as you are describing
them.
With uProduce 4.6.2. with busy ICP-based campaigns, I experienced
"deadlock detected" on \aspnet_isapi.dll.
I managed to fix them, by:
* defining a separate application pool for each virtual folder,
assigned to each campaign;
* making the following changes in the .Net Framework machine.config:
[...]
<configuration>
<system.web>
[...]
<!-- Added by Xerox Oct. 4, 2009 -->
<!-- For Performance, Stability and Availability Purpose -->
<!-- Read
http://www.guidanceshare.com/wiki/ASP.NET_2.0_Performance_Guidelines_-_Threading
-->
<httpRuntime
minFreeThreads="88"
minLocalRequestFreeThreads="76"
/>
<processModel
autoConfig="true"
maxWorkerThreads="100"
minWorkerThreads="50"
maxIoThreads="100"
/>
</system.web>
<
system.net>
<connectionManagement>
<add address="*" maxconnection="12" />
</connectionManagement>
</
system.net>
<!-- End Xerox Addon -->
[...]
HTH