I am not aware of any resource leaks in uimaFIT or UIMA-J either. Maybe Solr doesn't handle resources in the way you expect? E.g. queries or documents may have to be closed/returned when they are no longer needed. You could to generate a heap dump using JVisualVM to figure our what kind of objects are accumulating.
Cheers, -- Richard > On 08.08.2016, at 09:22, armin.weg...@bka.bund.de wrote: > > Hello Richard! > > No, I can't change the reader. It's reading from Solr. The response documents > are put in a queue. The querying logic is done in hasNext(). hasNext() > returns true if the queue is not empty. If the queue is empty, hasNext() > sends a request to Solr and puts the response documents in the empty queue. > If there are no more response documents from Solr, the queue remains empty > and the reader is done. getNext() pulls a document from the queue and sets > the CAS's document text. The number of documents returned from Solr can be > given as a parameter. Currently it's set to 1, that is one document per > request. The only fields of the reader class are the parameters and the > document queue. All other variables are local to their methods. It's pretty > simple. There shouldn't be any resource leaks. > > Best, > Armin > > -----Ursprüngliche Nachricht----- > Von: Richard Eckart de Castilho [mailto:r...@apache.org] > Gesendet: Montag, 8. August 2016 08:50 > An: user@uima.apache.org > Betreff: Re: CPE memory usage > > Did you try using a different reader? > > Cheers, > > -- Richard > >> On 08.08.2016, at 08:10, <armin.weg...@bka.bund.de> >> <armin.weg...@bka.bund.de> wrote: >> >> Hi! >> >> I'm using uimaFIT 2.2.0 and uimaj 2.8.1. The collectection processing engine >> is slowy eating up all memory until it gets killed by the system. This >> happens even when I'm just runnging a collection reader and no other >> compoments (no analysis at all). Does anyone has experiented a similar >> behavior or has any ideas? >> >> Best, >> Armin >
