Notes for release 2.4.1.BETA

Changes

  • Major ant task bug fix bug# 1486235: Fixed the bad injar error and added AJ 1.5 - Xlint.properties
  • Fixed other minor bugs in the ant task.
  • More junit tests to the collector module.

Notes for release 2.4.BETA

Changes

  • Added jdbc and sql layer implementations for Compile Time Weaving using P6spy
  • Fixed minor bugs in the ant task.

Notes for release 2.3.1.BETA

Changes

  • Fixed bug# 1460025 - Removed AspectJTools.jar from aspectsytem-all.jar
  • Fixed minor bugs in web-gui call trace display when the call tracing is disabled

Notes for release 2.3.ALPHA

Changes

  • The InfraRED Ant task issues are resolved and tested with various app servers.
  • Included an InfraRED demo along with the documentation
  • Fixed minor bugs in jdbc monitoring.

Notes for release 2.3.ALPHA

Changes

  • Integrated AspectJ-1.5. InfraRED now can take advantage of the load-time weaving features of AspectJ-1.5. As of now AspectWerkz is supported, but in future we might drop this support. (AspectWerkz project merged with AspectJ and as of now the project is abandoned). We would like to hear from the community about it.
  • InfraRED can now persist the performance data collected onto an Oracle database.
  • Improved display of SQL queries in InfraRED GUI
  • Added new property mbean-server-provider. This property defines the JMX implementation to be used to expose InfraRED configuration via JMX.
  • Added new property prepared-statement-monitoring-enabled. When this property is enabled, InfraRED tracks the values bound to a PreparedStatement.
  • Logging can be configured with infrared-log4j.properties along with infrared-log4j.xml
  • Fixed bugs 1435022, 1435005, 1432904 and 1434991
  • Added an aspect NonWrappingJdbcAspect as fix for bug# 1423202

Known Issues

  • We have not ensured that the InfraRED Ant task works fine in this release.
  • Bug# 1422185. A workaround for this is described in the troubleshooting page.
  • Incorrect data is displayed when an API directly or indirectly calls itself (direct or indirect recursion). We are working on fixing this.
  • When data is picked from the database, call traces are not shown.
  • We have noticed the JVM deadlocking sporadically on Weblogic server at startup, when using AspectWerkz for the weaving. 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-1.2 and AspectWerkz-2.0 will fail during aspect weaving (offline and load-time) of a class if one of the referred classes are missing. AspectJ-1.5 has a feature where this does not happen.

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.