Return-Path: 
 <user-return-6405-apmail-uima-user-archive=uima.apache.org@uima.apache.org>
X-Original-To: apmail-uima-user-archive@www.apache.org
Delivered-To: apmail-uima-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 64797180F8
	for <apmail-uima-user-archive@www.apache.org>;
 Tue, 28 Apr 2015 09:20:32 +0000 (UTC)
Received: (qmail 82001 invoked by uid 500); 28 Apr 2015 09:20:32 -0000
Delivered-To: apmail-uima-user-archive@uima.apache.org
Received: (qmail 81956 invoked by uid 500); 28 Apr 2015 09:20:32 -0000
Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@uima.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@uima.apache.org>
List-Post: <mailto:user@uima.apache.org>
List-Id: <user.uima.apache.org>
Reply-To: user@uima.apache.org
Delivered-To: mailing list user@uima.apache.org
Received: (qmail 81945 invoked by uid 99); 28 Apr 2015 09:20:31 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2015 09:20:31 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: message received from 54.164.171.186
 which is an MX secondary for user@uima.apache.org)
Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2015 09:20:24 +0000
Received: from smtp113.ord1c.emailsrvr.com (smtp113.ord1c.emailsrvr.com
 [108.166.43.113])
	by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with
 ESMTPS id 3E8B64380B
	for <user@uima.apache.org>; Tue, 28 Apr 2015 09:20:04 +0000 (UTC)
Received: from smtp15.relay.ord1c.emailsrvr.com (localhost.localdomain
 [127.0.0.1])
	by smtp15.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 4471738031B;
	Tue, 28 Apr 2015 05:19:41 -0400 (EDT)
Received: by smtp15.relay.ord1c.emailsrvr.com (Authenticated sender:
 reshu.agarwal-AT-orkash.com) with ESMTPSA id BC79D38018B
	for <user@uima.apache.org>; Tue, 28 Apr 2015 05:19:40 -0400 (EDT)
X-Sender-Id: reshu.agarwal@orkash.com
Received: from [192.168.0.117] ([UNAVAILABLE]. [14.141.49.198])
	(using TLSv1.2 with cipher DHE-RSA-AES128-SHA)
	by 0.0.0.0:465 (trex/5.4.2);
	Tue, 28 Apr 2015 09:19:41 GMT
Message-ID: <553F50F4.2090708@orkash.com>
Date: Tue, 28 Apr 2015 14:50:52 +0530
From: "reshu.agarwal" <reshu.agarwal@orkash.com>
Organization: Orkash Services Pvt Ltd
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: user@uima.apache.org
Subject: DUCC- process_dd
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

I was trying to scale my processing pipeline to be run in DUCC 
environment with uima as process_dd. If I was trying to scale using the 
below given configuration, the threads started were not as expected:


<analysisEngineDeploymentDescription
         xmlns="http://uima.apache.org/resourceSpecifier">

         <name>Uima v3 Deployment Descripter</name>
         <description>Deploys Uima v3 Aggregate AE using the Advanced 
Fixed Flow
                 Controller</description>

         <deployment protocol="jms" provider="activemq">
                 <casPool numberOfCASes="5" />
                 <service>
                         <inputQueue endpoint="UIMA_Queue_test" 
brokerURL="tcp://localhost:61617?jms.useCompression=true" prefetch="0" />
                         <topDescriptor>
                                 <import 
location="../Uima_v3_test/desc/orkash/ae/aggregate/FlowController_Uima.xml" 
/>
                         </topDescriptor>
                         <analysisEngine async="true" 
key="FlowControllerAgg" internalReplyQueueScaleout="10" 
inputQueueScaleout="10">
                                 <scaleout numberOfInstances="5"/>
                                 <delegates>
                                         <analysisEngine 
key="ChunkerDescriptor">
                                                 <scaleout 
numberOfInstances="5" />
                                         </analysisEngine>
                                         <analysisEngine key="NEDescriptor">
                                                 <scaleout 
numberOfInstances="5" />
                                         </analysisEngine>
                                         <analysisEngine 
key="StemmerDescriptor">
                                                 <scaleout 
numberOfInstances="5" />
                                         </analysisEngine>
                                         <analysisEngine 
key="ConsumerDescriptor">
                                                 <scaleout 
numberOfInstances="5" />
                                         </analysisEngine>
                                 </delegates>
                         </analysisEngine>
                 </service>
         </deployment>

</analysisEngineDeploymentDescription>


There should be 5 threads of FlowControllerAgg where each thread will 
have 5 more threads of each 
ChunkerDescriptor,NEDescriptor,StemmerDescriptor and ConsumerDescriptor.

But I didn't think it is actually happening in case of DUCC.

Thanks in advance.

Reshu.