I am still not sure why there were alternate class loader in AnalysisComponentCasIterator.hasNext()->restoreClassLoaderUnlockCas() but the usual ResourceManagerFactory.setResourceManagerCreator() fixed the problem.
Best, Peter Am 16.05.2017 um 18:30 schrieb Peter Klügl: > Looks like it is a ClassLoader problem after all. There seem to be two > of them switching all the time... need to investigate further... > > > Peter > > > Am 16.05.2017 um 18:06 schrieb Peter Kluegl: >> Hi, >> >> >> I am currently stuck at a problem and do not find a way to debug it >> successfully. >> >> >> I have several analysis engines, some of them are ruta engines. In one >> of them, another uimaFIT analysis engine is called/executed within the >> rules. This causes somehow that the JCasGen annotation object are >> created anew after the engine since no object is found in the submap. As >> a result, the internal information of the RutaBasic annotations is lost. >> I does not matter what the analysis engine does as it also happens if it >> is empty, and it happens after the process method is called (The >> RutaBasic annotation is still fine within the process method). I was not >> able to identify the reason why the objects are required to be created >> again. >> >> Can someone can give me a hint where/how I could debug it? >> >> What can influence the table in JCasHashMapSubMap? >> >> >> I can provide more information what I already tried, e.g., it does not >> seem to be a CL problem, but I was not able to create a small >> reproducible example yet. >> >> >> Best, >> >> >> Peter >> >>
