My use case is that I want to look at DAO cache and Lucene cache for hits/misses and size of SoftHashMap % relative to VM heap size. This is realy hard to get via stress test and lets you evalute your design decsssions. Also, I can force invalidate something out of turn. For example lets say I update content on the back end DB, now I want DAO and Lucene to reset.
Also my clients LOVE to look at monitors. Man I show them some stress test tool that shows sessions and what type they are, now all the digintaries look at it. THEY want to buy a 60" LCD to put in the recpetion of IT!
Monitoring makes them feel that they are doing something to the CEO.
The saying at IBM used to be that the value of system is messured by managemnt in pounds of paper it produces. Everyone loves reports on their desk.
1.5 has a bulit in JMX VM monitor, look at it once and there goes your productivity.
In the "old days", 3 tier meant client/server and managment tier.
JMX sounds scary but it was easy once I read up enough.
Also, I do not think it's intrusive now, in the sense thatno mater what the RequestProcessBeanThingObject is, it can be monitored.
I think it'd be one of the more popular features.
Hell, it can be done for 1.27 or whatever the counter says, and no, it does not force you to have 1.5 but I can't image it working w/1.3.
.V
Niall Pemberton wrote:
Sounds like a great idea and something that would be fun to do, but for me I don't deploy/change my *live* webapp that often and so theres no real selling point to my users to develop a feature like this - similar to the "Hot Deployment" stuff Jack/Michaels been talking about. I guess for people in larger teams (mines a team of one :-) it would probably sell itself as a development feature alone.
Niall
-
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
