Pull Request Closed #github #java
Pcp Integration <[email protected]>
| Newsgroups | gmane.comp.sysutils.pcp |
|---|---|
| Message-ID | <[email protected]> |
[performancecopilot/parfait] Pull request closed by natoscott ( https://github.com/natoscott ) : #36 Implement the JMX proxying mode in the parfait-agent jar ( https://github.com/performancecopilot/parfait/pull/36 ) This provides a main() method in ParfaitAgent, and all the supporting code/springbean configuration, allowing separate java processes to be monitored. i.e. this now works: java -jar ./lib/parfait.jar -connect=localhost:9875 when a second java program is running with JMX access to port 9875 made available. That is done via properties, e.g. via .properties file or on the command line: java \ -Dcom.sun.management.jmxremote \ -Dcom.sun.management.jmxremote.port=9875 \ -Dcom.sun.management.jmxremote.local.only=false \ -Dcom.sun.management.jmxremote.authenticate=false \ -Dcom.sun.management.jmxremote.ssl=false \ MyApplicationMainClass The other parfait-agent configuration options are also still available, like -Dparfait.name, -Dparfait.interval and so on for fine-tuning the parfait proxy process behaviour. On an implementation note, spring profiles are used to allow mbean definition sharing between the different modes, and to inject different mbeanserver definitions - see local.xml and proxy.xml in particular (and