To answer the original questions, max handler threads are basically running + queued threads, with an allowance for internal coldfusion processes as well. Wouldn't touch the setting, personally.
Running threads, usually set at 4 per processor, queued threads, you can set this as you please (though a lower value is safer). 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. Possible memory leak sources include: - site spiders/crawlers that create a new session with every request: if you are creating objects or large data structures within the session, that would be an issue - external applications, especially COM/.Net/Gateways - large structures in the application scope - caches, objects - large queries (cached or not) - too many SELECT *'s? - Data source memory leaks (esp. MySQL) I don't think modifying thread limits will fix the issue. On Mon, Apr 12, 2010 at 10:55 AM, Mark Ireland <[email protected]>wrote: > In my experience leaving the max set at 10 is a good rule of thumb. > > With Enterprise you can set an alert that kills the 11th thread (and only > that one) if it hangs up. > > > Date: Sun, 11 Apr 2010 17:33:41 -0700 > > Subject: [cfaussie] Coldfusion JRun Max handler threads setting > > From: [email protected] > > To: [email protected] > > > > > Hi all, > > > > Can anyone provide any advice on settings for the Max handler threads? > > As far as I know this is just the queue that threads sit in before > > being moved to the 'active handler threads' pool where they are > > actually executed. So new requests to the web server will sit in this > > queue until the server is free to process it. > > > > Our server processes threads pretty fast, but we have an issue at the > > moment where we get "java.lang.OutOfMemoryError: unable to create new > > native thread" on the odd occasion, normally when something hammers > > the server for a long period of time, I am going to possibly scale > > back the memory allocated to JRun so the operating system has more to > > play with, but I'm wondering if reducing the max handler threads pool > > will help this as well as there will be less total threads using up > > operating system memory? We don't actually need a large wait pool and > > it'd be better if requests got a server busy message rather than > > bloating out the available threads and thus operating system memory. > > > > Cheers > > Barry Chesterman. > > > > -- > > 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]<cfaussie%[email protected]> > . > > For more options, visit this group at > http://groups.google.com/group/cfaussie?hl=en. > > > > ------------------------------ > Looking for a hot date? View photos of singles in your > area!<http://clk.atdmt.com/NMN/go/150855801/direct/01/> > > -- > 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]<cfaussie%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/cfaussie?hl=en. > -- Joel Cass ----------------------------- http://www.jozza.net ----------------------------- -- 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.
