My belief is that the threads go busy and never release. I don't know if a stuck thread results in a new one being assigned to a request or if new requests get stuck also. Though I've seen the result all too often I've never been able to determine a cause. But once it happens it cascades until there are no threads left.
Lil
On 1/13/2009 at 4:24 PM, "Jeffrey Sessler" <Jeff at ScrippsCollege.edu> wrote:
> I'd be looking for other issues since I find it hard to believe that 217
> concurrent users would ever result in 75 busy threads.
>> My Webaccess will sometimes have 500+ users and I seldom see the peak
> threads go above 10. In fact, my max is set to 24 and I've never run out.
>> Jeff
>>>>> "Diana Morgan" <Diana.Morgan at pisd.edu> 1/13/2009 9:39 AM >>>
> On my webmail server I see the "request rejected because all threads are
> busy" message on the console log. Where in Console One can I adjust
> those settings? Right now on the console it shows for the threads:
> 75/75/75 (busy/total/peak). There are 217 users logged in. It
> happened yesterday and I rebooted the server. But now it's happening
> the very next day. It is running GW7.0.1.
>>> --
> Visit http://www.ngwlist.com for help unsubscribing