Re: Growing WOWorkerThread Problem

Growing the number of worker threads isn't the problem - it's a symptom. 
You're app is either taking longer to process requests than it can handle 
given the request rate or you've somehow deadlocked (in which case your 
requests are never going to return a response).

Good luck finding the root cause.

- sq

On Fri, 23 Jun 2006, Fred Wells wrote:

> Hello all,
>
> We are having a significant problem with all of our WO app with WOWorkerThreads.
>
> We get this message in our logs:
> <com.webobjects.appserver._private.WODefaultAdaptor>: Growing number of WOWorkerThreads to 32
> and when it gets particularly hungry:
> <com.webobjects.appserver._private.WODefaultAdaptor>: Growing number of WOWorkerThreads to 64
>
> The problem is, is this will completely render the app useless. If you are in a session you will get no response from the server and eventually the browser will give up. Or will bring up the first page[login in all of our apps] and then hang. There will be no indication of anything wrong in the logs except for the aformentioned 'Growing..' business. The only way to recover is to do a force quit through JavaMonitor or kill the process command line.
>
> The only sort of clue that we have is that we can sort recreate in two distinct activities:
> Heavy SQL queries [this is more random and not as consistent]
> Using thrird party jar to interact with another application:
> specifically Adobe Document Server.
>
> If anybody has encountered anything like this and has some insight that would be great.
>
> -thanks
>
>
> Frederick Wells
> Capps Digital
> 35 W Wacker
> 30th Fl.
> Chicago, IL
> 312.220.3056
> www.cappsdigital.com
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>
>