> *To:* Martin Eppel (meppel)
> *Cc:* dev@stratos.apache.org; Lasindu Charith (lasi...@wso2.com); Ryan Du
> Plessis (rdupless)
> *Subject:* Re: Testing Stratos 4.1: Application undeployment: application
> fails to undeploy (nested grouping, group scaling)
>
>
>
> Hi Martin,
&g
om:* Reka Thirunavukkarasu [mailto:r...@wso2.com]
> *Sent:* Monday, June 22, 2015 7:30 AM
> *To:* Martin Eppel (meppel)
> *Cc:* dev@stratos.apache.org; Lasindu Charith (lasi...@wso2.com); Ryan Du
> Plessis (rdupless)
>
> *Subject:* Re: Testing Stratos 4.1: Application undeployment: a
Plessis
(rdupless)
Subject: Re: Testing Stratos 4.1: Application undeployment: application fails
to undeploy (nested grouping, group scaling)
Hi Martin,
I have verified the fix by enabling read.write.lock.monitor.enabled=true. The
fix worked fine with it. Since we are using concurrency and
>>
>>>
>>> commit 58bea52be814269416f70391fef50859aa5ae0a1
>>>
>>> Author: lasinducharith
>>>
>>> Date: Fri Jun 19 19:40:27 2015 +0530
>>>
>>>
>>>
>>> *From:* Martin Eppel (meppel)
>>> *Sent:* Sunday
yed,
>>
>> “s-g-c1-c2-c3: applicationInstances 0, groupInstances 0, clusterInstances
>> 0, members 0 ()”
>>
>>
>>
>>
>>
>> Thanks
>>
>>
>>
>>
>>
>> Martin
>>
>>
>>
>>
>>
>&
June 21, 2015 10:28 AM
> *To:* dev@stratos.apache.org; Reka Thirunavukkarasu
> *Cc:* Lasindu Charith (lasi...@wso2.com); Ryan Du Plessis (rdupless)
> *Subject:* RE: Testing Stratos 4.1: Application undeployment: application
> fails to undeploy (nested grouping, group scaling)
>
>
>
: Lasindu Charith (lasi...@wso2.com); Ryan Du Plessis (rdupless)
Subject: RE: Testing Stratos 4.1: Application undeployment: application fails
to undeploy (nested grouping, group scaling)
Hi Reka,
Here is another example which fails, see application at [1.], attached log
files and jsons. I run a
Imesh Gunaratne [mailto:im...@apache.org]
> *Sent:* Sunday, June 21, 2015 1:32 AM
> *To:* Reka Thirunavukkarasu
> *Cc:* dev; Lasindu Charith (lasi...@wso2.com); Ryan Du Plessis (rdupless)
>
> *Subject:* Re: Testing Stratos 4.1: Application undeployment: application
> fails to undeploy
>
>
>
>
>
>
>
>
>
>
>
>
>
> *From:* Imesh Gunaratne [mailto:im...@apache.org]
> *Sent:* Sunday, June 21, 2015 1:32 AM
> *To:* Reka Thirunavukkarasu
> *Cc:* dev; Lasindu Charith (lasi...@wso2.com); Ryan Du Plessis (rdupless)
>
> *Subject:*
;>>
>>>
>>> Thanks
>>>
>>>
>>>
>>> Martin
>>>
>>>
>>>
>>> *From:* Imesh Gunaratne [mailto:im...@apache.org]
>>> *Sent:* Saturday, June 20, 2015 7:29 PM
>>> *To:* dev
>>> *Cc:* Lasi
ious email that would be
>> great,
>>
>>
>>
>> Thanks
>>
>>
>>
>> Martin
>>
>>
>>
>> *From:* Imesh Gunaratne [mailto:im...@apache.org]
>> *Sent:* Saturday, June 20, 2015 7:29 PM
>> *To:* dev
>> *Cc:* Lasin
ndu Charith (lasi...@wso2.com); Reka Thirunavukkarasu (
> r...@wso2.com); Ryan Du Plessis (rdupless)
> *Subject:* Re: Testing Stratos 4.1: Application undeployment: application
> fails to undeploy (nested grouping, group scaling)
>
>
>
> Hi All,
>
>
>
> I'm so
(lasi...@wso2.com); Reka Thirunavukkarasu (r...@wso2.com);
Ryan Du Plessis (rdupless)
Subject: Re: Testing Stratos 4.1: Application undeployment: application fails
to undeploy (nested grouping, group scaling)
Hi All,
I'm sorry I could not follow the entire discussion.
Can someone explai
Hi All,
I'm sorry I could not follow the entire discussion.
Can someone explain the latest status please? Have we resolved the initial
group scaling issue and now seeing an application removal problem?
Thanks
On Sat, Jun 20, 2015 at 2:06 AM, Martin Eppel (meppel)
wrote:
> Hi Lasindu, Reka,
>
To: dev
Subject: Re: Testing Stratos 4.1: Application undeployment: application fails
to undeploy (nested grouping, group scaling)
Hi Martin,
I also encountered a similar issue with the application un-deployment with PCA
but I guess you are using JCA.
I can see that Anuruddha has done a fix for
> +++--+
>
> | g-sc-G12-1 | g-sc-G12-1 | Deployed |
>
> +--------+----+------+
>
>
>
> ['g-sc-G12-1: applicationInstances 1, groupInstances 2, clusterInstances
> 3, members 0 ()\n&#
log4j.logger.org.apache.stratos.autoscaler.rule.RuleLog=DEBUG
From: Udara Liyanage [mailto:ud...@wso2.com]
Sent: Friday, June 05, 2015 10:00 AM
To: dev
Subject: Re: Testing Stratos 4.1: Application undeployment: application fails
to undeploy (nested grouping, group scaling)
Hi Martin,
Better if you can enable debugs logs for
a Liyanage [mailto:ud...@wso2.com]
>> *Sent:* Thursday, June 04, 2015 11:11 PM
>> *To:* dev
>> *Subject:* Re: Testing Stratos 4.1: Application undeployment:
>> application fails to undeploy (nested grouping, group scaling)
>>
>>
>>
>> Hi,
>>
>>
gt;
>
> Martin
>
>
>
> *From:* Udara Liyanage [mailto:ud...@wso2.com]
> *Sent:* Thursday, June 04, 2015 11:11 PM
> *To:* dev
> *Subject:* Re: Testing Stratos 4.1: Application undeployment: application
> fails to undeploy (nested grouping, group scaling)
>
>
>
> H
: application fails
to undeploy (nested grouping, group scaling)
Hi,
This might be possible if AS did not receive member activated event published
by CC. Is it possible to enable debug logs if this is reproducible.
Or else I can add an INFO logs and commit.
On Fri, Jun 5, 2015 at 9:11 AM
Hi Martin,
I added some info logs in efe67ad99f9fca80d4ba66c01e9b642c57838dc3. Could
you please resend the logs with this change applied?.
I tried to reproduce this issue but was not success full. Could you please
send us debugs logs so we can get a better understanding about the exact
issue.
Ad
Hi,
This might be possible if AS did not receive member activated event
published by CC. Is it possible to enable debug logs if this is
reproducible.
Or else I can add an INFO logs and commit.
On Fri, Jun 5, 2015 at 9:11 AM, Udara Liyanage wrote:
> Hi,
>
>
> For the first issue you have mentio
Hi,
For the first issue you have mentioned, the particular member is activated,
but it is still identified as an obsolete member and is being marked to be
terminated since pending time expired. Does that mean member is still in
Obsolete list even though it is being activated?
//member started
TI
23 matches
Mail list logo
