How to report bugs

While using any computer errors can occur due to various causes. Current systems are becoming more complex and involved multiple programs and their machines.

As an example, a problem encountered when attempting to view a document may be due, among others the following reasons:

Therefore, in case of error should be collected much information as possible and try to analyze and identify all operations that cause the error (eg, "a specific operation on a given document type," "Any operation on a folder concrete "," The sequence: adding a document and immediately after delete ", etc..)

Providing the information collected on the sequence of operations and the environment in which failure occurs, this can be diagnosed and, or improve the documentation or correct the code erroneous.

To collect the errors OpenProdoc includes a web form. This form allows you to report an error or malfunction of OpenProdoc. Please include as much detail as possible, to help reproduce the error and correct it.

Errors Report Form

As specified in the license, the author is not liable in any respect by the use of OpenProdoc, but we will try to correct any errors found. Thank you for your cooperation.

How to identify bugs

When errors occur, it is necessary to collect information on the operations and errors encountered. This information may be collected automatically.

OpenProdoc configuration file "" contains two parameters related to the trace:

TRACELEVEL refers to the desired trace level:

Always default should be level 0 (ie TraceLevel = 0), level 2 temporarily activated when you want to detect an error.

TRACECONF indicates the path where is stored the file of the trace configuration (eg TRACECONF = /home/OPD/

By default, a file is provided but can be modified at will according to the log4j format, the tool used to log. For those who know log4j, should be noted that the log level parameter assigned in TraceLevel takes precedence over the value assigned in the configuration file

Help Index OpenProdoc