Neu iTech Logging Version 2.4.1

iTech Logging Version 2.6

The 2nd generation logging solution

Version 2.6 contains a bundle of changes:

Bugfix: Because of the ITLogLib initialization changes in ITL 2.5.1, ITLogBook often displayed no or the wrong module or/and case for a logmessage.

Introduction of ITLogLib2/.NET2:

ITLogLib2/.NET2 ("ITLogLib2DotNet2.dll") is a new variant of ITLogLib2, made for the .NET framework 2 and higher. It supports the same API as its predecessor, ITLogLib2/.NET (which is now better called ITLogLib2/.NET1), but is more robust.

The older ITLogLib2/.NET1 is still available and runs from .NET framework 1 on (and higher), but it runs into problems if your application is working with multiple application domains ("appdomains") and unloads the initial domain. This is a problem with the runtime code provided by Visual C++ 2002/.NET which practically cannot be solved!

Note: To run the new ITLogLib2/.NET2 on customer machines, the Visual C++ 8 Runtime Library (Release Version) is required. The iTech Logging Setup installs it, of course. If you build your own Setups containing ITLogLib2/.NET2, you should include the VC8 RTL merge module from Microsoft!

New (non-)blocking strategy "delete oldest logmessage":

The blocking strategies of the ITLogLib logging libraries determine what to do when a new logmessage is added for a logchannel, but the logmessage queue of this logchannel is already full. In practice this primarily happens when the current user doesn't have permissions to write to the logfile folders or if the logfile folders were placed on another machine which then became unavailable.

Previously the ITLogLib logging libraries only supported the following strategies:

Ignore limit: In this case the logmessages queues can be filled without limitation. This -- of course -- leads to the problem that the application can eat up more and more memory space and bring the system into trouble and/or crash.

Block sender: In this case an application thread that sends a logmessage to a full logmessage queue is blocked until the logmessage output works again.

Now you can -- and should -- use the new blocking strategy:

Delete oldest logmessage: In this case, if an application thread sends a logmessage to a full logmessage queue, the oldest logmessage in the queue is deleted to make place for the new logmessage. The logging application thread will not be blocked, and memory usage for logmessage storage will stay restricted.

If later the logmessage output works again, you first get a logmessage which tells how many logmessage had been thrown away in the meantime.

Example: Warning | 24.03.2008 20:04:07 | LOG | DELETED LOGMSGS | Number of deleted logmessages: 18.

The blocking strategy can be configured in ITConfigManager. Its main dialog has been completely redesigned to make it more user-friendly!

Diagnostic messages in the Windows event log:

For logchannels with output to files (i.e. not to ITLogServer/COM) you get an error message in the Windows Event log if the logging output doesn't work. This message is repeated from time to time -- currently every minute.

Here is an example for this kind of message:

Event Type: Error
Event Source: ITLogLib/COM-DLL
Event Category: None
Event ID: 0
Date: 24.03.2008
Time: 19:28:35
User: N/A
Computer: XP3
Description:
The description for Event ID ( 0 ) in Source ( ITLogLib/COM-DLL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:
Cannot create or open logfile: "c:\test\ITLogging2\LoggingDemoVB6\StdLog/LOG_2008_03_24/RUN20080324192817/20080324192835.ilf"!.

If the output works again, you get an info message like this:

Event Type: Information
Event Source: ITLogLib/COM-DLL
Event Category: None
Event ID: 0
Date: 24.03.2008
Time: 19:29:12
User: N/A
Computer: XP3
Description:
The description for Event ID ( 0 ) in Source ( ITLogLib/COM-DLL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:
Could now write logfile: "c:\test\ITLogging2\LoggingDemoVB6\StdLog/LOG_2008_03_24/RUN20080324192817/20080324192912.ilf"!.

HTML help files (*.CHM): All remaining HLP files were converted to the CHM format (compare the ITL 2.5 release notes).

Setup redesigned: The top level of the Setup feature hierarchy had become overloaded after adding more and more ITLogLib variants, and it was not easy to locate and select just the ITLogLib runtimes (versus the SDK and other stuff). This has been much improved now.

Note: The feature hierarchy is displayed in the Setup if you select "Custom" as the Setup Type. It is also displayed after installation if you go to the entry "iTech Logging 2" under "Add/Remove Programs", open it and chose the "Modify" option.

Go to: Download page, News page.

[ Home ]