maxIdleConnectionTimeout is a property from jetty, by default jetty will reset the connection between client and server if jetty detect the connection is idle more than 200 sec, this scenario could happen if the server side need a very long time to process the request, for example we can let serviceImpl class sleep 250 sec to simulate this scenario. If this happen, generally this can cause client to re-send the request, which mess up the conversation between client and server. So users need set bigger maxIdleConnectionTimeout of jetty if their seviceImpl is a long time process.
As this is transport level configuration so this could vary between different transports, tomcat should have similar configuration as it in jetty, but I'm not exactly sure how... －－－－－－－－－－－－－ Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 On 2013-8-2, at 下午5:22, Sergey Beryozkin wrote: > Hi > On 02/08/13 09:57, gowri shankar iyer wrote: >> Hello Sergey, >> >> Thanks for the reply. We have not configured any retry/failover >> behaviour but doubt that cxf has an implicit retry particularly during >> load conditions. I wanted to understand this is because of >> maxIdleConnectionTimeout setting being very high, and if yes why. Can >> you throw some light on this ? >> > Sorry, no idea about 'maxIdleConnectionTimeout' parameter, I don't see it in > the CXF source code, and Google links me to this thread :-). > > But either way I'm not aware of the CXF server itself trying to smartly > manage the pending requests. > > May be you can try and add @UseAsyncRequest annotation ? > Or even go and use CXF Continuations API - I will be documenting it next, I > was asked to do it 1 year ago :-), but with the async invocations support in > CXF it is really now the time to do it > > Sergey >> Thanks >> Gowri Shankar >> >> >> On Fri, Aug 2, 2013 at 2:16 PM, Sergey Beryozkin <[email protected] >> <mailto:[email protected]>> wrote: >> >> I replied twice yesterday, have you seen a pointer to a Failover >> wiki page ? >> >> Re configuring that property in Tomcat: I think you need to manage >> that kind of settings at Tomcat connector levels >> >> Sergey >> >> On 02/08/13 09:34, gowri shankar iyer wrote: >> >> Can someone please help ? >> Gowri Shankar >> >> >> ---------- Forwarded message ---------- >> From: gowri shankar iyer <[email protected] >> <mailto:[email protected]>> >> Date: Thu, Aug 1, 2013 at 12:52 PM >> Subject: cxf client retries service calls >> To: [email protected] <mailto:[email protected]> >> >> >> Hello, >> >> Is there any way that a cxf client retries service calls in a >> load scenario >> ? We have been observing when there is a spike in the website >> traffic by 2x >> the number of service calls zooms by 10x. I googled and found >> out in a >> thread that this could be a reason because of >> "maxIdleConnectionTimeout" >> being very high, is this true ? If yes, can someone explain in >> detail why >> this is the case. >> >> Also please throw some light on how to set max idle timeout in a >> tomcat >> server using spring ? We use <jaxws:endPoint> for configuring >> cxf on the >> server side >> >> Please keep me in the reply since I am not part of the group. >> >> Thanks >> Gowri Shankar >> >> >>
