CQ TarPM continue running after default time | Community
Skip to main content
F
Fisherwoon
October 16, 2015
Solved

CQ TarPM continue running after default time

  • October 16, 2015
  • 3 replies
  • 774 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

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. 

3 replies

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

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. 

F
FisherwoonAuthor
October 16, 2015

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

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 16, 2015

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

Terms & ConditionsAccessibility statement

Loading footer...