Adding dev@
On Fri, Sep 20, 2013 at 2:04 AM, Darshana Gunawardana <[email protected]>wrote: > Hi all, > > I have worked on some recent issues on APIM which thought to be caching > issues in permissions. When i try to isolate the issue, i suspects that > this is more general problem of the usage of caching in APIM distributed > deployment. > > "To work distributed caching, nodes (which intended to share caches) > needed to be in same cluster." > > Based on above fact, the problem is how it gonna facilitate APIM > distributed setup where store/publisher needed to sync information about > API resources. > > For an example if we add a new API on publisher it not gonna display on > store, if the store already has cached information on APIs and publisher > has no way to tell to store the cache is out-dated. Here simple registry > caching on store and publisher cause the issue and there can be many > several scenarios like this. > > The above scenario works as expected on following cases, > - Waiting for a 15 mins which is caching timeout > - Restarting the server > - Adding store & publisher to a same cluster. > > Maybe i'm missing some obvious thing here? If so please sorted me out. If > not how does in earlier versions manage this? I believe this not a > Hazelcast specific scenario. > > Thanks > > -- > Regards, > > * > Darshana Gunawardana > *Software Engineer > WSO2 Inc.; http://wso2.com* > E-mail: [email protected] > **Mobile: +94718566859 > *Lean . Enterprise . Middleware > -- Regards, * Darshana Gunawardana *Software Engineer WSO2 Inc.; http://wso2.com* E-mail: [email protected] **Mobile: +94718566859 *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
