Here are some tips and tricks for troubleshooting validation problems using ACTF.
There are several sources of debug information when running Inter-JVM (external AOP-based) validations using one of the ACTF launch configurations. These include:
Here are some particular problems you may encounter when running an AOP-based validation and a proposed solution for them.
Problem | Solution |
---|---|
Reports seem clearly incorrect (e.g. far too many errors and warnings). |
This might be due to a number of factors. First, check the file containing the external dump of the launched JVM or application - actf_jvm_trace.out by default (see AOP Properties). If there are exceptions indicating that the actf-msaa.dll file is not found, remember that the JVM you are using must be able to find this .dll file. It does so by looking in its jre/bin directory so be sure that such a dll exists in that directory and that you are using the JVM you think you are using. Another problem may be related to the classpath referenced by the script code interpreter you are using. Double-check the path(s) in the relevant path preference pages (e.g. the Interpreter Paths preference page or the Code Processor classpath on the Languages Preference Page. |
No validations for or failure to launch an Eclipse installation or instance of an Eclipse-based product |
When using the Eclipse Application with ACTF launch configuration keep in mind that the following system properties must be set on the properties tab of the AOP Preference page:
The latter two properties may only need to be set when launching using a JVM 1.4.2. |