Hi,
We are trying to do indexing and looks like it is not completing. It was showing partially indexed for one of the branch.
So started the complete reindex again, but still showing errors in the logs and looks like it is not going to complete:
[04 Apr 2016 22:18:07,230] WARN com.interwoven.hunter.index.IdolIndexHelper (WorkareaIndexJobProcessor-0) - waitForIndexToComplete(): GetQueryTagValues command return 0 value. retry=97
[04 Apr 2016 22:18:17,235] WARN com.interwoven.hunter.index.IdolIndexHelper (WorkareaIndexJobProcessor-0) - waitForIndexToComplete(): GetQueryTagValues command return 0 value. retry=98
[04 Apr 2016 22:18:27,428] WARN com.interwoven.hunter.index.IdolIndexHelper (WorkareaIndexJobProcessor-0) - waitForIndexToComplete(): GetQueryTagValues command return 0 value. retry=99
[04 Apr 2016 22:18:36,477] INFO com.interwoven.hunter.index.WorkareaIndexer (Thread-16) - Adding workarea event for //mdc1brc0303/default/main/MCOM/WORKAREA/temp_workarea
[04 Apr 2016 22:18:36,479] INFO com.interwoven.hunter.index.WorkareaIndexer (Thread-16) - Adding workarea event for //mdc1brc0303/default/main/MCOM/WORKAREA/work
[04 Apr 2016 22:18:37,432] WARN com.interwoven.hunter.index.IdolIndexHelper (WorkareaIndexJobProcessor-0) - waitForIndexToComplete(): GetQueryTagValues command return 0 value. retry=100
[04 Apr 2016 22:18:37,433] ERROR com.interwoven.hunter.index.WorkareaIndexJobProcessor (WorkareaIndexJobProcessor-0) - Couldn't complete workarea indexing due to exception. Remove this from pending requests!
Error Code :-1
com.interwoven.hunter.index.api.IndexException: The index job with index id (1459821695976) is incomplete.
at com.interwoven.hunter.index.IdolIndexHelper.waitForIndexToComplete(IdolIndexHelper.java:259)
at com.interwoven.hunter.index.IndexServiceCFSImpl.indexWorkarea(IndexServiceCFSImpl.java:252)
at com.interwoven.hunter.index.WorkareaIndexJobProcessor.processNextJob(WorkareaIndexJobProcessor.java:65)
at com.interwoven.hunter.index.Indexer.run(Indexer.java:158)
at java.lang.Thread.run(Thread.java:662)
Did anyone seen this error before? Already opened a case with HP, but still waiting on their response.
Thanks
Ajay
