• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Growing number of WOWorkerThreads to 32 -- deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Growing number of WOWorkerThreads to 32 -- deployment


  • Subject: Re: Growing number of WOWorkerThreads to 32 -- deployment
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 7 Jul 2004 09:14:00 -0700

On Jul 7, 2004, at 8:59 AM, Cretu Catalin wrote:

Hi,

We have some issues with our project in deployment. We
cannot see exactly what happened, but on the output
there is a message :
"Growing number of WOWorkerThreads to 32"
"Growing number of WOWorkerThreads to 64"

That means that a request is taking so long to return that more and more new requests are coming in and getting queued up. One worker thread is created for each request in the queue. This is a sign of a problem in your application. One cause could be a request that does a lot of processing. You can work around this with WOLongResponsePage, but it does have some issues of its own that you will need to deal with.

Another cause is deadlock in your application, either on session or editing context. Search the archives, wocode, and wodev for more information on the (several) causes of deadlock and solutions for them. Running on a recent version of WO helps too.

One other possibility is that your app is just overloaded: to many requests and too few instances.


But we have the message:
"Created adaptor of class WODefaultAdaptor on port
2015 and address opa/xxx.xxx.xxx.xxx with
WOWorkerThread minimum of 16 and maximum of 256"

I don't think those do much.


Somebody has any idea what means and/or how I can
setup the application not to create so many threads?

That is a symptom, not a problem. What you want to do is to fix your application so that it does not need so many worker threads.


Also from time to time in JavaMonitor we can see the
number of "Active Sessions" per instance is growing
very fast (the access to Java monitor is blocked -
port 1065 is not accessible)
1085 you mean?

Chuck


and the user access to
the application is down. Do you have any idea what
happened and how we can fix it?

Thanks,

Catalin






__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Growing number of WOWorkerThreads to 32 -- deployment (From: Cretu Catalin <email@hidden>)

  • Prev by Date: Growing number of WOWorkerThreads to 32 -- deployment
  • Next by Date: Re: SSDD + Tomcat
  • Previous by thread: Growing number of WOWorkerThreads to 32 -- deployment
  • Next by thread: Store files in the database?
  • Index(es):
    • Date
    • Thread