Thanks for the response.
Unfortunately, we had a load of these errors at one go, and Tomcat
subsequently died of an OutOfMemory error.
André Warnier
24/03/2011 15:58
Please respond to
"Tomcat Users List"
To
Tomcat Users List
cc
Subject
Re: Tomcat + apache + mod_jk
ar...@bca-grou
So I assume adding connectionTimeout attribute to the connector config
could help mitigate this?
André Warnier
24/03/2011 15:15
Please respond to
"Tomcat Users List"
To
Tomcat Users List
cc
Subject
Re: Tomcat + apache + mod_jk
Hi.
The schema is :
a) request :
browser -(1)-> (a
Martin Gainty
24/03/2011 15:04
Please respond to
"Tomcat Users List"
To
Tomcat Users List
cc
Subject
RE: Tomcat + apache + mod_jk
can we see the connector configuration you are implementting in
server.xml?
Martin
__
Verzicht und Ver
For the first time we have received this error (many times). Looks to me
like tomcat cannot talk to apache to me. Can anyone shed any light on
this?
Windows Server 2003
Tomcat: 6.0.16
Apache: 2.2
JDK: 1.6.0_23
Tomcat and Apache on same box so I don't see how it can be a network
issue as some
I don't think I do this but I'm double-checking. Thanks.
After writing to the OutputStream, should I just close the OutputStream
which seems to generate a CometEvent.CLOSE or explicitly call
event.close() after closing the stream?
Thanks, Adam
"Caldarale, Charles R"
21/03/2011 15:47
Plea
Hi,
I am using Tomcat 6.0.32 with the Http11NioProtocol connector to implement
long polling.
My comet processor is holding the HttpSevletResponse (After receiving a
CometEvent.BEGIN) on a queue until an event is ready to send back. When it
sends back the event, it is writing a binary stream to
