Other error messages
In addition to error messages generated by the DITA Open Toolkit, you might also encounter error messages generated by Java or other tools.
Out of Memory error
In some cases, you might receive a message stating the build has failed due to an Out of Memory error. Try the following approaches to resolve the problem:
- Increase the memory available to Java.
- Reduce memory consumption by setting the generate-debug-attributes option to
false. This option is set in the lib/configuration.properties file. This will disable debug attribute generation (used to trace DITA-OT error messages back to source files) and will reduce memory consumption.
dita.preprocess.reloadstylesheetAnt property to
true. This will allow the XSLT processor to release memory when converting multiple files.
- Run the transformation again.
java.io.IOException: Can't store Document
After running a JavaHelp transformation, you may receive a java.io.IOException: Can't store Document message.
This problem occurs when HTML files unrelated to the current transformation are found in the output directory. Delete the content of the output directory and run the transformation again.
If you receive a
java.lang.UnsupportedClassVersionError error message with an
Unsupported major.minor version and a list of Java classes, make sure your system meets the
minimum Java requirements as listed in the Release Notes and installation instructions.
Unable to locate tools.jar
If a Java Runtime Environment (JRE) is used when building output via Ant, the Unable to locate tools.jar error may appear. This message is safe to ignore, since DITA-OT does not rely on any of the functions in this library. If a Java Development Kit (JDK) is also installed, setting the JAVA_HOME environment variable to the location of the JDK will prevent this message from appearing.