Menu

Jacob COM Fail Exception

Help
Pravir
2007-03-21
2013-04-25
  • Pravir

    Pravir - 2007-03-21

    Hi Christian,

    On executing data driven test using my jameleon script, ComFailException is thrown. Refer to stack trace below for details. Can you let me know why this error is thrown inconsistently for different line # in the CSV file?

    Regards,
    Pravir

    <log4j:message>com.jacob.com.ComFailException: Can't map name to dispid: Document
        at com.jacob.com.Dispatch.invokev(Native Method)
        at com.jacob.com.Dispatch.invokev(Dispatch.java:804)
        at com.jacob.com.Dispatch.get(Dispatch.java:1153)
        at com.tapsterrock.jiffie.IDispatch.getDispatchProperty(IDispatch.java:95)
        at com.tapsterrock.jiffie.InternetExplorer.getDocument(InternetExplorer.java:429)
        at net.sf.jameleon.plugin.jiffie.IEFunctionTag.getDocument(IEFunctionTag.java:205)
        at net.sf.jameleon.plugin.jiffie.IEFunctionTag.store(IEFunctionTag.java:162)
        at net.sf.jameleon.util.StateStorer.storeState(StateStorer.java:205)
        at net.sf.jameleon.util.StateStorer.eventOccured(StateStorer.java:129)
        at net.sf.jameleon.function.FunctionTag.doTag(FunctionTag.java:290)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
        at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
        at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
        at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
        at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
        at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
        at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:42)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
        at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
        at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
        at net.sf.jameleon.SessionTag.doTag(SessionTag.java:189)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
        at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
        at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
        at net.sf.jameleon.TestCaseTag.invokeChildren(TestCaseTag.java:658)
        at net.sf.jameleon.TestCaseTag.executeDrivableRow(TestCaseTag.java:725)
        at net.sf.jameleon.data.DataExecuter.executeData(DataExecuter.java:79)
        at net.sf.jameleon.TestCaseTag$2.run(TestCaseTag.java:882)
        at net.sf.jameleon.TestCaseTag.executeBody(TestCaseTag.java:929)
        at net.sf.jameleon.TestCaseTag.spanCSV(TestCaseTag.java:878)
        at net.sf.jameleon.TestCaseTag.doTag(TestCaseTag.java:813)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
        at org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:706)
        at org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:670)
        at org.apache.commons.jelly.JellyContext.runScript(JellyContext.java:579)
        at net.sf.jameleon.ExecuteTestCase.runScript(ExecuteTestCase.java:271)
        at net.sf.jameleon.ui.TestCasePane$ExecuteButtonAction$2.run(TestCasePane.java:293)

     
    • Christian Hargraves

      This is only for storing the state of the application. It doesn't look like it is causing your tests to fail. There are just some times when the Jiffie plug-in can't get the HTML to save.

       
    • Pravir

      Pravir - 2007-03-22

      Thanks Christian. Is there any specific reaons for this error to appear. Sometimes error is consistenly reproducible while other times it works totally fine.

      Please adivse as it is is very irritatin.

      Regards
      Pravir,

       
      • Christian Hargraves

        It turns out this message was being printed to std out instead of the log. I opened a bug for it (https://sourceforge.net/tracker/index.php?func=detail&aid=1686291&group_id=84246&atid=572239)

        and change the message to be logged at debug level. It will be included in the next release

         
    • Pravir

      Pravir - 2007-03-23

      Is there any temporary solution to it?

      Regards,
      Pravir.

       
      • Christian Hargraves

        nope. unless you want to build from the latest source code

         

Log in to post a comment.