[ http://jira.codehaus.org/browse/XFIRE-743?page=comments#action_81235 ] Andres Bernasconi commented on XFIRE-743: -----------------------------------------
Actually, I think that the best number of connections is equal to the number of ExecutionThreads (this is how BEA calls 'workers' that process requests). I do the same thing for jdbc connections, because getting a new connection is expensive, and I don't want anybody waiting to be able to work on one. This is specially true with web services, which tend to take longer than jdbc calls. So if I configure my App Serv. with 50 'worker threads' I would set HttpClient to max 50 connections. (again, if it is REALLY unlikely that you could get all worker threads to execute the same web service at the same time, I would probably lower it). By the way, will there be any way to configure these parameters (and all others that can be configure) through Spring ?. I really like the fact that I don't have to write a single line of Java Code to get XFire running... so setting all these options from spring could be really useful. My 2 cents. Regards, AB > HttpClient only does 2 connections by default > --------------------------------------------- > > Key: XFIRE-743 > URL: http://jira.codehaus.org/browse/XFIRE-743 > Project: XFire > Issue Type: Bug > Reporter: Dan Diephouse > Assigned To: Tomasz Sztelak > Fix For: 1.2.3 > > > the multithreaded connection manager only opens two threads by default in the > http connection manager. This can cause a major bottleneck for multithreaded > applications. We should bump this up and make it configurable more easily. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
