Chapter 8.  Typical Errors

Errors may happen and good error messages will help to solve a problem. Some typical problems will be described in the following sections.

PDFUnit Evaluation Mode - Limit reached

50 test cases can be executed by the PDFUnit-Monitor when it runs in evaluation mode. Each following test case will fail with the error message:

You have to restart the application. Ask for a test license to evaluate PDFUnit without these messages. Write a mail to info[at]pdfunit.com.

Starting the Application Twice - Logging Port in Use

The internal logging appender 'PDFUnitMonitorAppender' (see log4j2.xml) sends the validation results to the user interface using port 4445. If the application was started a second time, the port is in use by the first started PDFUnit-Monitor and an error message is shown:

If this port is used by another application, change the port in pdfunit-monitor.config and in log4j2.xml.

Incomplete Rendering of the Directory Tree

Sometimes, a file name appears incomplete. By pressing the button 'Reset All', all tests run again and the view is refreshed. If you need to preserve the result, export it first.

Configuration pdfunit.config not in Classpath

If the config file pdfunit.config is not found in installation directory, the PDFUnit-Monitor sends the message:

If you want to verify that all required files can be found in the classpath, run the script verifyInstallation.bat (oder verifyInstallation.sh) and read the report verifyInstallation_result.html. You should see 'Summary: No Errors'.

Configuration pdfunit-monitor.config not in Classpath

If the file pdfunit-monitor.config is not in the classpath, then the following message is shown immediately after you try to start PDFUnit-Monitor: