+1 for fixing it. CEP could print the WARN once and then it is better to
clean the in-memory data which contain the reference of the particular non
existent member in the Topology.
Thanks,
Reka
On Fri, Oct 30, 2015 at 12:27 AM, Akila Ravihansa Perera wrote:
> Hi,
>
> I'm seeing the following er
Thanks for the confirmation Gayan. I have checked it in master. I have
verified the intergration test logs in [1] which has created 6 members in a
round-robin manner without any issue. You can check the log as with [2] in
the integration test. I'm not sure whether any particular issue is there
when
Hi Reka,
Is it not commented out in the Stratos 4.1.x branch[1]. That test under the
stratos.application.deployment group. We are running that test in the build.
[1]
https://github.com/apache/stratos/blob/stratos-4.1.x/products/stratos/modules/integration/test-integration/src/test/java/org/apache
I am not quite sure about the logic in partition validator[1]. We may need
to rethink the logic again here.
https://github.com/apache/stratos/blob/stratos-4.1.x/components/org.apache.stratos.cloud.controller/src/main/java/org/apache/stratos/cloud/controller/iaases/ec2/EC2PartitionValidator.java#L5
Hi Akila,
We had a partition round-robin integration test [1]. If that is successful,
then round-robin algo is working fine with partitions. Unfortunately, the
particular logic[2] which verifies the round-robin is commented out. Can
you attach the complete log?
[1]
https://github.com/apache/strat
Hi,
I observed the following stack trace while deploying an application in
Stratos. Here are the steps that I did.
1. Deploy network partition, policies, application.
2. Wait until application is active
3. Undeploy the application.
4. Restart Stratos
5. Deploy the application
At this point follo
Akila created STRATOS-1595:
--
Summary: Invalid partition detected when deploying an application
Key: STRATOS-1595
URL: https://issues.apache.org/jira/browse/STRATOS-1595
Project: Stratos
Issue Type:
Hi,
I'm seeing the following error message in Stratos after undeploying an
application.
Failed to publish member fault event. Member having [member-id]
wso2brs-210-application.wso2brs-210-manager.wso2brs-210-manager.domainf0ff75ce-2f21-4ea9-9b5b-4299d761e64e
does not exist in topology
This is be
Akila created STRATOS-1594:
--
Summary: Failed to publish member fault event... log message is
repeatedly printed
Key: STRATOS-1594
URL: https://issues.apache.org/jira/browse/STRATOS-1594
Project: Stratos
Hi,
I noticed an unexpected behavior when deploying an application with network
partition having multiple partitions on EC2 platform.
1. My network partition as follows;
{
"id": "network-partition-ec2",
"provider": "ec2",
"partitions": [
{
"id": "partition-1",
10 matches
Mail list logo