Hi Hiranya, Charitha found this issue [1] which is related to syncing proxy service configurations. Here's the root cause for this..
* When security is applied for the proxy service in the RW node, it updates the proxy.xml file and also the meta file * Deployment Synchronizer syncs the proxy.xml to RO node * RO node hot-updates the proxy.xml and in the process it touches the meta file * When DS tries to sync the meta file, a conflict occurs because node2 has already touched it This doesn't happen for AAR services because the original .aar file never get changed when configurations are changed through the UI. So only the meta file will be updated and synced. We have to come up with a proper solution for this. Thanks, ~Isuru [1] https://wso2.org/jira/browse/CARBON-13070 -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : [email protected] blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
