Hello,
In my testing, Comet READ event will be fired when receiving data in
http POST.
(http GET will not trigger Comet READ event)
a question is: how to know the whole request data (header+body) is fully
received ?
one way is: parsing the request data, but because http is based on TCP
ting questions to the users and dev lists is frowned upon in
>> this community. If you are ever unsure where to post, post to the users
>> list and you will be redirected if necessary.
>>
>>> My team currently uses tomcat8 to serve our Scala application developed
>>
he users and dev lists is frowned upon in
> this community. If you are ever unsure where to post, post to the users
> list and you will be redirected if necessary.
>
>> My team currently uses tomcat8 to serve our Scala application developed
>> using lift. Our application uses come
2016-01-06 18:11 GMT+01:00 Ikenna Darlington :
> Hello Devs,
>
> My team currently uses tomcat8 to serve our Scala application developed
> using lift. Our application uses comet to send real time data from the
> server to the client.
>
> Unfortunately we noticed that in the
ve our Scala application developed
> using lift. Our application uses comet to send real time data from the
> server to the client.
>
> Unfortunately we noticed that in the new release of tomcat - tomcat9,
> comet is no longer supported because
>
>
> *
>
> Web
Hello Devs,
My team currently uses tomcat8 to serve our Scala application developed
using lift. Our application uses comet to send real time data from the
server to the client.
Unfortunately we noticed that in the new release of tomcat - tomcat9,
comet is no longer supported because
On 09/12/2014 17:01, Nikita Zyulyaev wrote:
> Greetings!
>
> I’ve got a problem using Tomcat 7.0.47 NioConnector with nginx 1.6.2 and
> atmosphere 2.2.3.
>
> It happens when nginx and atmosphere close the same comet connection
> concurrently.
>
> In NioEn
Greetings!
I’ve got a problem using Tomcat 7.0.47 NioConnector with nginx 1.6.2 and
atmosphere 2.2.3.
It happens when nginx and atmosphere close the same comet connection
concurrently.
In NioEndpoint.Poller thread(A) the SocketChannel becomes ready for read when
nginx closes it. Poller
e you need that.
>
> - -chris
>
> > On Tue, Sep 16, 2014 at 12:05 PM, Elias Kopsiaftis
> > wrote:
> >
> >> Hey,
> >>
> >> I actually answered my own question. Turns out config was not on
> >> comet page but on connectors page for NIO conne
Tue, Sep 16, 2014 at 12:05 PM, Elias Kopsiaftis
> wrote:
>
>> Hey,
>>
>> I actually answered my own question. Turns out config was not on
>> comet page but on connectors page for NIO connectors.
>>
>> I do have another problem though. Stress tester connect
On Tue, Sep 16, 2014 at 12:05 PM, Elias Kopsiaftis
wrote:
> Hey,
>
> I actually answered my own question. Turns out config was not on comet
> page but on connectors page for NIO connectors.
>
> I do have another problem though. Stress tester connects and works fine
> w
Hey,
I actually answered my own question. Turns out config was not on comet page
but on connectors page for NIO connectors.
I do have another problem though. Stress tester connects and works fine
when I lower number of connections from 20 to 10, however, when the program
exits and everything
I am using Tomcat7 on Linux and was wondering, is there any way to increase
the number of comet threads? Is there a max number of CometEvents that can
be queued? I have a feeling either certain connections are not logging
themselves, or they are being dropped due to an overload caused by my
stress
of
> org.apache.catalina.valves.CometConnectionManagerValve
> wrong. sorry about that. Still have the random disconnect error though
>
>
> On Fri, Aug 1, 2014 at 10:46 AM, Elias Kopsiaftis
> wrote:
>
>> I am developing a COMET application that is primarily based on the
>> example given on the documentation of
ok looks like i have the configuration of
org.apache.catalina.valves.CometConnectionManagerValve
wrong. sorry about that. Still have the random disconnect error though
On Fri, Aug 1, 2014 at 10:46 AM, Elias Kopsiaftis wrote:
> I am developing a COMET application that is primarily based on
I am developing a COMET application that is primarily based on the example
given on the documentation of the chat server. My problem is that when two
users connect, the connection held open by the comet servlet is closed. I
know this because I am getting END events in my log.
The confusing part is
I am having random errors, but we are still looking into them because right
now we think they are probably from our end. The current one is that the
connection from the client to the comet servlet will randomly repeatedly
receive "NULL". Still looking into this to see what the server is
g to save
> myself the work. Also, I couldnt find a page of known tomcat7 comet
> issues. If such a page existed it would be helpful
Check Bugzilla. Anything logged and not fixed is "known", I suppose.
Also check the changelogs. Feel free to check everything between Tomat
6.0.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Elias,
On 5/29/14, 3:12 PM, Elias Kopsiaftis wrote:
> ok thanks guys, I just got freaked out when I saw that post.
There are other things that might freak you out. Read the security
statements for Tomcat 7, for instance, and decide if you are at th
>
> You should make sure you are using the most up-to-date patch version
> of Tomcat in your release line. If you are using Tomcat 7, you want to
> make sure you are using Tomcat 7.0.54 which was just recently released
> and includes a few security updates.
>
> As for a tec
nology for the future, you should dump Comet: the world
is standardizing on Websocket. Java EE now includes a Websocket API,
so you'll be able to deploy Websocket-based web applications on any
compliant container instead of tying yourself to the Tomcat-specific
Comet implementation.
- -chris
To make sure it doesnt exist in Tomcat7. Thats why. Ive never looked into
the tomcat source code and theres no point for my current project unless
this bug still exists. Just trying to save myself the work. Also, I couldnt
find a page of known tomcat7 comet issues. If such a page existed it would
which
is in development depends on Comet technology to work.
http://bighow.net/4294974-Comet_under_Tomcat_6_0_33_sends_data_to_a_wrong_user.html
Before I start digging into the tomcat7 source code, can anyone verify or
contest the issue on that site? If Comet is not 100%
dependable, how about
oh yea, im on tomcat 7 btw
On Thu, May 29, 2014 at 2:13 PM, Elias Kopsiaftis wrote:
> Hey guys,
>
> I found this on the web, and it really alarms me because my web app which
> is in development depends on Comet technology to work.
>
>
> http
Hey guys,
I found this on the web, and it really alarms me because my web app which
is in development depends on Comet technology to work.
http://bighow.net/4294974-Comet_under_Tomcat_6_0_33_sends_data_to_a_wrong_user.html
Before I start digging into the tomcat7 source code, can anyone verify
s Kopsiaftis wrote:
>> > Is there any way to put a reverse proxy in front of a Comet
>> > servlet?
>>
>> I don't believe so. There is work being done on supporting Websocket
>> through mod_proxy but it will likely never support Comet.
>>
>> > I t
PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Elias,
>
> On 5/12/14, 11:20 AM, Elias Kopsiaftis wrote:
> > Is there any way to put a reverse proxy in front of a Comet
> > servlet?
>
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Elias,
On 5/12/14, 11:20 AM, Elias Kopsiaftis wrote:
> Is there any way to put a reverse proxy in front of a Comet
> servlet?
I don't believe so. There is work being done on supporting Websocket
through mod_proxy but it will likely ne
Is there any way to put a reverse proxy in front of a Comet servlet? I
tried apache but thats a no go because it uses a single thread per
connection, which is not scaleable, then I tried nginx, which perhaps I did
something wrong in my setup but in the client code, the call to
getInputStream never
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Elias,
On 4/18/14, 2:55 PM, Elias Kopsiaftis wrote:
> Oh, what I meant was version information is that server sends
> version and tells you to upgrade if you dont have the right
> version.
I was asking for you to tell us what versions of everything
ccessed by the client until it
> > gets a return value from the login servlet, and im sure it happens
> > in this order in the code. My best guess is that the request is
> > somehow going to two servlets somehow, but i dont know if this is
> > even possible, but I dont know
rn value from the login servlet, and im sure it happens
> in this order in the code. My best guess is that the request is
> somehow going to two servlets somehow, but i dont know if this is
> even possible, but I dont know what else could happen. If you are
> running a comet servlet
are running a comet servlet next to traditional servlets, its there
any chance both will get the same request?
> I am trying to implement a Comet process.
> > Tomcat 6.0.36
> > Red Hat Enterprise Linux Server release 6.2 (Santiago)
> > Java 7u11 (32 bit)
> >
> > I have implemented CometProcessor. I am using the NIO connector.
> > When I try the servlet I get: HTTP me
2013/1/22 Andrew Winter :
> I am trying to implement a Comet process.
> Tomcat 6.0.36
> Red Hat Enterprise Linux Server release 6.2 (Santiago)
> Java 7u11 (32 bit)
>
> I have implemented CometProcessor. I am using the NIO connector.
> When I try the servlet I get: HTTP method
Here is the NIO connector:
Normal servlet requests work, just not the Comet.
After I sent this email, I installed the APR and switched back to the
standard connector:
The log then showed that the APR connector was being used, but I get the
same message when I try to use the comet servlet
On 22/01/2013 16:52, Andrew Winter wrote:
> I am trying to implement a Comet process.
> Tomcat 6.0.36
> Red Hat Enterprise Linux Server release 6.2 (Santiago)
> Java 7u11 (32 bit)
>
> I have implemented CometProcessor. I am using the NIO connector.
> When I try the servlet I
I am trying to implement a Comet process.
Tomcat 6.0.36
Red Hat Enterprise Linux Server release 6.2 (Santiago)
Java 7u11 (32 bit)
I have implemented CometProcessor. I am using the NIO connector.
When I try the servlet I get: HTTP method GET is not supported by this URL
Am I doing something wrong
possible?
You can set up as many connectors in Tomcat as you want: it's just
more port numbers. You can even have them all share the same
so you have a single thread pool for everything, regardless
of protocol.
> Ideal thing would be to add mod_proxy (without removing mod_jk) so
> my
7;
Subject: Comet not sending response under load
Hello Everyone,
I am having an issue where tomcat 6.0.35 comet is not sending a response
when the host is under significant load. It is also sending the end
event which, as far as I understand, means the CometEvent is not being
closed.
Hello Everyone,
I am having an issue where tomcat 6.0.35 comet is not sending a response
when the host is under significant load. It is also sending the end
event which, as far as I understand, means the CometEvent is not being
closed.
I am suspicious that this may be because the legacy
I have two servlets, one is comet. i am using an nio connector. i have an
application that connects to both servlets at once, however, the standard
servlet does not process any requests. i am able to connect to it, because
i dont get an exception from the client when connecting. i can also write
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
-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 lo
-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 whil
-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
ki
sue... you
> guys move too fast for me :-)
>
>
>> > servlet-api-2.5.jar
>>
>> Where?
>>
>
> This was included in our pom.xml file as provided, which
> was blatantly stolen from an example somewhere online.
>
> > tomcat-*-7.0-SNAPSHOT
>&g
eing somewhere it stated we should include this
in our pom.xml as required to "make it all work".
On a more general level, was the Comet implementation in Tomcat simply
a precursor to Servlet 3.0's asynchronous functionality?
In looking at other examples and reading the overview of
b browsers usually respect
it.
IIRC "the same server" = the same DNS name, so different names have
different connection limits.
It should be already discussed elsewhere - try to search.
>
> It seems as though tomcat (or the comet filter) is limiting the number of
> connections from
g to connect. However, if I connect from a second client (IP
address), then the "void event(CometEvent event)" method is called, and the
second client starts receiving messages.
It seems as though tomcat (or the comet filter) is limiting the number of
connections from the same IP address.
quot;void event(CometEvent event)" method is called, and the
second client starts receiving messages.
It seems as though tomcat (or the comet filter) is limiting the number of
connections from the same IP address. I have not tested this yet, but that
would be an issue in NAT situations where a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sudeep,
On 8/1/2011 2:47 PM, Sudeep Pradhan wrote:
> Stale as in, It gives me response which was suppose to be given for
> the previous request (it gives me xml(previous) response instead of
> json(current)).
That's not what you said before. Can yo
with Tomcat 6.0.32.*
Is this a bug?
Thanks,
Sudeep
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Saturday, July 30, 2011 2:00 PM
To: Tomcat Users List
Subject: Re: Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is
terminated
On 29/07/2011 18:33, Sudeep
.@pidster.com]
> Sent: Friday, July 29, 2011 12:32 AM
> To: Tomcat Users List
> Subject: Re: Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is
> terminated
>
> On 28/07/2011 20:42, Sudeep Pradhan wrote:
>> Hi,
>>
>> I have a CometProcessor Servlet
-
From: Pid [mailto:p...@pidster.com]
Sent: Friday, July 29, 2011 12:32 AM
To: Tomcat Users List
Subject: Re: Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is
terminated
On 28/07/2011 20:42, Sudeep Pradhan wrote:
> Hi,
>
> I have a CometProcessor Servlet which is
On 28/07/2011 20:42, Sudeep Pradhan wrote:
> Hi,
>
> I have a CometProcessor Servlet which is used for streaming system events to
> a http client. I have SSL enabled on the server. I use *curl* as the http
> client. I get streaming events on the console. But when I do a Ctrl-C on the
> console
Hi,
I have a CometProcessor Servlet which is used for streaming system events to a
http client. I have SSL enabled on the server. I use *curl* as the http client.
I get streaming events on the console. But when I do a Ctrl-C on the console
there no End event is raised and hence the connection
t(eventString);
writer.flush();
}
Thanks,
Sudeep
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Monday, July 25, 2011 12:37 PM
To: Tomcat Users List
Subject: Re: Comet: How to send *Chunked* response
On 25/07/2011 19:23, Sudeep Pradhan wrote:
On 25/07/2011 19:23, Sudeep Pradhan wrote:
> Hi,
>
> I am using CometProcessor to stream event notifications from server to
> client. The events are generated at random. I want to send the notification
> with Transfer Encoding as chunked so that I can use Apache's
> ChunkedInputStream to parse
Hi,
I am using CometProcessor to stream event notifications from server to client.
The events are generated at random. I want to send the notification with
Transfer Encoding as chunked so that I can use Apache's ChunkedInputStream to
parse the output.
I get the PrintWriter from the ServletRes
al Message-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: Wednesday, July 13, 2011 1:43 PM
To: Tomcat Users List
Subject: Re: Comet over HTTPS: END event recieved immeidately for the first few
times
is it possible that when you turn on SSL, you are using the regular BIO
conn
helps you understand the scenario better.
Thanks,
Sudeep
-Original Message-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: Wednesday, July 13, 2011 1:43 PM
To: Tomcat Users List
Subject: Re: Comet over HTTPS: END event recieved immeidately for the first few
times
is it pos
is it possible that when you turn on SSL, you are using the regular BIO
connector when you use SSL and Comet is not supported by that connector.
best
Filip
On 7/11/2011 11:05 AM, Sudeep Pradhan wrote:
Hi Filip,
I have tried the app with tomcat 6.0.32 and 7.0.16, and the result is the same.
I
as the client
for testing.
Please let me know if you want to know more.
Thanks,
Sudeep
-Original Message-
From: Filip Hanik - Dev Lists [mailto:devli...@hanik.com]
Sent: Sunday, July 10, 2011 8:12 PM
To: Tomcat Users List
Subject: Re: Comet over HTTPS: END event recieved immeidately for
PM
To: users@tomcat.apache.org
Subject: Comet over HTTPS: END event recieved immeidately for the first few
times
Hello,
I am using Tomcat 6.0.20 on Ubuntu 10.04 and have written a simple
TomcatWeatherServlet as presented in
http://www.ibm.com/developerworks/web/library/wa-cometjava/ I modifie
Any insights on this?
-Original Message-
From: Sudeep Pradhan [mailto:pradh...@vmware.com]
Sent: Wednesday, June 29, 2011 4:54 PM
To: users@tomcat.apache.org
Subject: Comet over HTTPS: END event recieved immeidately for the first few
times
Hello,
I am using Tomcat 6.0.20 on Ubuntu
Hello,
I am using Tomcat 6.0.20 on Ubuntu 10.04 and have written a simple
TomcatWeatherServlet as presented in
http://www.ibm.com/developerworks/web/library/wa-cometjava/ I modified the
servlet to stream weather feed to multiple curl clients. I am using curl 7.21.6
as my client.
When I run c
Hello, i have a problem to implement a Comet Server, i use tomcat 7
and i try to keep many connections open and for each client connected
return a string each time than other client press "go()" but the
return from the server only happend when the time out expired, and
execute the e
sol myr wrote:
Thanks :)
You're correct about blocking inputStreams, but I actually need Tomcat to write
a multipart *response*, on an OutputStream (the reading side is on the client,
and our client-side programmers will manage it without blocking).
I wondered whether I'll have to hand-code it
(manually output the headers,
etc), or is there some utilities on Tomcat/apach.
Thanks anyway :)
--- On Tue, 1/4/11, Filip Hanik - Dev Lists wrote:
From: Filip Hanik - Dev Lists
Subject: Re: Comet and multipart
To: "Tomcat Users List"
Date: Tuesday, January 4, 2011, 9:43 AM
> 1) If
t;content-length" for all messages put together, or it might omit it
altogether and use "chunked" instead - which is also be an option, but then how do we tell tomcat
to have a chunk per message).
I would not use Content-Length, by doing so, you're setting a limit to yourself
On 04/01/2011 10:34, Joe Biron wrote:
>>> Is there a better way to do this? Should my application handle these
>>> timeouts, and use the comet.timeout as a longer safety net?
>>
>> That sounds like the way to do it to me.
>>
>> Mark
>
> Thanks. It
>> Is there a better way to do this? Should my application handle these
>> timeouts, and use the comet.timeout as a longer safety net?
>
> That sounds like the way to do it to me.
>
> Mark
Thanks. It would be great if the comet event "pump" gave me a
PRE_TIMEOUT
; response.flushBuffer();
> event.close();
> ...
>
> the client does not receive the response. They only sense an
> unceremonious connection close - which, if through routers, may take
> quite some time to be detected.
>
> How can I hook into the timeout to send the client a
on, 1/3/11, Filip Hanik - Dev Lists wrote:
From: Filip Hanik - Dev Lists
Subject: Re: Comet and multipart
To: "Tomcat Users List"
Date: Monday, January 3, 2011, 8:47 AM
On 1/3/2011 7:48 AM, sol myr wrote:
> Hi,
>
> We're implementing a CometServlet on top of Tomcat NIO conn
Hello,
I've been making great progress with CometProcessor on Tomcat 6.0.29.
I have a question about handling timeouts (and I did review this
thread: http://www.mail-archive.com/users@tomcat.apache.org/msg55616.html).
I want my clients to connect and stay connected for a very long time,
but I do
On 1/3/2011 7:48 AM, sol myr wrote:
Hi,
We're implementing a CometServlet on top of Tomcat NIO connector, using "long
polling".
Currently we're using the approach recommended by most tutorials: the client
opens a connection and waits for a message (for a configured timeout); if such
a message
On 03/01/2011 14:48, sol myr wrote:
> Hi,
>
> We're implementing a CometServlet on top of Tomcat NIO connector, using "long
> polling".
> Currently we're using the approach recommended by most tutorials: the client
> opens a connection and waits for a message (for a configured timeout); if
> su
Hi,
We're implementing a CometServlet on top of Tomcat NIO connector, using "long
polling".
Currently we're using the approach recommended by most tutorials: the client
opens a connection and waits for a message (for a configured timeout); if such
a message arrives, the client consumes it (e.g.
Op donderdag, 2 december 2010 20:37 schreef Pid :>
On 12/2/10 3:28 PM, Ronald Klop wrote:
> Hello,
>
> I'm trying Tomcat 7. The Comet classes have been moved from the
> org.apache.catalina package to the org.apache.catalina.comet package.
> That is fine by me. But fo
On 12/2/10 3:28 PM, Ronald Klop wrote:
> Hello,
>
> I'm trying Tomcat 7. The Comet classes have been moved from the
> org.apache.catalina package to the org.apache.catalina.comet package.
> That is fine by me. But for deployment reasons it would be easy if I can
> deploy t
Hello,
I'm trying Tomcat 7. The Comet classes have been moved from the
org.apache.catalina package to the org.apache.catalina.comet package. That is
fine by me. But for deployment reasons it would be easy if I can deploy the
same war on Tomcat 6 and Tomcat 7. In that way I don't n
Caldarale, Charles R schrieb am 29.11.2010 um 22:47 (-0600):
> > From: Michael Ludwig [mailto:mil...@gmx.de]
>
> > can we say that:
>
> > (a) blocking IO requires one thread (or, in some other
> > server environments, one process) per socket
>
> Well, sort of. The actual requirement is one thr
> From: Michael Ludwig [mailto:mil...@gmx.de]
> Subject: Re: (Tomcat) Does NIO connector make a difference outside of 'Comet'
> ?
> can we say that:
> (a) blocking IO requires one thread (or, in some other
> server environments, one process) per socket
Well, sort
Mark Thomas schrieb am 29.11.2010 um 16:34 (+):
> On 29/11/2010 16:23, sol myr wrote:
> > I've just started looking into the NIO Connector.
> > And I see why it's great to combine NIO+Comet...
> > But does it makes any difference outside of Comet?
>
> Yes.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sol,
On 11/29/2010 11:23 AM, sol myr wrote:
> I've just started looking into the NIO Connector.
> And I see why it's great to combine NIO+Comet...
> But does it makes any difference outside of Comet?
Some data: please read th
On 29/11/2010 16:23, sol myr wrote:
> Hi,
>
> I've just started looking into the NIO Connector.
> And I see why it's great to combine NIO+Comet...
> But does it makes any difference outside of Comet?
Yes.
>
> 1) Namely, if I only have old-fashioned Servlets (no
Hi,
I've just started looking into the NIO Connector.
And I see why it's great to combine NIO+Comet...
But does it makes any difference outside of Comet?
1) Namely, if I only have old-fashioned Servlets (not a "CometProcessor") -
will it improve performance to use NIO connec
Mark Thomas wrote:
>
> If there is a problem with Comet then create a Bugzilla entry
> (preferably with a test case) and someone will take a look. Tests cases
> should be the simplest possible code to reproduce the problem.
>
https://issues.apache.org/bugzilla/show_bug.cgi?id=
f the way there will be a release.
>>
>
> As per http://old.nabble.com/Tomcat-7-tt27962562.html#a27962663 the thread
> above , what is the status/ETA of comet async timeouts in Tomcat 7?
I wasn't aware there was a problem with Comet. The async timeouts I was
referring to were
xt:
http://old.nabble.com/Comet-async-timeouts-in-Tomcat-7-tp29993045p29995090.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional co
f the way there will be a release.
>>
>
> As per http://old.nabble.com/Tomcat-7-tt27962562.html#a27962663 the thread
> above , what is the status/ETA of comet async timeouts in Tomcat 7?
Could you be more precise about what you are asking for?
The changelog is here:
http://tom
m/Tomcat-7-tt27962562.html#a27962663 the thread
above , what is the status/ETA of comet async timeouts in Tomcat 7?
Thanks,
-Jeremy Norris
--
View this message in context:
http://old.nabble.com/Comet-async-timeouts-in-Tomcat-7-tp29993045p29993045.html
Sent from the Tomcat - User mailing
> From: Thiago Locatelli da Silva [mailto:thiago.si...@digitro.com.br]
> Subject: Help with Tomcat 6.0.29 and Comet
> The only way to make my application is avoid closing the event in
> the END event, only in the ERROR event (and all the other ones).
> I am not sure this is the
Hello everybody.
We have an application which was developed using comet and gwt and it
was build over the tomcat 6.0.16 code. It was working very well and as
according to the documentation, we are closing all the come events when
we reach the event type ERROR and END. The application has
Hello All,
I have seen a lot of code related to Comet and I have noticed some
difference among them. The first one is that some codes close the event
on the BEGIN event and others dont. What is the best practice in this case?
I know that closing the event in the END and ERROR events is a
Hello everybody.
We have an application which was developed using comet and gwt and it
was build over the tomcat 6.0.16 code. It was working very well and as
according to the documentation, we are closing all the come events when
we reach the event type ERROR and END. The application has
Hello everybody.
We have an application which was developed using comet and gwt and it
was build over the tomcat 6.0.16 code. It was working very well and as
according to the documentation, we are closing all the come events when
we reach the event type ERROR and END. The application has
A little more info.
I mentioned that on Centos when I disabled keepalives the response to the
client would not close right away (as it would do properly on my Windows
machine). I downgraded TC on my windows machine from 6.0.28 to 6.0.26 (same
as I have on Centos) and I can now duplicate this issu
FYI - I am using org.apache.coyote.http11.Http11NioProtocol as my connector
protocol. My "long polling" requests are pretty quick (less than 2 seconds)
so its not a long connection issue.
1 - 100 of 528 matches
Mail list logo
