To report a bug, please send an email to support@launchsoftware.com.

Performance Problems
The performance of the application is related to a) the size of the messages files, b) the number of messages files that are in the messagesPath, c) the speed of disk access where the messages files are stored, and d) the frequency of refresh of the messages files.

If the refresh period is set too low, and there are many large messages files, then the application may be spending all of its time reading the contents of the files from disk. Reducing the frequency of refresh will help to alleviate this problem.

If the messages files are very large then performance will suffer, even though the contents of the files are cached in memory. To reduce the size of the messages files, it may be better to use the rolling file mechanism supported by Log4J and briefly described here. This will split the messages across multiple, smaller, files.

If there are a large number of log files, and potentially a large audience for those files, it may be better to use multiple instances of the Log4Web application in the web server or application server. Each instance can be configured with different messagesPath values, so that they are each handling a subset of the total set of messages files. Refer to the web server or application server documentation on how to create multiple instances of the Log4Web application.

Error Page is Displayed
Occasionally, Log4Web may display the following error page.

">

The reasons for this are explained on the page itself. The most likely cause is that the file list that Log4Web has cached, is out of date because a log file has been deleted. This page may also appear if the web server has been restarted. The problem should disappear on the next attempt to display the messages files.

Output Appears as Unformatted Text
If the messages page shows unformatted text instead of a table of messages, this is probably because the messages file is not an XML output file generated by Log4J. Click here for details on configuring Log4J to generate XML output files.

No Messages Appear in the Output
If the output display shows an empty set of messages, this may be because none of the messages conform to the filter parameters selected. However, this may also be because the messages files have been generated by an incompatible version of Log4J. Click here to discover how to select the version of Log4J that you are using.

Exceptions Thrown When Using JDK 1.4
This is caused by an incompatible set of XML parser classes being loaded into the JVM. JDK 1.4 provides its own copy of the XML parser classes. Unfortunately, it does not provide application developers with a straightforward way of using a different version of the XML parser classes. Check the FAQ for details on how to work around this problem.