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

    Multi-threaded extract completes but throws exception, missing log summary

    • Article Type: General
    • Product: Voyager
    • Product Version: 8.2.0

    Problem Symptoms:
    * No extract summary in logs for multi-threaded extract
    * Error at command line similar to
    622862 [Thread-3] INFO com.endinfosys.voyager.extract.Extract - Disconnected from database
    Exception in thread "main" java.lang.NullPointerException

    Cause:
    This behavior is the result of VYG-5574.

    Resolution:
    Issue VYG-5574 is resolved for Voyager 9.1.0 and higher.

    Additional Information

    Replication steps:
    1. Run a multi-threaded Selective extract:
    1.a. cd /m1/voyager/xxxdb/sbin
    1.b. Pprimoexp.sel -f ../ini/PrimoExp-Selective.ini -B1 -E250000 -T5
    2. The extract runs and finishes with messages similar to the following:
    512027 [Thread-2] INFO com.endinfosys.voyager.extract.Extract - Disconnected from database
    535627 [Thread-4] INFO com.endinfosys.voyager.extract.Extract - Disconnected from database
    549621 [Thread-0] INFO com.endinfosys.voyager.extract.Extract - Disconnected from database
    591564 [Thread-1] INFO com.endinfosys.voyager.extract.Extract - Disconnected from database
    622862 [Thread-3] INFO com.endinfosys.voyager.extract.Extract - Disconnected from database
    Exception in thread "main" java.lang.NullPointerException
    at java.util.LinkedList$ListItr.next(LinkedList.java:891)
    at com.endinfosys.util.Stats.dumpTimedEventsSummary(Stats.java:397)
    at com.endinfosys.voyager.primo.PrimoExtract$StatGatherer.logStats(PrimoExtract.java:488)
    at com.endinfosys.voyager.primo.PrimoExtract$StatGatherer.logResults(PrimoExtract.java:428)
    at com.endinfosys.voyager.primo.PrimoExtract.runMultiThreaded(PrimoExtract.java:111)
    at com.endinfosys.voyager.primo.PrimoExtract.main(PrimoExtract.java:57)
    3. In individual log files in /m1/voyager/xxxdb/primo/Selective/logs, none contain summary of records extracted at the end.
    4. Run 1 extract for same bib_id range.
    5. Logs contain summaries and no exceptions or errors are shown at command line.
    2569938 [main] INFO com.endinfosys.voyager.extract.Extract - Disconnected from database
    2569941 [main] INFO com.endinfosys.voyager.extract.Extract - Simple status
    2569996 [main] INFO com.endinfosys.voyager.extract.Extract - ************************* START OF SUMMARY ***********************
    BIB-Range-AvailabilityHistory
    In 249438 visit(s) took 103207 millisecs for doing 399890 with 0 errors
    BIB-Range
    In 249438 visit(s) took 2433741 millisecs for doing 249438 with 0 errors
    2569996 [main] INFO com.endinfosys.voyager.extract.Extract - ************************** END OF SUMMARY ************************
    2569998 [main] INFO com.endinfosys.voyager.primo.PrimoExp - Wrote 249438 records to 250 files in /m1/voyager/bigdb/primo/Selective/bundled/
    2569998 [main] INFO com.endinfosys.voyager.primo.PrimoExp - Extract completed in 42 minutes 49 seconds

    Workaround: None.

    Category: Interoperability (Voy) - Voyager

    Subject: Primo (Voy) - Voyager


    • Article last edited: 10/17/2014
    //doorbell.io feedback widged