I have a basic CometProcessor servlet implemented, and everything appears
to work as expected, except for one small issue: I cannot make multiple
requests from the same client to the same server.
My servlet simply sends messages to the client as they come in (think of it
as a one-sided chat, no
William Speirs wrote:
I have a basic CometProcessor servlet implemented, and everything appears
to work as expected, except for one small issue: I cannot make multiple
requests from the same client to the same server.
My servlet simply sends messages to the client as they come in (think of it
2012/1/18 William Speirs wspe...@apache.org:
I have a basic CometProcessor servlet implemented, and everything appears
to work as expected, except for one small issue: I cannot make multiple
requests from the same client to the same server.
My servlet simply sends messages to the client as
Thanks for the quick responses, I'll respond to both at once below:
On Wed, Jan 18, 2012 at 11:56 AM, André Warnier a...@ice-sa.com wrote:
really a second, different browser ? or another window/tab from the same
browser ?
(if the second case, it may be re-using the same local IP:port (or just
Quick update... I switched the code to using Servlet 3.0 and I can get
streaming data from all three browsers on the same machine: Chrome,
FireFox, and IE.
I still cannot get two tabs in Chrome or FireFox to stream data, but I
think that is simply because they are sharing JSESSIONIDs and I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William,
On 1/18/12 11:22 AM, William Speirs wrote:
It seems as though tomcat (or the comet filter) is limiting the
number of connections from the same IP address.
Have you discarded the browser as one of the components making these
kinds of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 1/18/12 12:02 PM, Konstantin Kolinko wrote:
The HTTP specification recommends to have no more than 2 active
connections to the same HTTP server. The web browsers usually
respect it.
Firefox uses 6 since v3 [1]
I remember a while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William,
On 1/18/12 1:13 PM, William Speirs wrote:
Quick update... I switched the code to using Servlet 3.0 and I can
get streaming data from all three browsers on the same machine:
Chrome, FireFox, and IE.
A Tomcat upgrade probably helped a lot
On Wed, Jan 18, 2012 at 2:00 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
Quick update... I switched the code to using Servlet 3.0 and I can
get streaming data from all three browsers on the same machine:
Chrome, FireFox, and IE.
A Tomcat upgrade probably helped a lot with
hi Peter, there was a recent large change in TC 6.0 to warn about
misconfigured server.xml
The easiest way to try out the fix is actually to build it from source
Here is how you do it
1. Make sure you have JDK 1.5, ANT and Subversion installed
2. svn co
How do you send multiple requests to the same comet servlet?
Sending multiple chunks of a single request is fine. My problem occurs
after the client ends the chunked transaction by sending 0CRLFCRLF to the
server. The comet servlet correctly registers the END event.
But then the client
hi Peter,
thanks for the example, I am able to reproduce this error, let me take a
look and see why it is happening,
Filip
Peter Warren wrote:
How do you send multiple requests to the same comet servlet?
Sending multiple chunks of a single request is fine. My problem occurs
after the
turns out that if the request is comet, the recycling of the
input/output filter is not happening.
I have fixed this,
you can try the tomcat-coyote.jar from
http://people.apache.org/~fhanik/tomcat/tomcat-coyote.jar
Filip
Filip Hanik - Dev Lists wrote:
hi Peter,
thanks for the example, I am
Filip, thank you for your very prompt response! I replaced the
tomcat-coyote.jar with yours and now get the following exception on
startup. Is there another jar that I need to update?
Thanks,
Peter
Aug 14, 2007 9:02:29 PM org.apache.tomcat.util.digester.Digester startElement
SEVERE: Begin
14 matches
Mail list logo
