Hi, yes UIMA-AS service has multiple async consumers. The GetMeta consumer
responds to clients asking for service metadata.
The Process consumer handles client's process requests (invoking processing
pipelines). And the Target consumer enables clients to
target specific service instance.These consumers are independently scaled
and configured in a deployment descriptor.
Each consumer segments messages it wants to receive from a common queue
using JMS Selector. Both Process and GetMeta requests
support error handling which can also be defined in the deployment
descriptor. The service uses Spring JMS default listener to ingest JMS
messages from a service queue. The general flow of messages is a follows:
Listener > InputChannel > MessageHandler > Controller > AnalysisEngine >
OutputChannel
Currently, there is no documentation about UIMA-AS internals.
The general documentation for UIMA, UIMA-AS and DUCC are here:
https://uima.apache.org/documentation.html
-Jerry
On Mon, Feb 4, 2019 at 5:27 PM armin dadras
wrote:
> Hey there,
> We are currently looking into ActiveMQ and what the Broker does when we
> start a service instance. UIMA seems to start three consumers for each
> instance, and we don't really get behind what each of them is doing. We
> have a few questions: -in which UIMA class can we look up the function of
> those three consumers / where they are created
> -is it possible to regulate consumer regarding recourses used on them,
> does this even make sense or is it allready optimized
> -do you have generell documentation about the dataflow/architecture of
> UIMA/Ducc when processing data? Like the single steps during communication
> with ActiveMQ?
> Thank in advancceFlorian and Armin
>
>
>
>
