> > Running threads, usually set at 4 per processor, queued threads, you can set > this as you please (though a lower value is safer). >
This is a reasonably old recommendation (based on the original CFMX release). As a general recommendation it's not up-to-date. > Though I don't see how it addresses the OutOfMemory exceptions - the problem > is that the server cannot create a new thread to handle a request because > there is no memory available. Address the memory leak and you will no longer > have the error. > The type of OOM Barry is talking about here is not one that sources from the heap size and therefore a direct result of memory leaks in CF code, just saying. This is rather an error that you'd be getting if your heap size is too large - as weird as it might sound. > > I don't think modifying thread limits will fix the issue. I do :) Cheers Kai -- Kai Koenig - Ventego Creative Ltd ph: +64 4 476 6781 - mob: +64 21 928 365 / +61 450 132 117 web: http://www.ventego-creative.co.nz blog: http://www.bloginblack.de twitter: http://www.twitter.com/agentK Hands-on Regular Expression training @ webDU 2010 http://bloginblack.de/agentk/workshop-befriending-regular-expressions/ Hands-on Flash Catalyst and Flex 4 training @ Webinale 2010 http://bloginblack.de/agentk/workshop-rias-with-flash-catalyst-and-flex-4/ -- -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
