Topic
  • 2 replies
  • Latest Post - ‏2013-10-15T14:30:45Z by ClausSamuelsen
ClausSamuelsen
ClausSamuelsen
4 Posts

Pinned topic AQL module compilation fails

‏2013-04-22T16:42:18Z |

Compilation of AQL module fails with following message:

"org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator processing failed."

and in the error log is

"Caused by: java.lang.IllegalArgumentException: URI has an authority component"

 

BigInsights V2.0

Eclipse V3.6.2 on Windows 7

Eclipse is installed on a UNC path (\\servername\userpath) and workspace was also on the UNC device. I changed the workspace to the local drive (C:\), but I still get the error. Searching on the net shows that this problem typically is related to having the workspace on a UNC device. 

Eclipse error log:

!ENTRY com.ibm.biginsights.textanalytics.nature 4 0 2013-04-22 17:48:56.824
!MESSAGE Exception encountered during compilation
!STACK 0
java.lang.RuntimeException: org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator processing failed.   
at com.ibm.avatar.algebra.util.tokenize.MultilingualTokenizer.tokenizeStr(MultilingualTokenizer.java:224)
at com.ibm.avatar.algebra.util.dict.DictFile.compile(DictFile.java:558)
at com.ibm.avatar.aql.compiler.Compiler.compileDictionaries(Compiler.java:853)
at com.ibm.avatar.aql.compiler.Compiler.compileToTAM(Compiler.java:405)
at com.ibm.avatar.aql.compiler.Compiler.compile(Compiler.java:232)
at com.ibm.avatar.api.CompileAQL.compile(CompileAQL.java:279)
at com.ibm.biginsights.textanalytics.nature.ModularAQLBuilder.build(ModularAQLBuilder.java:382)
at com.ibm.biginsights.textanalytics.nature.ModularAQLBuilder.incrementalBuild(ModularAQLBuilder.java:851)
at com.ibm.biginsights.textanalytics.nature.ModularAQLBuilder.build(ModularAQLBuilder.java:173)
at com.ibm.biginsights.textanalytics.nature.AQLBuilder.build(AQLBuilder.java:69)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator processing failed.   
at org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:390)
at org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.processAndOutputNewCASes(PrimitiveAnalysisEngine_impl.java:298)
at org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.process(AnalysisEngineImplBase.java:267)
at com.ibm.avatar.algebra.util.tokenize.MultilingualTokenizer.tokenizeStr(MultilingualTokenizer.java:221)
... 21 more
Caused by: java.lang.IllegalArgumentException: URI has an authority component
at java.io.File.<init>(Unknown Source)
at com.ibm.dltj.tagger.impl.DLTTaggerDictionary.open(Unknown Source)
at com.ibm.dltj.tagger.impl.UnsupervisedRuleBasedTagger.open(Unknown Source)
at com.ibm.dltj.tagger.impl.AbstractTagger.open(Unknown Source)
at com.ibm.dltj.uima_annotator.pos_analysis.RuleBasedProcessingUnit.open(Unknown Source)
at com.ibm.dltj.uima_annotator.pos_analysis.ProcessingUnitFactory.get(Unknown Source)
at com.ibm.dltj.uima_annotator.pos_analysis.PartOfSpeechAnalyzer.open(Unknown Source)
at com.ibm.dltj.uima_annotator.lex_analysis.AnnotationsCreator.setCAS(Unknown Source)
at com.ibm.dltj.uima_annotator.lex_analysis.LexicalAnalyzer.process(Unknown Source)
at com.ibm.dltj.uima_annotator.implBase.jFrostAnnotator_ImplBase.process(Unknown Source)
at org.apache.uima.analysis_component.CasAnnotator_ImplBase.process(CasAnnotator_ImplBase.java:56)
at org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:376)
... 24 more

!ENTRY com.ibm.biginsights.textanalytics.nature 4 0 2013-04-22 17:48:56.870
!MESSAGE Exception encountered during compilation

org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator processing failed.

  • Simon ODoherty
    Simon ODoherty
    1 Post
    ACCEPTED ANSWER

    Re: AQL module compilation fails

    ‏2013-10-15T12:55:13Z  

    "Caused by: java.lang.IllegalArgumentException: URI has an authority component"

     

    Late response (as I only found this error as well). The issue relates to the fact you are installed on a UNC path. Map the path to a drive and reference that. 

  • Simon ODoherty
    Simon ODoherty
    1 Post

    Re: AQL module compilation fails

    ‏2013-10-15T12:55:13Z  

    "Caused by: java.lang.IllegalArgumentException: URI has an authority component"

     

    Late response (as I only found this error as well). The issue relates to the fact you are installed on a UNC path. Map the path to a drive and reference that. 

  • ClausSamuelsen
    ClausSamuelsen
    4 Posts

    Re: AQL module compilation fails

    ‏2013-10-15T14:30:45Z  

    "Caused by: java.lang.IllegalArgumentException: URI has an authority component"

     

    Late response (as I only found this error as well). The issue relates to the fact you are installed on a UNC path. Map the path to a drive and reference that. 

    Sorry, I should have replied long time ago, when I found the solution.

    Both Eclipse and the workspace must be on a local drive. It is not enough just to assign a drive name (e.g. E:\) to the remote drive.

    The problem only arises, when you're using the Multilingual Tokenizer. The Multilingual Tokenizer relies on UIMA to find its resources. It is UIMA, that requires the resources are on the local file system.

    If you can't use a local file system, you can as an alternative use the Standard Tokenizer. Since BigInsights v2 the Multilingual Tokenizer has been the default. To change this:

     

    First, enable the Advanced tab in the Text Analytics project properties. In Eclipse, go to Window > Preferences > BigInsights > Text Analytics and select "Show advanced tab..."

    Next, in the text analytics project, go to Preferences -> Text Analytics. Select the Advanced tab and choose default tokenizer.

     

    Regards

    Claus