This document has not been formally reviewed for accuracy and is provided "as is" for your convenience.
This article explains how to set up debug level logging for scrittura.
PLEASE NOTE: Customers need to be aware that as this action results in DEBUG log trace being switched on for all Scrittura Java classes, this could result in performance issues and it is better to selectively set debug on certain classes where possible (see Knowledge Base Article : KM03049382 ) If it is not known which classes are causing a certain issue, then it is best to test the effect of this under high load in a dev/pre environment before setting up in production
In log.cfg file
followed by a Set Config (Set All) operation .
A restart of the server may also be neccessary.
To ensure the change has worked you should see DEBUG traces in the scrittura logs that were'nt there before .