Hi Akila,

Please check the modified code. It now takes the value which is specified
as localMemberPort in axis2.xml.

Thanks,

On Tuesday, July 5, 2016, Akila Ravihansa Perera <raviha...@wso2.com> wrote:

> Hi Osura,
>
> As Isuru mentioned you need to be clear about tenantId since it might
> conflict with Carbon tenantId. As suggested, please rename it to something
> like AZURE_TENANT_ID or something like that.
>
> Regarding localMemberPort in axis2.xml, the value of this parameter should
> be same in all nodes by convention therefore no need read localMemberPort
> parameter value in each member's axis2.xml. When adding members to
> Hazelcast config context you need to take the value of this parameter.
> Because we cannot guarantee that it will be 4000 in every deployment. There
> are some special cases in which we need to change this. Have a look at [1]
> to see how this is handled in Mesos membership scheme.
>
> [1]
> https://github.com/wso2/mesos-artifacts/blob/master/common/mesos-membership-scheme/src/main/java/org/wso2/carbon/clustering/mesos/MesosMembershipScheme.java#L247
>
> Thanks.
>


-- 
Regards,
Osura Rathnayake
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to