During JavaOne the benefits of jconsole, distributed with Java 1.5,
were demonstrated for managing Java apps. If your application is
instrumented and JMX compliant you can monitor your app's behavior
using jconsole while your app is running. You can invoke jconsole
after your app's started and even monitor across a network. As Sun
state, you can:
* Detect low memory
* Enable or disable GC and class loading verbose tracing
* Detect deadlocks
* Control the log level of any loggers in an application
* Access OS resources—Sun's platform extension
* Manage an application's Managed Beans (MBeans)
Apple's Java 1.5 implementation includes jconsole (on my system):
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/
jconsole
Unfortunately this implementation has a bug (4169426) that prevents
some of the VM data being displayed. However, the MBean pane does
work and can be used to gain access to VM data and any JMX-compliant
app-data.
Rob
P.S. If this is old-news I apologize. jconsole/JMX's benefits are
evident and seemed worth mentioning (repeating) _______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/java-dev/email@hidden
