Notes for release 2.2.BETA

Changes

  • Mesaured performance overhead induced by InfraRED and published it as part of the project documentation
  • Made various tweaks to improve performance.
  • Added system property infrared.debug which controls InfraRED debug logging. If this system property (specified typically using -D JVM flag) is turned off (i.e its value is "false"), InfraRED will not log any debug messages even if the log4j configuration specifies debug level for the category. If the system property is turned on (i.e. its value is "true"), InfraRED will log debug message iff the category has log level DEBUG or more verbose. The default value of this system property is false.
  • infrared-agent.properties no longer allows case-insensitivity to boolean properties; it has to be either true or false.
  • Made various documentation improvements including bug# 1386837.
  • Renamed class net.sf.infrared.weblogic.setup.InfraRedApplicationLifeCycleListener to net.sf.infrared.weblogic.setup.InfraREDApplicationLifeCycleListener. See bug# 1388568.

Known Issues

  • When data is picked from the database, call traces are not shown.
  • We have noticed the JVM deadlocking sporadically on Weblogic server at startup. We are investigating this. Killing the server and restarting it works.
  • Peristed data collected with this version of InfraRED is not gaurenteed to work with future versions of InfraRED. As of now we don't maintain different versions of serialized objects.
  • If a class refers another one which is not in the CLASSPATH, the JVM will not complain at runtime if the code segment using the refered class is never executed. (When the class is compiled all classes referred need to be available). But both AspectJ and AspectWerkz will fail during aspect weaving (offline and load-time) of a class if one of the referred classes are missing. AspectJ5 has a feature where this does not happen, but InfraRED is not yet integrated with AspectJ 5.

    • Notes for release 2.2.ALPHA.1

    New Features

    • Presistence of collected data in a database; an in-process HSQLDB will be used for persistence by default.
    • Ability to track arbitarary context (beyong method calls and sql executions). An API is provided to write newer contexts and aspects.
    • Ability to load data from database and view it in the GUI
    • Easier installation
    • Ability to track JSP and Hibernate query execution times
    • Support for hierarchical and absolute layer

    Changes

    • Modified the ant task considerably
    • Uses AspectWerkz more. The recommended aspect system now is AspectWerkz with load-time weaving.
    • Restructured workspace and uses Maven 1.0.2 to build
    • No need to setup P6Spy pool connection now
    • Support for LocalCollectionStrategy is not available in this release. To view the statistics, you always need to deply InfraRED Web GUI WAR file.
    • Suport for snapshots (exporting and importing snapshots of performance statistics) is not available in this release. This release supports persisting performance statistics into a database, and we will provide support for snapshots in a future release.

    Known Issues

    • This release is not tested for performance. We plan to make a release soon with performance tests run.
    • When data is picked from the database, call traces are not shown.
    • We have noticed the JVM deadlocking sporadically on Weblogic server at startup. We are investigating this. Killing the server and restarting it works.
    • Peristed data collected with this version of InfraRED is not gaurenteed to work with future versions of InfraRED. As of now we don't maintain different versions of serialized objects.