> From: adarsh thimmappa [mailto:adarsh.tm...@gmail.com]
> Subject: Re: Apache Tomcat 7.0.14
> I observed that the TCP connection suddenly disappears after
> the response is sent.
Connections don't "suddenly disappear" - someone (possibly the client) closes
it. Aga
Hi Mark,
I would be sorry if that was aggressive. I was testing the NIO
connector and was monitoring the TCP connections between the client(Here the
client is Apache MINA based) and the tomcat server(tomcat 7.0.14) through
the tool (CurrPorts v1.91 - Monitoring Opened TCP/IP network ports
Ok..Thanks.
On Thu, Jun 23, 2011 at 3:02 AM, Mark Thomas wrote:
> You really need to read
> http://www.catb.org/~esr/faqs/smart-questions.html before folks here
> just start ignoring your messages.
>
> On 22/06/2011 20:59, adarsh thimmappa wrote:
> > Hi All,
> > In the entire source file of
You really need to read
http://www.catb.org/~esr/faqs/smart-questions.html before folks here
just start ignoring your messages.
On 22/06/2011 20:59, adarsh thimmappa wrote:
> Hi All,
> In the entire source file of *
> org.apache.coyote.http11.Http11NioProtocol* class in *tomcat server 7.0.14
Hi All,
In the entire source file of *
org.apache.coyote.http11.Http11NioProtocol* class in *tomcat server 7.0.14*,
there are no setters to set any of these properties such as
connectionTimeout,socket reuseaddress, keepalivetimeout etc. I compared the
same file with the *tomcat server version
Hi Mark,
Let me investigate further. I will definitely get back on this.
On Wed, Jun 22, 2011 at 11:37 PM, Mark Thomas wrote:
> 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
> >
>
> From: adarsh thimmappa [mailto:adarsh.tm...@gmail.com]
> Subject: Re: Apache Tomcat 7.0.14
> Can anyone please confirm this is an issue or not.
Not directly. Can you get Wireshark (or equivalent) traces of the traffic
between the client and the server? You can use those to determ
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 timesi feel like nothing left w.r.t going back to this link
> a
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 timesi feel like nothing left w.r.t going back to this link
again. If anyone is having configuration which is working
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 lev
Hi Andre,
I am using the below Connector tag configuration in the
server.xml.I am still facing the same problem.
Thanks,
Adarsh
On Wed, Jun 22, 2011 at 4:18 PM, André Warnier wrote:
> adarsh thimmappa wrote:
>
>> Hi All,
>> I am using Apache Tomcat 7.0 (7.0.14 ver
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
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/
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 7.0.14.
Apache Tomcat 7.0.14 includes bug fixes and the following new features
compared to version 7.0.12:
- new StuckThreadDetectionValve to identify long running requests
- JAAS authentication support for the
14 matches
Mail list logo
