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

    Harvester fails at 24% after applying SFX KB revision 20141000

    • Article Type: General
    • Product: SFX

    Problem Symptoms:
    After applying SFX KB revision 20141000, the Verde harvester fails about 24% of the way through the next bulk.

    The harvester_client.log contains errors as follows:

    FATAL [com.exlibris.verde.harvester.HarvesterProcess] Basic Operation failed
    com.exlibris.verde.api.exception.APIException
    at com.exlibris.verde.api.HarvesterMngmtServiceBean.initHarvesterPortion(HarvesterMngmtServiceBean.java:284)
    at sun.reflect.GeneratedMethodAccessor3839.invoke(Unknown Source)

    The server.log contains errors as follows:

    ERROR [com.exlibris.verde.harvester.SFXDBConnector] [RMI TCP Connection(725792)-xxxxxxxxx] SFXDBConnector - failed to read VERDE_GLOBAL portion
    ERROR [com.exlibris.verde.harvester.HarvesterDataCache] [RMI TCP Connection(725792)-xxxxxxxxx] Failed to init portions
    java.lang.StringIndexOutOfBoundsException: String index out of range: -263
    at java.lang.String.substring(String.java:1444)
    at com.exlibris.verde.harvester.HarvesterUtil.validateAndPrepareVerdeGlobal(HarvesterUtil.java:402)
    at com.exlibris.verde.harvester.SFXDBConnector.getVerdeGlobalPortion(SFXDBConnector.java:275)
    at com.exlibris.verde.harvester.SFXDBConnector.initPortion(SFXDBConnector.java:223)

    Cause:
    There is a new issue in SFX regarding objects that have many related objects. This causes the object information in the publishing tables to hit the character limit.

    Resolution:
    We will release a solution for this issue later today or tomorrow. This article will be updated with instructions on how to apply the fix.


    • Article last edited: 3/19/2014
    • Was this article helpful?
    //doorbell.io feedback widged