Wednesday, November 16, 2005

jManage 1.0 beta2 is now available

You can download jManage 1.0 beta2 here.

Release Notes :

This is the beta2 release of the much awaited 1.0 version. Please see jManage home page for the list of features in 1.0.

To upgrade an existng jManage installation, please copy all files from the old jmanage_home/config dir to the new jmanage_home/config dir. E.g. copy files from jmanage-0.5.4/config to jmanage-1.0-beta2/config dir ("cp -r" on unix does the trick).
Please make sure you copy all files, specially "jmanage-key".

The following 0.5 install guide still holds good (except that the port number is now configured in jetty-config.xml):

Changes since 1.0 beta :

Feature Requests:

1333311 - Add to Application, etc, via Wildcard Reference
1357757 - Improve graphing module by adding yaxis label & scale factor

Bugs Fixed:

1350519 - NPE in connectionFailed.jsp
1354263 - Cluster level operations don't work in 1.0 beta
1351764 - #!/bin/sh needs to be first line in shell scripts
1350515 - does not work

Thursday, November 03, 2005

Using jManage 1.0 to connect to JDK 1.5

JDK1.5 exposes mangement information via a set of MBean registered in the platform MBeanServer. jManage can be used to manage and monitor a JDK 1.5 application.

To enable a JDK 1.5 application for remote monitoring, add the following system properties to your JDK1.5 application:

Add this application in jManage as a JSR160 application with the following URL:


You will see that you can monitor and manage ClassLoading, Memory, Threads, etc. You can even change the log level of your application, if your application uses JDK logging API.

Note that it is important to enable authentication for your production JDK1.5 application. To enable authentication and access control, please read this.