ResourceInitializationExceptions thrown by a deployed aggregate are only 
partially logged
-----------------------------------------------------------------------------------------

                 Key: UIMA-1731
                 URL: https://issues.apache.org/jira/browse/UIMA-1731
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
            Reporter: Burn Lewis
            Priority: Minor
             Fix For: 2.3AS


When the XcasCollectionReader fails to init because its input directory is 
missing it reports the cause when run in core UIMA, i.e.

Caused by: org.apache.uima.resource.ResourceInitializationException: 
Initialization of annotator class "com.ibm.nlp.readers.XcasCollectionReader" 
failed.  (Descriptor: 
file:/.automount/hlthome01/a/hlthome01/homes/hlthome01.3/burn/workspace/factotem/desc/pipe/readers/XcasCollectionReader.xml)
Caused by: org.apache.uima.resource.ResourceInitializationException: Invalid 
value for parameter "InputDirectory" in component "null" -- directory "xmidata" 
does not exist.

but when deployed under UIMA-AS this detailed exception is missing ... all we 
get is the higher-level cause, e.g.

1/30/10 10:56:15 PM - 3: 
org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl.initializeAnalysisEngine:
 WARNING: org.apache.uima.resource.ResourceInitializationException: 
Initialization of annotator class "com.ibm.nlp.readers.XcasCollectionReader" 
failed.  (Descriptor: 
file:/u/burn/workspace/factotem/desc/pipe/readers/XcasCollectionReader.xml)

Also, the detailed message lists the component as "null" ... the collection 
reader follows the example code and reports the error with:
      throw new ResourceInitializationException(
          ResourceConfigurationException.DIRECTORY_NOT_FOUND,
          new Object[] { PARAM_INPUTDIR, this.getMetaData().getName(), 
directory.getPath() });

How should we retrieve the component name?




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to