Marshall Schor wrote:
The documentation for this has been posted to the Apache UIMA wiki.
I read the documentation of UIMA JMS and would like to ask a few
questions about it:
1) Do you have any experiences with the memory footprint when using UIMA
AS? It seems to me that when deploying a larger system with multiple AEs
a lot of queues are used. Each AS aggregate use a queue for the
delegates. How is the performance with all these queues? Do you have any
measurements?
2) Collection Process complete - The documentation says: "If a component
is replicated, only one of the instances will receive the
collectionProcessComplete call". I think replicated mean there is more
than von instance of the same component. So why does only one of the
components receive that call? Is that given by design that only one, and
we don't know which of the component receive the information? I think is
is the same as with a CAS, right?
3) When the system processes a document without any CasMultiplier the
process call for this document blocks until the result is created and
returned? So in the system only one CAS is created and used. If the
system has also CasMultiplier components the CasPool size for a
CasMultiplier component can limit the CASes that can be used/created at
the same time. But how does this work if the system collects the
documents itself? The the call blocked as long as all the documents are
processed?
4) The error handling seems to be similar as in the CPM with some
additional new features (real retry). Is there some reuse of the old code?
5) UIMA AS does not have a StatusListener that can/must be implemented
to get some information about the system. How are the results reposted
in the good case? I understand that in an error case, the error with
some additional background information is returned.
Thanks
-- Michael
