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
