You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Sajith Kariyawasam (JIRA)" <ji...@apache.org> on 2014/09/30 11:36:34 UTC
[jira] [Resolved] (STRATOS-641) LoadBalancer doesn't keep
super-tenant subscriptions for a multi-tenant service
[ https://issues.apache.org/jira/browse/STRATOS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sajith Kariyawasam resolved STRATOS-641.
----------------------------------------
Resolution: Fixed
Duplicates STRATOS-377
> LoadBalancer doesn't keep super-tenant subscriptions for a multi-tenant service
> -------------------------------------------------------------------------------
>
> Key: STRATOS-641
> URL: https://issues.apache.org/jira/browse/STRATOS-641
> Project: Stratos
> Issue Type: Bug
> Components: Load Balancer
> Affects Versions: 4.0.0
> Reporter: Nirmal Fernando
> Assignee: Imesh Gunaratne
> Fix For: 4.1.0 M1
>
>
> Reason seems to be that since no one creates super tenant, TenantCreatedMessageProcessor event would not send for super tenant. Hence, Stratos LB doesn't treat super tenant as a valid tenant. Example is when a super tenant subscription to a multi-tenant service, Stratos LB logs following [1].
> Fix would be to pre-load the maps in TenantManager, with super-tenant details.
> [1]
> TID: [0] [LB] [2014-04-30 15:56:43,709] WARN {org.apache.stratos.messaging.message.processor.tenant.TenantUnSubscribedMessageProcessor} - Tenant not found: [tenant-id] -1234
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)