On 22/06/2011 19:03, adarsh thimmappa wrote:
> Hi All,
>       Can anyone please confirm this is an issue or not. I have visited this
> link....
> http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributeslot
> more times....i feel like nothing left w.r.t going back to this link
> again. If anyone is having configuration which is working for version
> 7.0.14..for this particular issue please share with me.

The default, out of the box configuration works for me with a single
change to use the HTTP NIO connector.

There is no issue here.

You need to do some further investigations to figure out why it isn't
working for you.

Mark

> 
> 
> On Wed, Jun 22, 2011 at 7:13 PM, André Warnier <a...@ice-sa.com> wrote:
> 
>> I don't think that az this stage you should be playing with the socket.*
>> attributes, which refer to the low-level JVM TCP socket, and have quite
>> another meaning and other side-effects.
>>
>> Re-read the description of the "keepAliveTimeout" attribute instead, which
>> does refer to the HTTP protocol level.
>>
>> As a general rule : the default values for the Connector attributes have
>> generally been chosen to be reasonable and fit the most usual use cases.
>>  Only modify them if you have a specific and precise reason to do so, after
>> doing adequate measurements.
>>
>>
>> adarsh thimmappa wrote:
>>
>>> Hi Andre,
>>>         I am using the below Connector tag configuration in the
>>> server.xml.....I am still facing the same problem.
>>>
>>> <Connector  port="80"
>>>                  protocol="org.apache.coyote.**http11.Http11NioProtocol"
>>>                  socket.soKeepAlive="true"
>>>                  socket.soTimeout="3600000"
>>>                  maxKeepAliveRequests="-1"
>>>                  redirectPort="8443" />
>>>
>>>
>>>
>>>
>>>
>>> Thanks,
>>> Adarsh
>>>
>>>
>>>
>>>
>>> On Wed, Jun 22, 2011 at 4:18 PM, André Warnier <a...@ice-sa.com> wrote:
>>>
>>>  adarsh thimmappa wrote:
>>>>
>>>>  Hi All,
>>>>>         I am using Apache Tomcat 7.0 (7.0.14 version) server. I have a
>>>>> requirement such that Once i make a HTTP request, and get back the
>>>>> response,
>>>>> i want to keep that connection alive indefinitely. What is the
>>>>> configuration
>>>>> i need to make on the server side. By default, client uses HTTP/1.1
>>>>> protocol
>>>>> version to make HTTP requests. I know that in HTTP/1.1, the Connection
>>>>> is
>>>>> kept alive by default. I am testing this setup on localhost.
>>>>>
>>>>>
>>>>> *        Any help or suggestions will be appreciated.*
>>>>>
>>>>>  Maybe reading the on-line documentation ?
>>>>>
>>>> http://tomcat.apache.org/****tomcat-7.0-doc/config/http.**<http://tomcat.apache.org/**tomcat-7.0-doc/config/http.**>
>>>> html#Common_Attributes<http://**tomcat.apache.org/tomcat-7.0-**
>>>> doc/config/http.html#Common_**Attributes<http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributes>
>>>>>
>>>>
>>>> keepAliveTimeout
>>>> maxKeepAliveRequests
>>>>
>>>>
>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: 
>>>> users-unsubscribe@tomcat.**apa**che.org<http://apache.org>
>>>> <users-unsubscribe@**tomcat.apache.org<users-unsubscr...@tomcat.apache.org>
>>>>>
>>>>
>>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>>
>>>>
>>>>
>>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: 
>> users-unsubscribe@tomcat.**apache.org<users-unsubscr...@tomcat.apache.org>
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
> 
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to