Have you taken a look at at http://wso2.org/project/wsas/java/2.2.1/docs/wsas-clustering.html?

Azeez

Hubert, Eric wrote:
Hi all,

today we tried a simple test regarding load balancing with clusteraware
stickiness (session affinity) which did not work (this is related to
JIRA https://wso2.org/jira/browse/ESBJAVA-439).

Before I try to reopen that JIRA or create a new one linked to that, I
would like to ask a few questions about clustering configuration. Where
can I find information about how to properly configure clustering.

I found nothing in the WSO2-land, only a page within the Axis2
documentation, which seems to fit but does not explain the details:
http://ws.apache.org/axis2/1_3/clustering-guide.html#stateful%20Web%20Se
rvices

What shall I do to activate clustering support for WSO2 ESB? Is it
sufficient to uncomment the configuration section about clustering in
Axis2.xml of all nodes? This is what we actually did.

How does clustering work internally? I could not see any multicast
configuration or something like that.
According to the comments in the JIRA our configuration should work, as
we use named endpoints. Please find attached our synapse configuration
file.

If we don't miss any configuration step, I will open a new JIRA issue.
Please let me know how to proceed with this!

Regards,
   Eric





------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>
<syn:definitions xmlns:syn="http://ws.apache.org/ns/synapse";>
    <syn:registry provider="org.wso2.esb.registry.ESBRegistry">
        <syn:parameter name="root">file:registry/</syn:parameter>
        <syn:parameter name="cachableDuration">15000</syn:parameter>
    </syn:registry>
    <syn:proxy name="LocalLoadBalance" startOnLoad="true">
        <syn:target inSequence="main" outSequence="main"/>
    </syn:proxy>
    <syn:endpoint name="HelloWS_THIRD">
        <syn:address uri="http://10.35.29.213:9001/WSTEST3/HelloWorldService"/>
    </syn:endpoint>
    <syn:endpoint name="HelloWS_FIRST">
        <syn:address uri="http://10.35.29.213:9001/WSTest/HelloWorldService"; 
statistics="enable"/>
    </syn:endpoint>
    <syn:endpoint name="HelloWS_SECOND">
        <syn:address uri="http://10.35.29.213:9001/WSTEST2/HelloWorldService"/>
    </syn:endpoint>
    <syn:sequence name="main" onError="errorHandler">
        <syn:in>
            <syn:send>
                <syn:endpoint name="root">
                    <syn:loadbalance policy="roundRobin">
                        <syn:endpoint key="HelloWS_FIRST"/>
                        <syn:endpoint key="HelloWS_SECOND"/>
                        <syn:endpoint key="HelloWS_THIRD"/>
                    </syn:loadbalance>
                </syn:endpoint>
            </syn:send>
            <syn:drop/>
        </syn:in>
        <syn:out>
            <syn:send/>
        </syn:out>
    </syn:sequence>
    <syn:sequence name="fault">
        <syn:log level="full">
            <syn:property name="MESSAGE" value="Executing default &quot;fault&quot; 
sequence"/>
            <syn:property name="ERROR_CODE" 
expression="get-property('ERROR_CODE')"/>
            <syn:property name="ERROR_MESSAGE" 
expression="get-property('ERROR_MESSAGE')"/>
        </syn:log>
        <syn:drop/>
    </syn:sequence>
    <syn:sequence name="errorHandler">
        <syn:makefault>
            <syn:code xmlns:tns="http://www.w3.org/2003/05/soap-envelope"; 
value="tns:Receiver"/>
            <syn:reason value="COULDN'T SEND THE MESSAGE TO THE SERVER."/>
        </syn:makefault>
        <syn:header name="To" action="remove"/>
        <syn:property name="RESPONSE" value="true"/>
        <syn:send/>
    </syn:sequence>
</syn:definitions>


------------------------------------------------------------------------

_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user


_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Reply via email to