Fast ESP batch file run gives message :05:52:27,160 INFO [CCTKDocumentFeeder] Total number of failed callbacks......:1 RRS feed

  • Question

  • How can i find which document has failed .Is there any log which tells list of documents feed succesfully nad which all failed?
    Monday, September 15, 2014 12:12 PM

All replies

  • Hello,

    It looks like you are using the CCTK to create a custom feeder to feed content to ESP.  Have you configured your connector to write log messages, such as the document name that was being processed?

    The CCTK Guide discusses, on page 31, how the connector can log messages, and how you can configure your connector to log information.  The log does not out of the box have a report that shows a list of successful and failed documents, but you could likely write code that does that task.  Below is an excerpt from the guide:

    Main classes and methods:

    The core logging functionality is built on log4j, but there is a wrapper class called CCTKLogger that has a few convenience methods. It reads its configuration from a file named cctklog4j.xml; this file must exist in the CLASSPATH of the executable. It has a constructor that can take a connector configuration as input, from which it reads the collection name that the connector feeds to.This is used to make sure that the file log is written to a folder with the same name as the collection, and that the network logger refers to the collection log for all its messages. In addition, it has standard methods for logging at various log levels and for getting the stack trace from an exception.

    There is a network logger class called ESPLogServerAppender.This class can be referred to in cctklog4j.xml and be used to send all log messages directly to a log server instance of a FAST ESP installation.

    The toolkit supports a RollingFileAppender from log4j.The specification of this is found in the cctklog4j.xml file.

    For more information on log4j, see


    The most important sections in the cctklog4j.xml file are as follows:

    All messages from CCTK including DEBUG level will be logged:

    <logger name="com.fastsearch.esp.cctk"> <level value="DEBUG"/> </logger>

    All other sources, for example from contentapi, are logged from WARN.

    <!-- where all messages from the system go -->


    <!-- change to DEBUG for more output -->

    <level value="WARN"/>

    <appender-ref ref="console"/>

    <appender-ref ref="asyncfile"/>

    <appender-ref ref="net"/>


    Example Code:

    //Create a logger

    CCTKLogger logger = new CCTKLogger.getInstance(configuration,_MODULE_NAME);

    //Log a warning

    logger.logWarning("This is a warning");

    //Log error with stack trace

    logger.logError("Major problem",myException);

    Generally speaking, f your document was successfully processed by the connector, you could also view the logs from the various feeding chain components, such as the content distributor, indexing dispatcher, document processors, and the indexing logs at the time the batch was processed.  However, based on your log message, it seems that your document failed during the connector run.  For starters, you could enable debug logging on the connector, and go from there.  Let us know your findings, and if you have any questions.


    Rob Vazzana | Sr Support Escalation Engineer | US Customer Service & Support

    Customer Service   & Support                            Microsoft| Services

    Wednesday, September 17, 2014 7:22 PM