Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Indexing Fails immediately after execute

    • Article Type: General
    • Product: Primo
    • Product Version: 4
    • Relevant for Installation Type: Dedicated-Direct; Local;

    Problem Symptoms:
    ?· ? in BO - Process ends with Stopped error immediately after initiate.
    ?· FE_LOG:
    2013-01-27 23:30:14,448 INFO [t-Thread-200] [c-FullIndexJob] - "Indexing_and_Didumean_and_Hotswapping" is launched on 1/27/13 11:30 PM
    2013-01-27 23:30:14,646 ERROR [t-Thread-200] [c-syncQueue] - Exception: Index operation failed. Cause:
    2013-01-27 23:30:14,697 ERROR [t-Thread-200] [c-STDERR] - java.lang.RuntimeException: Index operation failed.
    2013-01-27 23:30:14,698 ERROR [t-Thread-200] [c-STDERR] - at com.exlibris.jaguar.utils.synchronization.syncQueue.update(syncQueue.java:84)
    2013-01-27 23:30:14,698 ERROR [t-Thread-200] [c-STDERR] - at java.util.Observable.notifyObservers(Observable.java:142)
    2013-01-27 23:30:14,698 ERROR [t-Thread-200] [c-STDERR] - at java.util.Observable.notifyObservers(Observable.java:98)
    2013-01-27 23:30:14,698 ERROR [t-Thread-200] [c-STDERR] - at com.exlibris.jaguar.utils.synchronization.syncObservable.notifyObservers(syncObservable.java:10)
    2013-01-27 23:30:14,698 ERROR [t-Thread-200] [c-STDERR] - at com.exlibris.jaguar.utils.synchronization.syncQueue.push(syncQueue.java:22)
    2013-01-27 23:30:14,710 ERROR [t-Thread-200] [c-STDERR] - at com.exlibris.jaguar.mng.indexing.IndexManager.runBatchIndex(IndexManager.java:118)
    2013-01-27 23:30:14,710 ERROR [t-Thread-200] [c-STDERR] - at com.exlibris.jaguar.mng.scheduling.jobs.FullIndexJob.execute(FullIndexJob.java:46)
    2013-01-27 23:30:14,710 ERROR [t-Thread-200] [c-STDERR] - at com.exlibris.jaguar.ejbs.JaguarExecutorBean$3.run(JaguarExecutorBean.java:110)
    2013-01-27 23:30:14,711 ERROR [t-Thread-200] [c-STDERR] - Caused by: com.exlibris.jaguar.JaguarException: Index operation failed.
    .
    .
    .
    2013-01-27 23:30:14,711 ERROR [t-Thread-200] [c-FullIndexJob] - Exception: java.lang.RuntimeException: Index operation failed. Cause:
    com.exlibris.jaguar.JaguarException: Index operation failed.
    java.lang.NullPointerException
    at com.exlibris.jaguar.mng.indexing.IndexManager.runMethod(IndexManager.java:595)
    at com.exlibris.jaguar.utils.synchronization.syncQueue.update(syncQueue.java:81)
    at java.util.Observable.notifyObservers(Observable.java:142)
    at java.util.Observable.notifyObservers(Observable.java:98)
    at com.exlibris.jaguar.utils.synchronization.syncObservable.notifyObservers(syncObservable.java:10)
    at com.exlibris.jaguar.utils.synchronization.syncQueue.push(syncQueue.java:22)
    at com.exlibris.jaguar.mng.indexing.IndexManager.runBatchIndex(IndexManager.java:118)
    at com.exlibris.jaguar.mng.scheduling.jobs.FullIndexJob.execute(FullIndexJob.java:46)
    at com.exlibris.jaguar.ejbs.JaguarExecutorBean$3.run(JaguarExecutorBean.java:110)
    Caused by: java.lang.NullPointerException
    at com.exlibris.jaguar.mng.indexing.IndexManager.checkIndexStatus(IndexManager.java:245)
    at com.exlibris.jaguar.mng.indexing.IndexManager.internalRunBatchIndex(IndexManager.java:135)
    at com.exlibris.jaguar.mng.indexing.IndexManager.runMethod(IndexManager.java:593)

    Cause:
    In Indexing Folder (e.g. /exlibris/primo/indexes/px_y - location may vary between installations):
    File indexStatus had bad syntax.

    Resolution:
    1. Backup the original indexStatus to indexStatus.<DATE>
    2. Alter the file: syntax should to look like:
    #Mon Feb 04 16:05:28 CET 2013
    dum.status=DUM_FINISHED
    indexing.status=INDEXING_FINISHED

    Category: Search Engine

    Subject: Indexing


    • Article last edited: 11/3/2015
    //doorbell.io feedback widged