Hubert, Eric wrote:
Hi Azeez,
yes, many thanks also from my side! Now this looks as expected and is
more or less fully self explaning. :-)
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?
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.
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.
The only class that needed to be changed in Axis2 is
TribesClusterManager. The only changes were to feed in the new
parameters to the membership service. We have a mechanism to include
patches with minimal changes. So we can include this class as a patch.
The patch will go through a full testing cycle. We will start thoroughly
testing this on Monday.
Then at least this simple and straightforward
backward possibility would allow for a simple patch.
Yes, the patch simply needs to be dropped into the patches directory in
the lib folder.
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).
My apologies that I didn't notice this earlier. I was to sure that there
is a way to configure this.
Regards,
Eric
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
