Hi Ivan, I could also add that the webservice is created in Netbeans by referencing the wsdl file. Therefore, I'm a little uncertain answering your question, but to my knowledge it is Axis2 implementation of JAX-WS that is in use. Hopefully the stack trace in my previous post could answer your question better.
Looking forward to resolv this puzzle. Best regards, Stig 2013/10/17 Ivan <[email protected]> > Hi, > > Which classes do you use to connect the long running web services ? axis2 > client API or jaxws spec API ? > > Thanks. > > > 2013/10/15 Stig Even Larsen <[email protected]> > >> Hi, >> >> I have a problem with webservice (JAX-WS and Axis2) requests being >> rejected by HttpClient (MultiThreadedHttpConnectionManager) with the >> message "Timeout waiting for connection". >> We are using Geronimo 2.2.1 binary distribution (with Axis 1.5.2) >> >> The system have 2 long running webservices for transferring data to a >> legacy system supporting webservices. We now need to consume several other >> webservices from the same host, but is running into problems because of the >> the default max connections per host being 2. >> >> After searching for several days I don't find a solution to my problem, >> so I reach out to you to hopefully be enlightened. >> >> My questions are: >> 1. How do I change the default max connections per host? >> 2. Is there a way to "isolate" the long running webservices so that the >> new one runs with a different ConnectionManager? >> 3. Or is there other solutions to this problem? >> >> >> Best regards, >> Stig Even Larsen >> > > > > -- > Ivan > -- Mvh, Stig Even Larsen
