Hi,
You might be able to get more accurate answer by this stack trace I hope:
Caused by: org.apache.commons.httpclient.ConnectionPoolTimeoutException:
Timeout waiting for connection
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:497)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:416)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:153)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:560)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at
org.apache.axis2.jaxws.core.controller.impl.AxisInvocationController.execute(AxisInvocationController.java:554)
Best regards,
Stig Even Larsen
2013/10/17 Ivan <xhh...@gmail.com>
> 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 <s...@priv.biz>
>
>> 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
