You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by cganesan <ch...@hp.com> on 2013/04/30 19:31:24 UTC
Automatic retry of HTTP Request upon Socket error
Hi
I came across this link https://issues.apache.org/jira/browse/CXF-2036
<https://issues.apache.org/jira/browse/CXF-2036>
while trying to find solution to a vexing problem with Socket exceptions.
The CXF 2.2.7 client (WebClient) throws socket exception upon HTTP request
to server (also using CXF Version 2.2.7). Server is configured optimally
using server.xml params. Since the exceptions are not frequent and not
related to server timeout/response, I'd like to explore the option of
retrying the request upon socket error.
My question here is, can I use the Conduit element to configure retries?
Since I don't see this retry property documented in the conduit element
configuration I'd like to confirm if it works with CXF 2.2.7 Conduit
element?
Appreciate your help on this.
Thanks
Chandru
--
View this message in context: http://cxf.547215.n5.nabble.com/Automatic-retry-of-HTTP-Request-upon-Socket-error-tp5726984.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Automatic retry of HTTP Request upon Socket error
Posted by Sergey Beryozkin <sb...@gmail.com>.
On 01/05/13 16:11, cganesan wrote:
> For the upgrade test, would it suffice to upgrade to CXF 2.4.2 from 2.2.7 or
> do you recommend a specific version?
>
Well, I don't know what the cause of the issue is, at the moment we are
just trying to narrow the problem, right ? Upgrading to the newer CXF is
one of the steps, but is also recommended on its own, FYI, CXF 2.5.10 is
the oldest supported CXF version, and I guess there will be at most
another one CXF 2.5.x release, may be two. Ideally, try CXF 2.6.7, if
not possible - CXF 2.5.10, and if that is tricky too, then the latest
CXF 2.4.x (I think it is CXF 2.4.10)
Sergey
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Automatic-retry-of-HTTP-Request-upon-Socket-error-tp5726984p5727010.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
Re: Automatic retry of HTTP Request upon Socket error
Posted by cganesan <ch...@hp.com>.
For the upgrade test, would it suffice to upgrade to CXF 2.4.2 from 2.2.7 or
do you recommend a specific version?
--
View this message in context: http://cxf.547215.n5.nabble.com/Automatic-retry-of-HTTP-Request-upon-Socket-error-tp5726984p5727010.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Automatic retry of HTTP Request upon Socket error
Posted by Sergey Beryozkin <sb...@gmail.com>.
On 01/05/13 15:20, cganesan wrote:
> Thanks Sergey. I'm using tomcat container ver 6.0.35 (from VMWare)
>
Then lets try to do the following, for the purpose of a test:
- avoid customizing its server.xml
- if that does not help, replace that with the basic Apache Tomcat
6.0.35, and
- finally, upgrade to the newer CXF
Cheers, Sergey
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Automatic-retry-of-HTTP-Request-upon-Socket-error-tp5726984p5727007.html
> Sent from the cxf-user mailing list archive at Nabble.com.
Re: Automatic retry of HTTP Request upon Socket error
Posted by cganesan <ch...@hp.com>.
Thanks Sergey. I'm using tomcat container ver 6.0.35 (from VMWare)
--
View this message in context: http://cxf.547215.n5.nabble.com/Automatic-retry-of-HTTP-Request-upon-Socket-error-tp5726984p5727007.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Automatic retry of HTTP Request upon Socket error
Posted by Sergey Beryozkin <sb...@gmail.com>.
I don't think we can configure HttpConduit do it - if it were possible then
it would probably lead to 'hiding' the issues like the ones you are seeing
with CXF 2.2.7. As suggested in the other emails, try upgrading to the newer
CXF.
The other question: do you use a standalone Jetty container (you refer to
server.xml, so probably yes) ? Can it be something to do with the way it is
configured ? Assuming it is a standalone Jetty container, please try
narrowing down the problem as follows, after upgrading to the newer CXF :-),
:
- remove the configuration completely and see if the issue persists
- update to the newer Jetty and see if the issue persists
Let us know how it goes please
Sergey
--
View this message in context: http://cxf.547215.n5.nabble.com/Automatic-retry-of-HTTP-Request-upon-Socket-error-tp5726984p5726999.html
Sent from the cxf-user mailing list archive at Nabble.com.