KonaKart uses standard log4j logging.

The KonaKart engines search for logging properties files in the following order on the classpath:

If none of the above are found on the classpath a few hard-coded properties are defined for basic logging by default.

Logging can be enabled for selected parts of the system and the level of the logging tuned as required. Use the following logging levels:

"DEBUG" logging will show the most detail.

The logging properties file "konakart-logging.properties" contains a set of the most commonly-used KonaKart logging properties. Simply edit this file to modify the logging level of the subsystem you need logging for. (You will find the file under the classes directories of both the konakart and konakartadmin webapps - e.g. webapps/konakart/WEB-INF/classes)

A very common example is to set the logging to display SQL that is being executed by KonaKart. You would do this by setting the following properties:

			# Torque/Village Persistence layer
			# Set both to DEBUG
			to see the SQL
			log4j.logger.org.apache.torque.util.BasePeer = DEBUG
			log4j.logger.com.workingdogs.village = DEBUG	

		

For any logging changes to take effect you have to refresh the caches from the Admin Application (Tools >> Refresh Caches). Alternatively you can simply restart Tomcat.