[ 
https://issues.apache.org/jira/browse/UIMA-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568749#action_12568749
 ] 

Marshall Schor commented on UIMA-780:
-------------------------------------

The CDE calls the framework code to "validate" the descriptor before saving it. 
 The framework validation code calls produceAnalysisEngine, with a flag 
indicating that this call is for validation purposes only.

The framework code goes so far as to actually load the class, but because the 
validation flag is on, it doesn't make an "instance" of it.  

Just loading the class, however, runs the class's "static" initializers.  If 
these initializers take a lot of resources, then that would explain what's 
happening.  Do you know if that is the case?   If so, is it possible to move 
the initialization to the "initialize" call, instead of doing it at "load" time?



> CDE hangs when processing AEs with very high initialization time (adding the 
> AE to the aggregate or saving the descriptor)
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-780
>                 URL: https://issues.apache.org/jira/browse/UIMA-780
>             Project: UIMA
>          Issue Type: Bug
>          Components: Eclipse plugins
>    Affects Versions: 2.2
>         Environment: Debian Linux
>            Reporter: Jennifer Chu-Carroll
>            Priority: Minor
>
> The CDE repeatedly hung when trying to add an AE with high initialization 
> time into the aggregate. When I finally successfully added it through editing 
> the source xml, it hung again while trying to save the descriptor. It appears 
> that the CDE is trying to initialize the annotator (CPU usage 200+%, using 
> 5.7G of memory). I verified this by having the annotator in question load a 
> toy dictionary and the problem disappeared.

-- 
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