I see the same. And when this happens, memory and cpu consumption by CQ goes right up. Can someone shed some light as to when this might happen? I'm aware tar optimization runs overnight optimizing files, creating new optimized data files and deleting already processed files. It completes successfully most times, but I have seen the above warning many a times - it's as though tar optimisation process goes into a lock and can't stop successfully at 5am - and continues to show these warnings all day causing exceptionally slow response times.
It's a surprise I can't find any information on this - it happens in our environments and in my local too, and I'm certain others have experienced it.
Thanks in advance for taking the time out to reply.
I would also like to know how to resolve this.