Hi Asankha, we have the following case: A business partner provides a portlet for us that's running inside our portal server. This portlet connects to the business partner's backend system using Hessian over HTTP. Both - portlet and backend - are outside our development influence.
We repeatedly had problems in the case that the partner's backend dropped out or got slow: The portlet opens more and more connections to its backend that get stale immediately. This problem extends until the portal server system cannot open any more connections and drops down too. So a single application harms the availability of the entire portal. It is no solution to configure short request timeout values, because there are some requests that take a longer time (up to minutes) under normal circumstances. In order to overcome this, we are thinking of placing some kind of shield between the portlet and the backend. One idea is to place an esb in the middle and limit the size of connections to and from the esb. Having some good experience with synapse, we are wondering if synapse could manage this. Hope that brings some clarification on the requirement. Thank you and best regards, Ralph Henze. Von: "Asankha C. Perera" <[email protected]> An: [email protected] Datum: 03.02.2010 17:52 Betreff: Re: Limit the size of http connection pools Gesendet von: Asankha Perera <[email protected]> Hello Ralph > is there a possibility to limit the size of http connection pools in > synapse > > - for incoming connections from consumers ? > - for outgoing connections to EPRs ? > Could you let me know why you want to change these - so that I can better understand your requirement thanks asankha -- Asankha C. Perera AdroitLogic, http://adroitlogic.org http://esbmagic.blogspot.com
