Return-Path: X-Original-To: apmail-stratos-dev-archive@minotaur.apache.org Delivered-To: apmail-stratos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3BA9617ABC for ; Mon, 4 May 2015 17:13:06 +0000 (UTC) Received: (qmail 37232 invoked by uid 500); 4 May 2015 17:13:06 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 37164 invoked by uid 500); 4 May 2015 17:13:06 -0000 Mailing-List: contact dev-help@stratos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stratos.apache.org Delivered-To: mailing list dev@stratos.apache.org Received: (qmail 37153 invoked by uid 99); 4 May 2015 17:13:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2015 17:13:05 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: message received from 54.76.25.247 which is an MX secondary for dev@stratos.apache.org) Received: from [54.76.25.247] (HELO mx1-eu-west.apache.org) (54.76.25.247) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2015 17:12:39 +0000 Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com [209.85.220.178]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id ACE592540A for ; Mon, 4 May 2015 17:12:37 +0000 (UTC) Received: by qkhg7 with SMTP id g7so89145418qkh.2 for ; Mon, 04 May 2015 10:11:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=+HUGtQVL2QTj0ph+exJvPA90A0TojdAWmNF16s6gPKU=; b=PBPJ19i9o9SE/DpODnYwgciQr5xTj1Lla4VIindv1YJqMxurmR7+wdZr4nwQnKBJSY 7FyfW3DSFHIxovzv01ZPyhD97++zKdI4/AV795f4LyHiOA9orph1t3nm18pjy5jZ6giG PgEU9aw6GP0N4N9L1w/wwdPfZTVqSpiczNR1o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=+HUGtQVL2QTj0ph+exJvPA90A0TojdAWmNF16s6gPKU=; b=PDrdg+Zj0WgELTSxjwOyyZxXAl3i9ozh39z4XS3CvXn9eOwIGa/pFsyHQPFPCDtPG5 l/Zb2Ljo9uow2XKGH0x46TlT61/R5Al+TM6R6sHeNVzT8YRg+/7xJnBOY2pPC0zjT/yk kVuiCQk9cgg198+h06mDB5xtaLoKcQbGfoJEgxvxQszlFg1vznudNEUqpNDVOreVNqbz Yu1OgFOoT6QEGiR1j8aSL3P3pMjHKfqLVUNaXoO0e1DbsY2WKfdlC8ve5rphbpOjIV7k bP86qAQLZLKu4HBbrrd+bSgVIhYNyoV8D8dlIWnzGrGf8XK9gJZNMF2yiki6p2siQ33c wdpA== X-Gm-Message-State: ALoCoQluRiWhL046yCuyGu4K3pTMbDxIkIrRvDYuw91gPB6TezzUEzweCI7vdCiFQzUTiWmmxoyQ X-Received: by 10.55.21.211 with SMTP id 80mr46968822qkv.100.1430759511662; Mon, 04 May 2015 10:11:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.36.196 with HTTP; Mon, 4 May 2015 10:11:31 -0700 (PDT) In-Reply-To: <07110D8A7AC60C49AE2432100017A3F6289B223E@xmb-rcd-x12.cisco.com> References: <07110D8A7AC60C49AE2432100017A3F62899E878@xmb-rcd-x12.cisco.com> <07110D8A7AC60C49AE2432100017A3F6289A2C3F@xmb-rcd-x12.cisco.com> <07110D8A7AC60C49AE2432100017A3F6289B1BD3@xmb-rcd-x12.cisco.com> <07110D8A7AC60C49AE2432100017A3F6289B223E@xmb-rcd-x12.cisco.com> From: Reka Thirunavukkarasu Date: Mon, 4 May 2015 22:41:31 +0530 Message-ID: Subject: Re: Testing stratos 4.1 - nested grouping fails to deploy with unequal cartridge types ? To: dev Content-Type: multipart/alternative; boundary=001a11473dce73b5e4051544a847 X-Virus-Checked: Checked by ClamAV on apache.org --001a11473dce73b5e4051544a847 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Martin, I have replied in the earlier thread. Hope you got it.. Thanks, Reka On Mon, May 4, 2015 at 10:22 PM, Martin Eppel (meppel) wrote: > Resending it in case you missed it, > > > > Thanks > > > > Martin > > > > *From:* Martin Eppel (meppel) > *Sent:* Sunday, May 03, 2015 4:31 PM > *To:* dev@stratos.apache.org > *Subject:* RE: Testing stratos 4.1 - nested grouping fails to deploy with > unequal cartridge types ? > > > > Hi Reka, > > > > Can you please confirm, as you stated in the email below applicationId an= d > group alias cannot have the same string. > > But that following example =E2=80=93 see snippet of application.json - , = with > =E2=80=9CapplicationId=E2=80=9D, =E2=80=9Capplication name=E2=80=9D and= =E2=80=9Cgroup name=E2=80=9D the same but =E2=80=9Cgroup > alias=E2=80=9D different should be working ok ? > > > > Btw, I am not clear why we have this restriction, application and group > should be different objects, so why do =E2=80=9CapplicationId=E2=80=9D an= d =E2=80=9Cgroup alias=E2=80=9D > have to be different ? > > Are we using a flat string search to identify objects ? > > > > Thanks > > > > Martin > > > > Snippet of application json: > > > > { > > "alias": "s-n-gr-s-G12-t-a-2", > > "applicationId": "s-n-gr-s-G12-t-a-2", > > "components": { > > "cartridges": [], > > "groups": [ > > { > > "name": "s-n-gr-s-G12-t-a-2", > > "groupMaxInstances": 1, > > "groupMinInstances": 1, > > "alias": "s-n-gr-s-G12-t-a-2*-x0x*", > > "cartridges": [ > > { > > > > *From:* Reka Thirunavukkarasu [mailto:reka@wso2.com ] > *Sent:* Friday, April 24, 2015 1:57 AM > *To:* dev > *Subject:* Re: Testing stratos 4.1 - nested grouping fails to deploy with > unequal cartridge types ? > > > > Hi Martin, > > Found the issue. It was an issue with your application definition. You > were using same Id for applicationId and the blower group alias. So in th= is > specific case GroupMonitor and ApplicationMonitor got messed up with this > configuration. Please note that it would be better to use GroupName also = a > unique value as to avoid confusion in case if the same group used by > multiple application. Please see the configuration below as your one: > > { > "alias": "subscription-G1-G2-G3", > "applicationId": "subscription-G1-G2-G3", > "components": { > "cartridges": [], > "groups": [ > { > "name": "subscription-G1-G2-G3", > "groupMaxInstances": 1, > "groupMinInstances": 1, > "alias": "subscription-G1-G2-G3", > "cartridges": [], > "groups": [ > > After i changed it to below configuration, your sample worked fine as > attached the UI Topology. > > { > "alias": "subscription-G1-G2-G3-G4", > "applicationId": "subscription-G1-G2-G3-G4", > "components": { > "cartridges": [], > "groups": [ > { > "name": "subscription-G1-G2-G3", > "groupMaxInstances": 1, > "groupMinInstances": 1, > "alias": "subscription-G1-G2-G3", > "cartridges": [], > "groups": [ > > Hope this will help you. Will check further whether we need to do the > validation. Then we can find such issues in the application addition itse= lf. > > Thanks, > > Reka > > > > > > On Fri, Apr 24, 2015 at 1:22 PM, Reka Thirunavukkarasu > wrote: > > Hi Martin, > > I didn't encounter such issue, since i constructed a similar sample > referring your one, it worked fine for me. I will check with exactly your > sample and update how it goes. > > Thanks, > > Reka > > > > > > On Fri, Apr 24, 2015 at 5:33 AM, Martin Eppel (meppel) > wrote: > > Hi Reka, > > > > I verified the fix and it is working, however while testing the scenario = I > noticed a different issue: > > > > When the application is subscribed the very first time after starting up > stratos, only 3 of the 4 cartridge actually spawn an instance (which all > become active). However, If I subsequently remove the application (withou= t > restarting stratos) and re-subscribe again all 4 cartridges spin up an > instance. > > > > I attached the log file which has both scenarios (1st subscription of the > app and 2nd one) plus the cartridge groups and application json. > > > > WDYT, is it a configuration error or a possible bug ? > > > > Thanks > > > > Martin > > > > *From:* Reka Thirunavukkarasu [mailto:reka@wso2.com] > *Sent:* Thursday, April 23, 2015 1:08 AM > *To:* dev > *Subject:* Re: Testing stratos 4.1 - nested grouping fails to deploy with > unequal cartridge types ? > > > > Hi Martin, > > Identified the bug and fixed it in > 2065d7a167b00bbca0a5efe9a1a178521b3bda8a. Please verify it and update the > thread. > > Thanks, > > Reka > > > > On Thu, Apr 23, 2015 at 11:42 AM, Reka Thirunavukkarasu > wrote: > > Hi Martin, > > I'm looking into this issue..I have tried a similar sample as your one an= d > got the issue reproduced in the local setup. It seems to be a bug in our > application parser. Will work on further on this and update the thread.. > > Thanks, > > Reka > > > > On Thu, Apr 23, 2015 at 10:32 AM, Imesh Gunaratne > wrote: > > Hi Martin, > > > > Thanks for reporting this problem, we will have a look at this and get > back to you soon. > > > > Thanks > > > > On Thu, Apr 23, 2015 at 5:27 AM, Martin Eppel (meppel) > wrote: > > Hi, > > > > I think I am seeing an issue with nested grouping: > > > > When I define a parent group (no cartridges) and 2 nested children groups= , > each containing cartridges with a different types I see an exception that= a > cartridge group is not defined in the parent group : > > > > TID: [0] [STRATOS] [2015-04-22 20:46:58,495] ERROR > {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} - Cartridge c3 > not defined in cartridge group: [application] subscription-G1-G2-G3 > [cartridge-group-name] subscription-G1-G2-G3 [cartridge-group-alias] > subscription-G1-G2-G3 > > java.lang.RuntimeException: Cartridge c3 not defined in cartridge group: > [application] subscription-G1-G2-G3 [cartridge-group-name] > subscription-G1-G2-G3 [cartridge-group-alias] subscription-G1-G2-G3 > > at > org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParse= r.validateCartridgeGroupReference(DefaultApplicationParser.java:590) > > at > org.apache.stratos.autoscaler.applications.parser.DefaultApplicationParse= r.parseGroups(DefaultApplicationParser.java:569) > > > > If I define the same cartridge types in both children groups the > application deploys fine (e.g. replace cartridge type c3 / c4 with c1 / c= 2 > in group =E2=80=9Cmultiple-groups-no-startup-G2=E2=80=9D, see =E2=80=A6= =E2=80=9Dworking=E2=80=9D=E2=80=A6. Artifacts) > > > > I attached wso2carbon.log / cartridge-group.json and application.json > files and all the other artifacts to the email. > > > > Also attached the artifacts (cartridge-group / application) and wso2carbo= n > log for the working case (see =E2=80=A6=E2=80=9Cworking=E2=80=9D=E2=80=A6= ) for comparison > > > > I created a JIRA for this issue: > https://issues.apache.org/jira/browse/STRATOS-1339 > > > > Thanks > > > > Martin > > > > > > -- > > Imesh Gunaratne > > > > Technical Lead, WSO2 > > Committer & PMC Member, Apache Stratos > > > > -- > > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > > Mobile: +94776442007 > > > > > > > -- > > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > > Mobile: +94776442007 > > > > > > > -- > > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > > Mobile: +94776442007 > > > > > > > -- > > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > > Mobile: +94776442007 > > > --=20 Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007 --001a11473dce73b5e4051544a847 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Martin,

I have replied in t= he earlier thread. Hope you got it..

Thanks,
Reka
=

On Mon, May= 4, 2015 at 10:22 PM, Martin Eppel (meppel) <meppel@cisco.com> wrote:

Resending it in case you = missed it,

=C2=A0

Thanks

=C2=A0

Martin

=C2=A0

From: Martin E= ppel (meppel)
Sent: Sunday, May 03, 2015 4:31 PM
To: dev@= stratos.apache.org
Subject: RE: Testing stratos 4.1 - nested grouping fails to deploy w= ith unequal cartridge types ?

=C2=A0

Hi Reka,

=C2=A0

Can you please confirm, a= s you stated in the email below applicationId and group alias cannot have t= he same string.

But that following exampl= e =E2=80=93 see snippet of application.json - , with =C2=A0=E2=80=9Capplica= tionId=E2=80=9D, =E2=80=9Capplication name=E2=80=9D=C2=A0 and =E2=80=9Cgrou= p name=E2=80=9D the same but =E2=80=9Cgroup alias=E2=80=9D different =C2=A0should be working ok ?

=C2=A0

Btw, I am not clear why w= e have this restriction, application and group should be different objects,= so why do =E2=80=9CapplicationId=E2=80=9D and =E2=80=9Cgroup alias=E2=80= =9D have to be different ?

Are we using a flat strin= g search to identify objects =C2=A0?

=C2=A0

Thanks

=C2=A0

Martin

=C2=A0

Snippet of application js= on:

=C2=A0

{

=C2=A0 "alias": "s-n-gr-s-G12-t-a-2&q= uot;,

=C2=A0 "applicationId&qu= ot;: "s-n-gr-s-G12-t-a-2",

=C2=A0 "components&q= uot;: {

=C2=A0=C2=A0=C2=A0 "= cartridges": [],

=C2=A0=C2=A0=C2=A0 "= groups": [

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 {

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 "name": "s-n-gr-s-G12-t-a-2&qu= ot;,

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 "groupMaxInstances": 1,

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 "groupMinInstances": 1,

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 "alias": "s-n-gr-s-G12-t-a-2-x0x",

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 "cartridges": [

=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 {

=C2=A0

From: Reka Thi= runavukkarasu [mailto:re= ka@wso2.com]
Sent: Friday, April 24, 2015 1:57 AM
To: dev
Subject: Re: Testing stratos 4.1 - nested grouping fails to deploy w= ith unequal cartridge types ?

=C2=A0

Hi Martin,<= /u>

Found the issue. It w= as an issue with your application definition. You were using same Id for ap= plicationId and the blower group alias. So in this specific case GroupMonit= or and ApplicationMonitor got messed up with this configuration. Please note that it would be better to use Gro= upName also a unique value as to avoid confusion in case if the same group = used by multiple application. Please see the configuration below as your on= e:

{
=C2=A0=C2=A0=C2=A0 "alias": "s= ubscription-G1-G2-G3",
=C2=A0=C2=A0=C2=A0 "applicationId": "subscription-G1-G2-G3",
=C2=A0=C2=A0=C2=A0 "components": {
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "cartridges": [],
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "groups": [
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 {
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "name": "subsc= ription-G1-G2-G3",
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "groupMaxInstances": 1,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "groupMinInstances": 1,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "alias": "subs= cription-G1-G2-G3",
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "cartridges": [],
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "groups": [

After i changed it to= below configuration, your sample worked fine as attached the UI Topology.<= br>
{
=C2=A0=C2=A0=C2=A0 "alias": "s= ubscription-G1-G2-G3-G4",
=C2=A0=C2=A0=C2=A0 "applicationId": "subscription-G1-G2-G3-G4",
=C2=A0=C2=A0=C2=A0 "components": {
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "cartridges": [],
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "groups": [
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 {
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "name": "subsc= ription-G1-G2-G3",
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "groupMaxInstances": 1,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "groupMinInstances": 1,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "alias": "subs= cription-G1-G2-G3",
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "cartridges": [],
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 "groups": [

Hope this will help y= ou. Will check further whether we need to do the validation. Then we can fi= nd such issues in the application addition itself.

Thanks,

Reka

=C2=A0

=C2=A0

On Fri, Apr 24, 2015 at 1:22 PM, Reka Thirunavukkara= su <reka@wso2.com= > wrote:

Hi Martin,<= /u>

I didn't encounte= r such issue, since i constructed a similar sample referring your one, it w= orked fine for me. I will check with exactly your sample and update how it = goes.

Thanks,

Reka

=C2=A0

=C2=A0

On Fri, Apr 24, 2015 at 5:33 AM, Martin Eppel (meppe= l) <meppel@cisco.c= om> wrote:

Hi Reka,

=C2=A0

I verified the fix and it= is working, however while testing the scenario I noticed a different issue= :

=C2=A0

When the application is s= ubscribed the very first time after starting up stratos, only 3 of the 4 cartridge actually spawn an instance (which all become active). However, I= f I subsequently remove the application (without restarting stratos) and re= -subscribe again all 4 cartridges spin up an instance.

=C2=A0

I attached the log file w= hich has both scenarios (1st subscription of the app and 2n= d one) plus the cartridge groups and application json. =

=C2=A0

WDYT, is it a configurati= on error or a possible bug ?

=C2=A0

Thanks

=C2=A0

Martin

=C2=A0

From: Reka Thi= runavukkarasu [mailto:re= ka@wso2.com]
Sent: Thursday, April 23, 2015 1:08 AM
To: dev
Subject: Re: Testing stratos 4.1 - nested grouping fails to deploy w= ith unequal cartridge types ?

=C2=A0

Hi Martin,<= /u>

Identified the bug an= d fixed it in 2065d7a167b00bbca0a5efe9a1a178521b3bda8a. Please verify it an= d update the thread.

Thanks,

Reka

=C2=A0

On Thu, Apr 23, 2015 at 11:42 AM, Reka Thirunavukkar= asu <reka@wso2.com> wrote:

Hi Martin,<= /u>

I'm looking into = this issue..I have tried a similar sample as your one and got the issue rep= roduced in the local setup. It seems to be a bug in our application parser.= Will work on further on this and update the thread..

Thanks,

Reka

=C2=A0

On Thu, Apr 23, 2015 at 10:32 AM, Imesh Gunaratne &l= t;imesh@apache.org> wrote:

Hi Martin,

=C2=A0

Thanks for reporting this problem, we will have a lo= ok at this and get back to you soon.

=C2=A0

Thanks

=C2=A0

On Thu, Apr 23, 2015 at 5:27 AM, Martin Eppel (meppe= l) <meppel@cisco.c= om> wrote:

Hi,

=C2=A0

I think I am seeing an issue with nested grouping:

=C2=A0

When I define a parent group (no cartridges) and 2 n= ested children groups, each containing cartridges with a different types I = see an exception that a cartridge group is not defined in the parent =C2=A0group :

=C2=A0

TID: [0] [STRATOS] [2015-04-22 20:46:58,495] ERROR {= org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -=C2=A0 Cartridge = c3 not defined in cartridge group: [application] subscription-G1-G2-G3 [cartridge-group-name] subscription-G1-G2-G3 [cartridge-group-alias] subsc= ription-G1-G2-G3

java.lang.RuntimeException: Cartridge c3 not defined= in cartridge group: [application] subscription-G1-G2-G3 [cartridge-group-n= ame] subscription-G1-G2-G3 [cartridge-group-alias] subscription-G1-G2-G3

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 at org.apache.stratos.autoscaler.applicat= ions.parser.DefaultApplicationParser.validateCartridgeGroupReference(Defaul= tApplicationParser.java:590)

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 at org.apache.stratos.autoscaler.applicat= ions.parser.DefaultApplicationParser.parseGroups(DefaultApplicationParser.j= ava:569)

=C2=A0

If I define the same cartridge types in both childre= n groups the application deploys fine (e.g. replace cartridge type c3 / c4 = with c1 / c2 in group =E2=80=9Cmultiple-groups-no-startup-G2=E2=80=9D, see =E2=80=A6=E2=80=9Dworking=E2=80=9D=E2=80=A6. Artifacts)<= /p>

=C2=A0

I attached wso2carbon.log / cartridge-group.json and= application.json files and all the other artifacts =C2=A0to the email.<= /u>

=C2=A0

Also attached the artifacts (cartridge-group / appli= cation) and wso2carbon log for the working case (see =E2=80=A6=E2=80=9Cwork= ing=E2=80=9D=E2=80=A6 ) for comparison

=C2=A0

I created a JIRA for this issue: https://issues.apache.org/jira/browse/STRATOS-1339<= /p>

=C2=A0

Thanks

=C2=A0

Martin



=C2=A0

--

Imesh Gunaratne=

=C2=A0

Techn= ical Lead, WSO2

Commi= tter & PMC Member, Apache Stratos



--

Reka Thirunavukkarasu<= br> Senior Software Engineer,
WSO2, Inc.:http://wso2.com,

Mobile: +94776442007=

=C2=A0




--

Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,

Mobile: +94776442007=

=C2=A0<= /p>




--

Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,

Mobile: +94776442007

=C2=A0<= /p>




--

Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,

Mobile: +94776442007

=C2=A0<= /p>




--
Reka Thirunavukkarasu
Senior Software Engi= neer,
WSO2, Inc.:http://ws= o2.com,
Mobile: +94776442007


--001a11473dce73b5e4051544a847--