Mohan wrote:I can't speak for other people, but you are certainly jumping the gun. I wouldn't implement anything until I've seen it work; a working prototype is a good way to go to do an impact analysis on, plus you get some hands on experience that you can rely on when making decisions.
We are in the initial stages of using JMX and I might be jumping the gun here. What kind of WebLogic cluster and performance impact tests do people use when introducing JMX ? Here I mean the performance of the MBean server on a cluster and also the overhead of JMX itself. How do you think the application performance will be impacted by JMX ?
Mohan wrote:Well then you are not jumping the gun, you only provide incomplete information. Don't know what else can be said about the remaining gaps in your OP, its hard to tell what exactly you are asking for without stepping on your toes because you already did it but failed to mention it. Apparently you know how to create unit tests, so not much to add there without specifics. As for remaining tests, generally you don't code them but you perform them. I'm pretty sure that you know how to set up an environment for load testing and system integration tests, right?
Not sure how one can deduce so much from a open-ended question like this about the OP and the work. A prototype is already in the works.
as for the communication layer, jmx uses rmi by default, so the communication overhead will be similar to an rmi server.I think here you mean the way clients like JConsole connect to the MBean Server ??
Mohan wrote:how would anyone else be able to give you the performance impact of your own custom code?as for the communication layer, jmx uses rmi by default, so the communication overhead will be similar to an rmi server.I think here you mean the way clients like JConsole connect to the MBean Server ??
I was thinking of custom Java code within the VM that connects to the server and exposes the MBeans over HTTP/JSON to a browser.
how would anyone else be able to give you the performance impact of your own custom code?I am not getting the flow of your question here because I was asking about the default RMI part because HTTP/JSON is not as heavy as RMI and that could have a performance impact. A browser is sufficient to view the details.