Error messages and troubleshooting This section contains information about problems that you might encounter and how to resolve them. Logging build informationWhen you run DITA-OT, key information is logged on the screen. This information can also be written to a log file. If you encounter a problem, you can analyze this information to determine the source of the problem and then take action to resolve it.Enabling debug modeDebug logging prints considerably more additional information. The debug log includes all information from the verbose log, plus details on Java classes, additional Ant properties and overrides, preprocessing filters, parameters, and stages, and the complete build sequence. The debug log can help you determine the root cause of a problem.DITA-OT error messagesThis topic lists each error message generated by the toolkit and provides additional information that might be helpful in understanding and resolving the error condition. If your toolkit installation includes custom plug-ins that define additional messages, you can add to this list by rebuilding the DITA-OT documentation.Other error messagesIn addition to error messages that DITA Open Toolkit generates, you might also encounter error messages generated by Java or other tools.Accessing help for the dita commandYou can access a list of subcommands and supported parameters for the dita command by passing the --help option on the command line.Increasing Java memory allocationIf you are working with large documents with extensive metadata or key references, you will need to increase the memory allocation for the Java process. You can do this from the command-line prompt for a specific session, or you can increase the value of the ANT_OPTS environment variable.Speeding up buildsSeveral configuration changes can significantly reduce DITA-OT processing time.