Hi Rajith, I think sample 200 (synapse_sample_200.xml), 201 and 205 will help you. Sample 201 is just failover sending. So if we are using Axis2 clustering with that we can keep only one node as the primary at a time. We don't have to worry about concurrent access issues, but it's only for high availability (not for scalability).
Sample 200 is state less load balancing. So either there should be no sessions or all nodes have to be clustered with considering the concurrent access issues. Sample 205 would be the best fit. It binds failover groups to http sessions. So we have cluster the nodes in failover groups using the primary backup model. Although the loadbalancing implementation supports service group ID based sessions, there is an issue in Axis2 ( https://issues.apache.org/jira/browse/AXIS2-2404), which prevents soap sessions from passing through Synapse. Therefore I didn't include a sample with the soap session. Once this issue is resolved, setting <session type="soap"/> would enable soap sessions. Regards, Chathura
