I using CQ 5.6.1 and CRX version 2.4.30, the tar optimization is continue running after past default time.
So far i dint change anything in repository.xml and workspace.xml.
I view the log file and found this log.
org.apache.jackrabbit.core.query.lucene.IndexMerger merged 66 documents in 14 ms into _7hw6.
Solved! Go to Solution.
Views
Replies
Total Likes
You can verify TarPM is running or not by presence of file optimizeNow.tar in data tar location. File a daycare with all the logs & thread dump for official help. Generally seen this happening with hardware issues.
Views
Replies
Total Likes
This message does not belong to the TarOptimization, but is a message by the Lucene Index, which is merged every now and then. Nothing to worry about.
Cheers,
Jörg
Views
Replies
Total Likes
So its that mean my TarPM is not running now?
Because in JMX console, i found the count of TarOptimizationWork is continue increasing.
Thanks
Fisher
Views
Replies
Total Likes
You can verify TarPM is running or not by presence of file optimizeNow.tar in data tar location. File a daycare with all the logs & thread dump for official help. Generally seen this happening with hardware issues.
Views
Replies
Total Likes
Views
Likes
Replies