• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

websphere ORB Thread Pool and web container thread pool

 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have some confusion w.r.t the relationship between ORB thread pool and web container thread pool. I was under impression, if under *one* jvm, meaning deploying web component and ejb component under one websphere server instance, the ORB thread pool size is controlled by web container thread pool size. If this is correct, this means ejbs will get their thread allocated from web container thread pool.

However, at this moment, I can not find any office documentation proving this. Can someone please provide me more information on this topic, more specifically, is there such relationship provided by websphere server?

Thanks in advance!
 
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi West,

AFAIK there is no operational connection between WebContainer thread pool and ORB thread pool, except for the fact that if you're accessing your application via web transport and then making RMI stuff in your EJBs then you'll be consuming a thread from webcontainer and one or more from ORB thread pool (and if you're using JMS, then also some threads from 'default thread pool', which is again an independent one). The two are independent, and size of both are controlled independently and dynamically by WAS runtime according to your settings, workload and the way your application works.

Documentation about different thread pools are scattered across infocenter, especially at tuning pages, but I also failed to find one that summarizes all.

Nonetheless, you can log into administrative console of a running instance, navigate to Monitoring and Tuning/ Performance Viwer/ Current Activity, expand thread pools node, and see all different thread pools you're using under a certain JVM, including their respective sizes and utilization at that time, and figure out how you utilize them.
 
reply
    Bookmark Topic Watch Topic
  • New Topic