Perfmon4j

This minor maintenance release includes features to make XML configuration less error-prone.

The ability to monitor SQL execution time was added. This feature provides composite monitoring that allows you to determine what percentage of time is spent in the SQL vs the Java application layer.

This release adds a powerful new way to force thread trace monitoring on a specific thread (or a specific request). You can now force a thread trace based on one of the following: HTTP request parameter, HTTP session parameter, HTTP cookie, thread name, or thread property. There is more support for logging performance and monitoring information to an SQL database. In addition to MySQL and SQL Server, there are also create scripts for Oracle and PostgreSQL.

A SQL-based appender for interval data was added. You can now configure timing data to be written to a SQL database. An "Output Interval data to a SQL Database" section was added to Perfmon4j-ConfigSamples.pdf with configuration examples. Problems where release Jars were not compiled for Java 1.5, the Log4j logger did not include Throwable, and reloading the appender failed to propagate attributes were fixed.

The option to instrument getters and setters is now provided. A severe defect was fixed in which the global classloader incorrectly maintained reference to classes that have been unloaded by classloader. A minor defect was fixed in which a Null Pointer Exception was thrown when a named appender does not exist in the configuration of SnapShotMonitor. A minor defect was fixed in which loading a snapshot monitor containing a non-public annotated method failed.