Jboss profiler

[holeinone]

Maybe we could use the thinkwork that went into Jboss Profiler?
http://www.jboss.org/jbossprofiler/doc/concept.html

[kjkoster]

Dear holeinone,

Whoa. That's cool stuff. Nice find.

Whether or not we can do something like that with Java-monitor really depends on the run-time overheap of something like this. Java-monitor is intended to run once per minute, 24x7 and that means that we are not free to use everything that is available. We cannot slow down processing. To give you an idea: I worry about the thread deadlock detection overhead in larger systems.

I've been pondering over this for a while now, and I'm still trying to find ways for incorporate computationally expensive analysis in Java-monitor in a user-friendly fashion.

For now my guideline is simple:

Is the overhead (as good as) nil?
Can we express the outcome in a single mbean with a handful of attributes?


So, turning back to JBoss profiler:

What aspect of JBoss profiler would you like see included in Java-monitor?
And why? :)
Is the overhead (as good as) nil?
Can we express the outcome in a single mbean with a handful of attributes?


Kees Jan