In general that's right. Not knowing what your server config and actual values are, I'd assume max handler threads sits somewhere at high few hundreds or at 1000?
Now - 1000 would in most scenarios be too many - also note that depending on operating system, platform architecture etc there's a natural limit how many threads could be spawend in the first place - iirc 1000 is higher than some particular windows installations would allow. My recommendation is to set it to a few hundreds, let's say 500 and then start load testing. Also helpful: Reduce the heap slightly (as you've mentioned) and try applying small thread stack sizes (by using the -Xss argument). Again depending on platform, architecture and JVM vendor you'll find there are different default settings for the stack size, you'd need to find out which yours would be and then decrease from there. 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/ -- > 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. -- 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.
