<HTML dir=ltr><HEAD><TITLE>Re: [esb-java-user] Loadbalancing with clusteraware stickiness(session affinity)</TITLE> <META http-equiv=Content-Type content="text/html; charset=unicode"> <META content="MSHTML 6.00.6000.16640" name=GENERATOR></HEAD> <BODY> <DIV id=idOWAReplyText94215 dir=ltr> <DIV dir=ltr> <DIV dir=ltr>Hi Azeez,</DIV> <DIV dir=ltr> </DIV> <DIV dir=ltr>yes, many thanks also from my side! Now this looks as expected and is more or less fully self explaning. :-)</DIV> <DIV dir=ltr>Did you have to change the code in the Axis2 clustering module to read these parameters from the config or were they just missing in the axis2.xml?</DIV> <DIV dir=ltr>I'm afraid that the first applies. I then would further guess that this change went to Axis2 trunk, as Axis2 1.4 is already out of the door. </DIV> <DIV dir=ltr>I would love to see this change in the Synapse 1.2/WSO2 ESB 1.7 version. The only way to achieve this would be a patch local to synapse, right? Hopefully the change in Axis2 only affects a single class which reads and sets the properties. Then at least this simple and straightforward backward possibility would allow for a simple patch. If all the assumptions above apply I would like to call for your vote for such a patch. Without having the possibility to configure these setting I'm quite sure that we won't get the ESB in our production environment with activated clustering (which we need for clustering and throttling). </DIV> <DIV dir=ltr>My apologies that I didn't notice this earlier. I was to sure that there is a way to configure this.</DIV> <DIV dir=ltr> </DIV> <DIV dir=ltr> </DIV> <DIV dir=ltr>Regards,</DIV> <DIV dir=ltr>   Eric</DIV></DIV></DIV> <DIV dir=ltr> <HR tabIndex=-1> Von: Paul Fremantle [mailto:paul@wso2.com] Gesendet: So 11.05.2008 09:27 An: esb-java-user@wso2.org Cc: Hubert, Eric Betreff: Re: [esb-java-user] Loadbalancing with clusteraware stickiness(session affinity) </DIV> <DIV> Azeez Thanks!! This makes it much clearer. Paul Afkham Azeez wrote: > 1. The default multicast address used is 228.0.0.4 > 2. The default multicast port is 45564 > 3. The default multicast frequency is 500ms > 4. You can have multiple cluster groups using the same multicast address > and port. In this case, you will need to specify unique domains. > 5. The TCP port listening for replication messages is the first > available server socket in range 4000-4100 > 6. You can have your HTTP/S, TCP etc. transports bound to one NW > interface and use a different interface to handle clustering messages. > > I have added more parameters in the cluster configuration section of the > axis2.xml file. > > <parameter name="multicastAddress">228.0.0.4</parameter> > <parameter name="multicastPort">45564</parameter> > <parameter name="multicastFrequency">500</parameter> > <parameter name="multicastMemberDropTime">3000</parameter> > > <parameter name="tcpListenHost">127.0.0.1</parameter> > <parameter name="tcpListenPort">4000</parameter> > > multicastAddress & multicastPort are used for membership management > through multicasts. > tcpListenHost & tcpListenPort are the parameters used for specifying the > IP and port used for member-to-member communications. > > HTH > Azeez > > Hubert, Eric wrote: >> Hello Azees, >> >> thanks for your reply which answers some of our questions. Please see my >> comments below! >> >>> Please see <A href="http://wso2.org/project/wsas/java/2.2.1/docs/wsas-">http://wso2.org/project/wsas/java/2.2.1/docs/wsas-</A> >>> clustering.html >> Thanks, I will review this documentation as well. >> >>  >>>> 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. >>>> >>> Generally this is sufficient provided that multicasting is enabled on >>> your network. >> Ok, multicasting was enabled on our test environment. We also used the >> same environment for a clustered JMS test with JBoss using JGroups. >> >> >>>> How does clustering work internally? I could not see any multicast >>>> configuration or something like that. >> >>> You do not have to configure the multicast address. Tribes will figure >> it >>> out. In order to have multiple groups, you need to provide different >>> "domain" entries in the axis2.xml file for the nodes belonging to the >>> different groups. >> Sorry, but I don't understand how an implementation can figure out the >> multicast address/port I have to use? In a production environment we >> can't use random or framework specific values. We are forced to >> configure the values we get assigned by the operations team. >> >> >> >>> When it comes to sending messages to the cluster, TCP connections are >>> used. >> Which port(s) will be used for that communication? >> >>  >>> The NW interface to which the clustered node should be bound to can be >>> provided by specifying the "axis2.local.ip.address" System property. >>> e.g. if you have two interfaces with IPs 192.168.1.23 & 192.168.1.50, >>> and want to bind the node to the first interface, you can point the >>> axis2.local.ip.address system property to 192.168.1.23. There is >> another >>> way the same thing can be achieved; edit the /etc/hosts file and point >>> the entry with you machines name to the required IP address. >> The second option will not work for us. We have no influence on that. >> Does this affect the whole binding, or only the multicast binding? Maybe >> I would like to bind the normal http listener to more than one IP >> address but handle the multicast traffic over a specific interface. How >> to achieve this? >> >> >>>> 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! >> So it seems as if we didn't miss any configuration in order to get our >> example working. As proposed we will wait for the new snapshot build >> from the release branch to test this again, before we will raise an >> issue on that. >> Regards, >>    Eric >> > > > _______________________________________________ > Esb-java-user mailing list > Esb-java-user@wso2.org > <A href="http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user">http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user</A> > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: <A href="http://pzf.fremantle.org/">http://pzf.fremantle.org</A> paul@wso2.com "Oxygenating the Web Service Platform", www.wso2.com </DIV></BODY></HTML>