none
JDBC Connector Intermittent Issue related to non-existance of all.log file RRS feed

  • Question

  • Hi

    I am using JDBC Connector V 5.2 on top of FAST ESP 5.3. Every thing is working fine, but sometimes the JDBC Connector displaying the below warning message.

    00:02:33,093 WARN  [CCTKDocumentFeeder] java.io.FileNotFoundException: all.log (No such file or directory)Cannot open log file: /opt/datasearch/var/log/connectors/jdbc/<<collection name>>/all.log No logging to file enabled

    The "WorkFolder" location in Configuration file is as below.
    /opt/datasearch/var/log/connectors/jdbc

    I also activated the DEBUG logging for JDBC Connector.

    Start 2013/06/23 23:00:19
    The Collection name is : <<Collection Name>>
    Deleted connector output file successfully
    Starting Database Extraction
    23:00:38,456 INFO  [JDBCConnector] Starting the connector!
    23:00:38,495 DEBUG [JDBCConnector] localConfigfileName: /opt/datasearch/data/connectorcontroller/JDBCConnector_<<Collection Name>>.xml
    23:00:38,498 DEBUG [JDBCConnector] Action:start
    00:02:32,806 INFO  [JDBCConnector] Validating config.......
    00:02:32,808 DEBUG [JDBCConnector] Start read config
    00:02:33,013 DEBUG [JDBCConnector] Finished reading configuration
    00:02:33,017 INFO  [JDBCConnector] Initializing.......
    00:02:33,021 DEBUG [JDBCConnector] Starting initialization
    00:02:33,054 DEBUG [JDBCConnector] Finished initialization
    00:02:33,062 INFO  [JDBCConnector] Starting crawl.......
    00:02:33,071 INFO  [JDBCConnector] Will start up publishers......
    00:02:33,093 WARN  [CCTKDocumentFeeder] java.io.FileNotFoundException: all.log (No such file or directory)Cannot open log file: /opt/datasearch/var/log/connectors/jdbc/<<collection name>>/all.log No logging to file enabled

    The reason why I am saying this issue as intermittent because in another run it works fine as below.

    Start 2013/06/24 23:00:23
    The Collection name is : <<Collection Name>>
    Deleted connector output file successfully
    Starting Database Extraction
    23:00:41,601 INFO  [JDBCConnector] Starting the connector!
    23:00:41,655 DEBUG [JDBCConnector] localConfigfileName: /opt/datasearch/data/connectorcontroller/JDBCConnector_<<Collection Name>>.xml
    23:00:41,656 DEBUG [JDBCConnector] Action:start
    23:00:43,112 INFO  [JDBCConnector] Validating config.......
    23:00:43,113 DEBUG [JDBCConnector] Start read config
    23:00:43,484 DEBUG [JDBCConnector] Finished reading configuration
    23:00:43,487 INFO  [JDBCConnector] Initializing.......
    23:00:43,491 DEBUG [JDBCConnector] Starting initialization
    23:00:43,515 DEBUG [JDBCConnector] Finished initialization
    23:00:43,522 INFO  [JDBCConnector] Starting crawl.......
    23:00:43,529 INFO  [JDBCConnector] Will start up publishers......
    23:00:43,654 INFO  [CCTKDocumentFeeder] Publisher :Initializing: com.fastsearch.esp.cctk.publishers.CCTKDocumentFeeder
    23:00:43,737 DEBUG [ChangeDetectorHypersonic] Change detection initialized:

    After comparing both logs, I found that this warning of "all.log" is generating in only when it is waiting for validating the config file. In first run(the error one), you can see that it waited for 1 Hour 2 Minutes between "Action:Start" and "validating config".

    As of now I am not able to get that why the connector is waiting for more than 1 hour in showing "validating config" message and this all.log file error occurs after that.

    Please let me know if anyone else have faced this issue earlier.


    Ashish Gupta Click "Vote As Helpful"! if you think that post is helpful in responding your question click "Mark As Answer, if you think that this is your answer for your question.



    • Edited by meashish Thursday, June 27, 2013 2:40 PM
    Tuesday, June 25, 2013 4:15 PM

Answers

  • Hi Ashish,

    An item I would suggest look at is the version of Java that is being used.  It should work if you are using the 32bit Java, and you are using a JVM at 1.6_28 or below.  Also, I would recommend the latest version of the JDBC connector, which is 5.2 SP1 with jdbcconnector_5_2_sp1_complete_patch07.  Let us know your findings, and if you have questions.

    Thanks!

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

    Customer Service   & Support                            Microsoft| Services

    Friday, November 15, 2013 9:18 PM
    Moderator

All replies

  • Hi Ashish,

    If you are still seeing this problem, what does your JDBC Connector configuration file show for the work folder? Is it set to "./"?  If so, could you change that to "../var" and then retry the connector job?  This could be due to a permissions issue as it is trying to find the all.log file in the bin/[collection_name] folder, which may not exist.

    Thanks!

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

    Customer Service   & Support                            Microsoft| Services

    Tuesday, September 24, 2013 2:02 PM
    Moderator
  • Hi Rob, Thanks for your reply. There are more than one configurtion for JDBC Connectors and and work folder in all ise not set to "./" It is set to "$FASTSRCH/var/log/connectors/jdbc" in which every collection creates a folder with collection name and having files (one of the file out of them is all.log). Thanks Ashish

    Ashish Gupta Click "Vote As Helpful"! if you think that post is helpful in responding your question click "Mark As Answer, if you think that this is your answer for your question.

    Wednesday, September 25, 2013 5:38 PM
  • Hi Ashish,

    An item I would suggest look at is the version of Java that is being used.  It should work if you are using the 32bit Java, and you are using a JVM at 1.6_28 or below.  Also, I would recommend the latest version of the JDBC connector, which is 5.2 SP1 with jdbcconnector_5_2_sp1_complete_patch07.  Let us know your findings, and if you have questions.

    Thanks!

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

    Customer Service   & Support                            Microsoft| Services

    Friday, November 15, 2013 9:18 PM
    Moderator