Customer Portal

Phase initialization failed with reason: XML ...FATAL ERROR

Comments 6

  • Avatar
    jurban
    0
    Comment actions Permalink
    Hi, which command line arguments are you using? I suspect you're using the "-loghost" argument, which should be used only when running a CloverETL graph from the CloverETL Designer.

    Jaro
  • Avatar
    pmisra
    0
    Comment actions Permalink
    ok, Thanks for the reply.

    I went back to the code and altered the engine initialization code to the following, but still got the same error. Are there any other values that I need to give for engine initialization?

    EngineInitializer.initEngine("plugins", null, null);
  • Avatar
    jurban
    0
    Comment actions Permalink
    Hi,
    I've tried your modified code (without the localhost loghost) and I don't get the logging initialization error. Are you sure you're running and building it correctly?

    Jaro
  • Avatar
    pmisra
    0
    Comment actions Permalink
    Thanks a lot for the prompt reply Jurban.

    I am running this code in eclipse as a main program, and trying to build the transformation graph and execute it to consume a XML file. The project has clover etl engine version 2.8.0 added as a dependency library and other supporting libraries. The eclipse environment is also having the evaluatation version of clover ETL designer installed.

    I am trying to build a graph of XMLExtract reading a XML file and dumping it into the Trash, but I am getting the error when the program execution reaches the line

    threadManager.executeWatchDog(watchDog);


    On further looking into the source code, I am getting the error while performing an initialization of XMLExtract component. The error is a NUllPointerException in the XMLExtract.init() method. The source of XMLExtract.java did not match the compiled binary of 2.8.0, so it is hard for me to say which line of the code has been causing problem.

    Some of the issues that might be causing the problems may be
    1. Some missing configuration that might be required. While I debugged more into the XMLExtract.java using the debug variables console, I say the projectURL variable to be null, could this cause the problem ?
    2. Can the Clover Designer plugin libraries conflict in any way in eclipse environment?
    3. Here is the list of dependencies I have in the eclipse project, am I missing any dependency?
      xmlbeans-2.3.0.jar
      annotations.jar
      commons-cli-1.1.jar
      commons-net-1.4.1.jar
      dom4j-1.6.1.jar
      icu4j-normalizer.jar
      jakarta-oro-2.0.8.jar
      janino.jar
      javolution.jar
      jms.jar
      joda-time-1.6.jar
      jsch-0.1.39.jar
      jsr173_1.0_api.jar
      jxl.jar
      ooxml-schemas-1.0.jar
      openxml4j-1.0-beta.jar
      poi-3.5-beta4-20081128.jar
      poi-ooxml-3.5-beta4-20081128.jar
      tar.jar
      cloveretl.engine.jar
      commons-logging.jar


    I would greatly appreciate some more clues on the same, Thanks again for your prompt support Jurban.
  • Avatar
    pmisra
    0
    Comment actions Permalink
    Hi,

    I am eagerly waiting for a solution to the above issue, I am not worried about the logger error, but if we scroll down the log uploaded above the execution is failing in the XMLExtract.init() method, for which I need help.

    Please help me get past this issue, Thanks.

    Regards
    Pankaj
  • Avatar
    pmisra
    0
    Comment actions Permalink
    Ok I was able to get a solution around the issue.

    I used the 2.7.2 set of clover engine, component jar and the third part jar. Surprisingly the XMLExtract is found in the thirdparty jar for 2.7.2 version of clover engine.

    Everything is running great after adding the required dependency.

    So most probably something went wrong while the XMLExtract was made a part of the component .jar in version 2.8.0, and I hope this finding helps clover to release another minor version of clover engine with issues like these fixed.

    But I would definitely would like to thank Jurban for his prompt support, nevertheless issues like these would need to be fixed asap, before more users face issues like these. Thanks.

    Regards
    Pankaj

Please sign in to leave a comment.