Hi tramasoli,
This might be an issue with caching. We had a defect that might lead to such log lines that has been fixed in the current releases (5.6.4 and later).
Please open a support case so that we can verify what exactly is going on here.
Best,
Jakob