• 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

relationship between Executor and ThreadMXBean

 
Ranch Hand
Posts: 77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If I use the PooledExecutor for running my threads and ThreadMXBean for monitoring and managing these threads, is there any realtionship between the two? In other words do I have to manually get the threads reference from PooledExecutor and monitor it in the ThreadMXBean. Both of these are new features in JDK1.5 but I am surprised that there is no connection between these two specific features.

Any suggestions/opinion is appreciated.

Thanks,
Basheer
 
author
Posts: 23951
142
jQuery Eclipse IDE Firefox Browser VI Editor C++ Chrome Java Linux Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In this case, I believe it is a design issue. The MBean that monitors the threading system, monitors it at the thread system level. That is how it was designed.

I guess it wouldn't be that hard to develop another mbean that gets registered when thread pools are created. You just need some experience with JMX.

Henry
[ December 30, 2005: Message edited by: Henry Wong ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic