On Sun, Aug 8, 2010 at 8:21 PM, Kasun Indrasiri <[email protected]> wrote:
> So, as per the suggestions, I have set the fail-safe mode as the default > mode of the ESB(should disable in production env).Also, we can select the > required fail-safe level (i.e. endpoints, proxyservices or both) through the > synapse.properties file. > > eg. > #(enabled by default) > #failsafe.mode.enable=endpoints > failsafe.mode.enable=proxyservices > #failsafe.mode.enable=disable > The settings does not look right to me: Should it not be something like... failsafe.mode.enable=[true/false] # defaults to true > > If we don't have any concerns over this, then we can add this capability to > 3.0.1. > > Thanks. > Kasun > > > On Tue, Aug 3, 2010 at 11:54 AM, Supun Kamburugamuva <[email protected]>wrote: > >> On Tue, Aug 3, 2010 at 7:22 AM, Prabath Siriwardana <[email protected]> >> wrote: >> > >> > >> > On Tue, Aug 3, 2010 at 6:31 AM, Samisa Abeysinghe <[email protected]> >> wrote: >> >> >> >> >> >> On Tue, Aug 3, 2010 at 4:44 AM, Sanjiva Weerawarana <[email protected]> >> >> wrote: >> >>> >> >>> If you're going to intro a param for this I suggest that the default >> be >> >>> to have it ON - which means ignore proxy errors at startup. Maybe a >> >>> production environment may not want that but for dev you certainly do. >> >>> Keeping it off by default will lead to continued user confusion and >> >>> frustration. Turning it off can be part of our production config >> >>> guidelines. >> >> >> >> +1. >> >> Also, can we do something about the default suspend behaviour along >> with >> >> this? The default suspend behavior is very annoying at times. I think >> we >> >> should flip the current defaults to the other end. >> > >> > >> > +1 >> >> Set the default time out to 30 secs in the Synapse trunk. We should do >> this for the 3.0.1 release as well. Actually we had this discussion in >> Synapse dev. >> >> Thanks, >> Supun.. >> >> >> > >> > Thanks & regards. >> > -Prabath >> > >> >>> >> >>> They key is that a proxy service setup needs to be transactional- all >> or >> >>> nothing. Either it starts and all is well or there must be no trace of >> it in >> >>> the system. Having it up with a missing security policy for example >> could be >> >>> quite bad :). >> >>> Sanjiva. >> >>> >> >>> On Mon, Aug 2, 2010 at 10:43 PM, Kasun Indrasiri <[email protected]> >> wrote: >> >>>> >> >>>> Hi folks, >> >>>> In ESB 2.x/3.x, if a proxy service is failed during the >> >>>> creation/deployment, then the ESB cannot be started. This prevents, >> an user >> >>>> from accessing the Management Console and only way to restore the >> system is >> >>>> to edit the configuration that resides in the files system(3.x). In a >> >>>> scenario where we have several proxy services (+ other sequences >> etc), the >> >>>> system becomes crappy, even if one proxy is failed during the >> startup. >> >>>> So, introducing a configuration parameter to switch on/off fail-safe >> >>>> mode for proxy services would be a better way of handling these >> issues. (We >> >>>> have a similar approach for enabling fail-safe mode for publishing >> WSDLs). >> >>>> A given proxy service may fail in two different stages. >> >>>> Deployment-time failures >> >>>> - We have the complete configuration for the proxy service but >> it >> >>>> failed when we are deploying it. >> >>>> - e.g. Missing security policy etc. >> >>>> - Axis2SynapseController - deployProxyServices() >> >>>> - ProxyService -buildAxisService(..) // hot deployment >> >>>> Creation-time failures >> >>>> - The proxy service's configuration cannot be built. >> >>>> - e.g. WSDL based proxies with unavailable wsdls >> >>>> - A proxy service configuration may get created when we are >> >>>> starting the ESB. >> >>>> - MultiXMLConfigurationBuilder - createProxyServices(..) >> >>>> >> >>>> I have locally did the required changes to address failures in above >> >>>> stages and tested it.(We can add a new property to synapse.properties >> >>>> (enableFailsafeProxyServices) and use it to check whether fail-safe >> mode is >> >>>> switch on or not.) >> >>>> However, I have some doubts over handling 'Proxy service >> creation-time >> >>>> failures'. If we are going to handle such scenarios, then we also >> have to >> >>>> handle cases like WSDL Endpoints failures. Do we really want to >> handle this? >> >>>> WDYT? >> >>>> >> >>>> Thanks. >> >>>> Kasun >> >>>> >> >>>> -- >> >>>> Kasun Indrasiri >> >>>> Senior Software Engineer >> >>>> WSO2, Inc.; http://wso2.com >> >>>> lean.enterprise.middleware >> >>>> >> >>>> cell: +94 71 536 4128 >> >>>> Blog : http://kasunpanorama.blogspot.com/ >> >>>> >> >>>> _______________________________________________ >> >>>> Carbon-dev mailing list >> >>>> [email protected] >> >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> Sanjiva Weerawarana, Ph.D. >> >>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >> >>> email: [email protected]; phone: +1 408 754 7388 x51726; cell: +94 77 >> 787 >> >>> 6880 | +1 650 265 8311 >> >>> blog: http://sanjiva.weerawarana.org/ >> >>> >> >>> Lean . Enterprise . Middleware >> >>> >> >>> _______________________________________________ >> >>> Carbon-dev mailing list >> >>> [email protected] >> >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >>> >> >> Thanks, >> >> Samisa... >> >> >> >> Samisa Abeysinghe >> >> VP Engineering >> >> >> >> WSO2 Inc. >> >> http://wso2.com >> >> http://wso2.org >> >> >> >> >> >> >> >> _______________________________________________ >> >> Carbon-dev mailing list >> >> [email protected] >> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> >> > >> > >> > >> > -- >> > Thanks & Regards, >> > Prabath Siriwardena >> > >> > http://blog.facilelogin.com >> > http://RampartFAQ.com >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > [email protected] >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > Kasun Indrasiri > Senior Software Engineer > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 71 536 4128 > Blog : http://kasunpanorama.blogspot.com/ > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
