Hi, The configuration you used is for CXF http-jetty, but not for standalone jetty.
The jetty configuration should be like <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting// DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd";> <Configure class="org.eclipse.jetty.server.Server"> <!-- =========================================================== --> <!-- Set connectors --> <!-- =========================================================== --> <!-- One of each type! --> <!-- =========================================================== --> <!-- Use this connector for many frequently idle connections and for threadless continuations. --> <Call name="addConnector"> <Arg> <New class="org.eclipse.jetty.server.nio.SelectChannelConnector"> <Set name="host"><Property name="jetty.host" /></Set> <Set name="port"><Property name="jetty.port" default="8181"/></Set> <Set name="maxIdleTime">300000</Set> <Set name="Acceptors">2</Set> <Set name="statsOn">false</Set> <Set name="confidentialPort">8443</Set> <Set name="lowResourcesConnections">20000</Set> <Set name="lowResourcesMaxIdleTime">5000</Set> </New> </Arg> </Call> </Configure> －－－－－－－－－－－－－ 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-4-2, at 下午9:08, Julio Carlos Barrera Juez wrote: > Hi! > > We have an application developed on top of ServiceMix 4.4.1. We are > experiencing a kind of timeout in my CXF REST Web Services. After exactly > 200 seconds, in a long processing task, WS server closes the connection > opened by a REST client with a FIN TCP packet adn the client resend the > message. It produces bad behaviours in the server, because both messages > are processed. We are thinking on developing asynchronous WS, but during > this process we need to develop a patch to this issue to avoid double calls. > > We use CXF and dOSGI to develop our REST API using javax.ws.* annotations. > We have tried to configure 'maxIdleTime' property of Jetty connector > creating a Jetty configuration file in $SERVICEMIX_HOME/etc/jetty.xml with > this contents: > > <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:beans=" > http://www.springframework.org/schema/beans"; xmlns:xsi=" > http://www.w3.org/2001/XMLSchema-instance"; xmlns:sec=" > http://cxf.apache.org/configuration/security"; xmlns:http=" > http://cxf.apache.org/transports/http/configuration"; xmlns:httpj=" > http://cxf.apache.org/transports/http-jetty/configuration"; xmlns:jaxws=" > http://java.sun.com/xml/ns/jaxws"; xsi:schemaLocation=" > http://cxf.apache.org/configuration/security > http://cxf.apache.org/schemas/configuration/security.xsd > http://cxf.apache.org/transports/http/configuration > http://cxf.apache.org/schemas/configuration/http-conf.xsd > http://cxf.apache.org/transports/http-jetty/configuration > http://cxf.apache.org/schemas/configuration/http-jetty.xsd > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans-2.0.xsd";> > > <httpj:engine-factory bus="cxf"> > <httpj:engine port="9001"> > <httpj:connector> > <beans:bean > class="org.eclipse.jetty.server.nio.SelectChannelConnector"> > <beans:property name="maxIdleTime" > value="10000" /> > </beans:bean> > </httpj:connector> > </httpj:engine> > </httpj:engine-factory> > </beans> > > We expect that the timeout was set to 10 seconds (instead of 200, only for > testing purposes), but it still was 200 seconds. > > How can we configure this property?
