Paul, > One question: What is the CPU count on the client when this is happening? It is a machine using a Intel Core 2 Duo 6600 @2.4 GHz.
> Please try adding [0] at the end of the XPath expression. I'm not sure > if this will make a difference, but it might. The whole message should > not be parsed, just the headers. Oh, that sounds good. How does the implementation know/decide whether it has to parse the whole message or just the header? I will try if the [0] will change anything and report back. > As regards clustering, you should be able to use ESB with any IP > spraying or load-balancing technique, e.g. hardware load-balancer, LVS, > etc. We have put some work into sharing state across a cluster for > throttling and caching. We also have done some work on hot-update across > a cluster - basically you "gracefully shutdown" each server in turn, > with the result that no requests are lost, and the load balancer > redirects work to the rest of the cluster. "Gracefully shutdown"? I hope you mean "gracefully restart" each server...? ;-) Is this also part of 1.6, or only the cluster support for caching and throttling. Are there any infos on the implementation? Do you use something like jgroups for intercluster communication? Clusterwide caching and throttling sounds very interesting. I would love to play with this options after I have finished the basic stuff. > As regards writing asynchronously to a database, I'm sure we can come up > with a mediator that does that - maybe we spawn a worker thread at > startup that writes to the DB from a queue and the mediator writes to > the queue. Based on your tests so far, I don't think this kind of > database writer will affect your performance much. That sounds to be a good idea. So you at least would have a default implementation without external dependencies. Regards, Eric _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
