onJmyra
overview
features
screenshots
online demo
sales
downloads
pricing
nothing
support
faq
support request
report a bug
privacy statement
contact
impressum
webdesign by c.senftleben  

History of Changes

Changes from V2.0.3 to V2.0.4

The following changes were made in all editions of JMyra.

Fixed Bugs and Other Changes

  • Fixed HTML code to display active log levels on "edit log set" page
  • Fixed a NPE occurring under heavy load when using the "keep files open" strategy for writing logfiles.
  • A LogView filter referencing a context value caused a NullPointerException when the thread did not contain the context value or it was null. Fixed.
  • When a log group template changes its name all log groups referencing it are now updated correctly
  • cosmetic change: version number now displays properly on main page
  • added Jabber log destination
  • gracefully handle log messages that are null
  • AccumulatingMailDestination no longer starts its own control thread per instance
  • fixed HTML-generation in edit forms
  • The NDC context of log messages created by Log4J can now be displayed using the $(context:log4jndc) variable.
  • new format element $(property.)

The following change only applies to JMyra Enterprise Edition.

Fixed Bugs and Other Changes

  • Fixed a NPE when creating users without name or with existing name
  • Fixed a user statistics display bug when the number of segments or the segment duration was changed


Changes from V2.0.2 to V2.0.3

The main reason for this version was a JDK 1.4 API call that had been introduced with version 2.0.2. This call has been replaced to maintain compatibility to JDK 1.2.

The following changes were made in all editions of JMyra.

Fixed Bugs and Other Changes

  • Version 2.0.2 used a JDK 1.4 API. Changed to use 1.2 compatibe API
  • Fixed the link to the log format documentation on the LogView page
  • Email log destinations now always sets a valid date in the header
  • fixed link to MBean update attribute action
  • cosmetic changes to watchdog page
  • logView page is no longer centered
  • version is now visible on the start page
  • the HTML pages now contain a DOCTYPE tag
  • MBean pages now have return links to navigate up the hierarchy

The following change only applies to JMyra Enterprise Edition.

New Features

  • Experimental feature: garbage collection statistics


Changes from V2.0.1 to V2.0.2

The following changes were made in all editions of JMyra.

New Features

  • The log formatting macros may now contain a length. The value of the macro is cut resp. expanded to the specified length. Details on the online documentation of the formatting macros.
  • Added an "explanation" page to JMyra. This page shows where log messages will be processed for specified log groups and levels.
  • A small API change: The com.jmyra.logger.Logger class now contains constants for the user defined log levels.

Fixed Bugs and Other Changes

  • Applications with a configured working directory would not start when the classpath of JMyra contains relative paths
  • $(level) macros in log file names are no longer blank padded to 8 characters
  • A relative path in a file log destination is now interpreted as relative to the configuration directory instead of the current working directory
  • Fixed a bug that led to inconsistent log level assignments in some situations. This bug was introduced in version 2.0.1
  • Enhanced the interaction with Java security. This should get rid of a lot of problems when running JMyra in an EJB or servlet environment.
  • fixed a bug with absolute log file names not being interpreted correctly on some Windows configurations
  • Global active/inactive setting for log levels in a log set are now correctly stored and read back
  • writing log files was not thread-safe in all situations
  • removed some unneccessary debug-output
  • fixed a NullPointerException on receiving remote log messages that did not contain a log context
  • Applications could not be started by JMyra if the configuration referenced a log set configuration that no longer existed. Now log set marked for start-up is used.


Changes from V2.0 to V2.0.1

The following changes were made in all editions of JMyra.

New Features

  • added isxxxEnabled() methods to the LogAdapter, where xxx is a log level, for example isErrorEnabled(). This allows you to check whether the log level is currently enabled for the log group being used. You can use this feature to save the overhead to construct the log message in your code if it isn't going to be used anyways.
  • Log levels can now globally activated and deactived on the log set level. Up to now you had to disable log levels in the LogGroupTemplates, which was rather inconvenient if you had a lot of templates. The new settings can be found on the edit page of the log sets.

Fixed Bugs

  • some license files were not read correctly
  • some guided tours loggen an error message due to a problem in the configuration
  • the integrated web server expected each HTTP/1.1 client to send at least one CONNECTION header
  • Internal errors (not that there should be any!) were displayed with the wrong content type
  • when a log destination was renamed it was removed from all log levels that used it.