On Tue, Jul 31, 2012 at 1:50 PM, Miyuru Wanninayaka <[email protected]> wrote:
> Hi all, > > Reason for this issue is during configuration update, there will be lots > of expensive registry operations will perform by deployment interceptor and > that will cause stuck thread detection to kick in. > > However now all service metadata persistence will happen on file system > and no more expensive registry operations. I have tested ESB tenants with > lots of proxy services and now deployment complete in split seconds. > > I guess that we will not hit this issue anymore with new deployment > interceptor. WDYT? There is no doubt that the persistence impl is now performed really quick because of the way it's designed. In fact, this is something we can market for 3.2.x users who are concerned about the server start up time. So, yes, this isn't there in C4. Cheers, --KasunG > -- > Thanks, > Miyuru > -- *Kasun Gajasinghe* Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>* twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>* *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
