Before deciding on this, I would like to know, how and when these
subscriptions are used.
At the start, ADC component loads all the subscriptions. Then what happens?
Who else is making use of this info (AFAIK LB does)?
On Mon, Aug 11, 2014 at 7:48 PM, Isuru Haththotuwa
wrote:
> Hi,
>
> Yes, cu
+1 for first approach. This is inline with the tenant level isolation
Lakmal suggested recently in another thread.
Touched, not typed. Erroneous words are a feature, not a typo.
On Aug 12, 2014 8:40 AM, "Nirmal Fernando" wrote:
>
>
>
> On Mon, Aug 11, 2014 at 7:48 PM, Isuru Haththotuwa
> wrot
On Mon, Aug 11, 2014 at 7:48 PM, Isuru Haththotuwa
wrote:
> Hi,
>
> Yes, currently Stratos Manager loads all Subcriptions at startup, and I
> agree this is not a very good practice. To improve this, I can think of two
> methods:
>
> 1. write each tenant's Subscriptions to tenant's own registry, a
On Mon, Aug 11, 2014 at 7:48 PM, Isuru Haththotuwa
wrote:
> Hi,
>
> Yes, currently Stratos Manager loads all Subcriptions at startup, and I
> agree this is not a very good practice. To improve this, I can think of two
> methods:
>
> 1. write each tenant's Subscriptions to tenant's own registry, a
Hi,
Yes, currently Stratos Manager loads all Subcriptions at startup, and I
agree this is not a very good practice. To improve this, I can think of two
methods:
1. write each tenant's Subscriptions to tenant's own registry, and then
load them to memory model when the tenant is loading. This infor
Hi all,
Recently we were observing a delay when SM is starting in our stratos
setup. See the following log segment. It seems ADCManagement component
takes a lot of time (in this case 3 minutes).
TID: [0] [SCC] [2014-08-11 06:49:39,850] INFO
{org.apache.stratos.messaging.message.receiver.topology
