1.4 standalone with tomcat. This is where the "problem" is. Hmmm...the "functioning" ones are using jetty. Most or maybe even all of them...
-----Ursprüngliche Nachricht----- Von: ant elder [mailto:[email protected]] Gesendet: Donnerstag, 10. Dezember 2009 11:31 An: [email protected] Betreff: Re: Limit of connections On Thu, Dec 10, 2009 at 10:01 AM, Apostolos Papageorgiou <[email protected]> wrote: > Hello! > > > > I am performing load tests with soapUI on web services that are provided by > Tuscany components. > > > > I am testing with different applications on different platforms and there is > only one case where my service does not accept more than 10 connections. > > I have often been using much more than 10 soapUI threads (virtual clients) > and they can always connect, all of them. > > Only with this particular service/application, 10 threads make it and all > the rest are rejected and they terminate later with a > SocketTimeoutException. > > I have not configured such a setting ("up to 10 connections allowed") and I > don't have a clue why this happens with this service. > > > > Can anybody think of something? > > > > Thanks in advance, > > Apostolos Before digging in the code could you say which version of Tuscany that is and if you're using the webapp runtime or standalone one, and if its the standalone one if its using Jetty or Tomcat (ie you've got tuscany-host-jetty or tuscany-host-tomcat jars on the classpath)? ...ant
