Return-Path: X-Original-To: apmail-geronimo-user-archive@www.apache.org Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 59D7310935 for ; Fri, 18 Oct 2013 19:29:06 +0000 (UTC) Received: (qmail 19276 invoked by uid 500); 18 Oct 2013 19:29:05 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 18860 invoked by uid 500); 18 Oct 2013 19:29:00 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 18851 invoked by uid 99); 18 Oct 2013 19:28:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2013 19:28:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.215.172] (HELO mail-ea0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2013 19:28:52 +0000 Received: by mail-ea0-f172.google.com with SMTP id r16so2263351ead.17 for ; Fri, 18 Oct 2013 12:28:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=gvQ77nBdmjMbJfwyzsOWiCFYSfKajtddn3N/3YHQTnA=; b=PTieLF/m7sBPC0qAAER3efmQ8ZSdHn7CTTyidEqRpVD1RIxll2MsNQKORrxfTUqdK7 kT72nQBSjvnEHwO55x6rjOh4KkHZPyywWOC1pGvOBHkRWSLC3bEhWsY1CPRXOhZZjR6n 5zncDDr2/1kVjkCv9TRZ+3MKX+92ngJbXxIUDDazCeizhmhVu8a+AaHo+sSqlmxshFF4 Ff6rFoStGUPRtREq8riDR7n50+z9aT+o5aQ7q5iNGxazJm7G5VEGOoM8jp5EjuEu2Vr2 3feR4daM4bSDkwSoABHScaz2mJIWkZN2hxmoyhFOLNhKZ5hRYKeB3l303sVdWCQAH4it lCMA== X-Gm-Message-State: ALoCoQkZx+GKF1MAgW70rUWkXycbAk0meoxTF2qzdYiCAHwo16z91Pi0xpCSSG9/g2hget/7ajAn MIME-Version: 1.0 X-Received: by 10.15.24.68 with SMTP id i44mr5051149eeu.87.1382124511597; Fri, 18 Oct 2013 12:28:31 -0700 (PDT) Received: by 10.14.151.193 with HTTP; Fri, 18 Oct 2013 12:28:31 -0700 (PDT) X-Originating-IP: [213.184.196.114] In-Reply-To: References: Date: Fri, 18 Oct 2013 21:28:31 +0200 Message-ID: Subject: Re: Webservice client - ConnectionPoolTimeoutException: Timeout waiting for connection From: Stig Even Larsen To: user@geronimo.apache.org Content-Type: multipart/alternative; boundary=089e0160c5448ca5a804e908f0fd X-Virus-Checked: Checked by ClamAV on apache.org --089e0160c5448ca5a804e908f0fd Content-Type: text/plain; charset=UTF-8 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 > 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 > >> 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 --089e0160c5448ca5a804e908f0fd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

You might be able to get more a= ccurate answer by this stack trace I hope:

Caused by: org.apache.com= mons.httpclient.ConnectionPoolTimeoutException: Timeout waiting for connect= ion
=C2=A0=C2=A0=C2=A0 at org.apache.commons.httpclient.MultiThreadedHttpConnec= tionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:497)=C2=A0=C2=A0=C2=A0 at org.apache.commons.httpclient.MultiThreadedHttpConne= ctionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.ja= va:416)
=C2=A0=C2=A0=C2=A0 at org.apache.commons.httpclient.HttpMethodDirector.exec= uteMethod(HttpMethodDirector.java:153)
=C2=A0=C2=A0=C2=A0 at org.apache.= commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
=C2=A0= =C2=A0=C2=A0 at org.apache.commons.httpclient.HttpClient.executeMethod(Http= Client.java:346)
=C2=A0=C2=A0=C2=A0 at org.apache.axis2.transport.http.AbstractHTTPSender.ex= ecuteMethod(AbstractHTTPSender.java:560)
=C2=A0=C2=A0=C2=A0 at org.apach= e.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
=C2= =A0=C2=A0=C2=A0 at org.apache.axis2.transport.http.HTTPSender.send(HTTPSend= er.java:76)
=C2=A0=C2=A0=C2=A0 at org.apache.axis2.transport.http.CommonsHTTPTransportS= ender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
=C2= =A0=C2=A0=C2=A0 at org.apache.axis2.transport.http.CommonsHTTPTransportSend= er.invoke(CommonsHTTPTransportSender.java:225)
=C2=A0=C2=A0=C2=A0 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.ja= va:435)
=C2=A0=C2=A0=C2=A0 at org.apache.axis2.description.OutInAxisOper= ationClient.send(OutInAxisOperation.java:402)
=C2=A0=C2=A0=C2=A0 at org.= apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOper= ation.java:229)
=C2=A0=C2=A0=C2=A0 at org.apache.axis2.client.OperationClient.execute(Opera= tionClient.java:165)
=C2=A0=C2=A0=C2=A0 at org.apache.axis2.jaxws.core.c= ontroller.impl.AxisInvocationController.execute(AxisInvocationController.ja= va:554)


Best regards,
Stig Even Larsen


2013/10/17 Ivan <xhhsld@gmail.com>
Hi,

Which classes do you use to con= nect the long running web services ? axis2 client API or jaxws spec API ?
Thanks.


2013/10/15 Stig Even Larsen <sla@priv.biz>
Hi,

I have a problem with webservic= e (JAX-WS and Axis2) requests being rejected by HttpClient (MultiThreadedHt= tpConnectionManager) with the message "Timeout waiting for connection&= quot;.
We are using Geronimo 2.2.1 binary distribution (with Axis 1.5.2)

The system have 2 long running webservices for transferring data t= o a legacy system supporting webservices. We now need to consume several ot= her 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.

<= /div>
My questions are:
1. How do I change the default ma= x connections per host?
2. Is there a way to "isolate" the long running webser= vices so that the new one runs with a different ConnectionManager?
3. Or is there other solutions to this problem?


Best regards,
Stig Even La= rsen
=



--
Ivan



--
Mvh,
Stig Even Larse= n
--089e0160c5448ca5a804e908f0fd--