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
oh yea, im on tomcat 7 btw
On Thu, May 29, 2014 at 2:13 PM, Elias Kopsiaftis yemi...@gmail.com 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.
On 5/29/2014 2:21 PM, Elias Kopsiaftis wrote:
oh yea, im on tomcat 7 btw
Then why are you asking about a problem in a very old version of Tomcat 6?
On Thu, May 29, 2014 at 2:13 PM, Elias Kopsiaftis yemi...@gmail.com wrote:
Hey guys,
I found this on the web, and it really alarms me
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 5/29/14, 2:45 PM, David kerber wrote:
On 5/29/2014 2:21 PM, Elias Kopsiaftis wrote:
oh yea, im on tomcat 7 btw
Then why are you asking about a problem in a very old version of
Tomcat 6?
+1
Also, that web site looks like a scraping
ok thanks guys, I just got freaked out when I saw that post.
On Thu, May 29, 2014 at 3:10 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 5/29/14, 2:45 PM, David kerber wrote:
On 5/29/2014 2:21 PM, Elias Kopsiaftis
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Elias,
On 5/29/14, 3:08 PM, Elias Kopsiaftis wrote:
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
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 doing
On
Hi all,
I am using Tomcat6 together with Comet. I implemented as described in
the article Advanced IO and Tomcat the servlet, message sender ...
The main reason for using comet is that I would like to implement a kind
of streaming, what means:
I am launching from the client with a AJAX
, but wanted to know what people recommend
before I just hack at it...
Thanks
Adam
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 27, 2008 8:20 PM
To: Tomcat Users List
Subject: Re: Tomcat Comet Question
try the simplest thing first, upgrade
I am having trouble getting Comet to work and was hoping someone knows
what my problem is...
I am running 6.0.13 on windows XP (yea, I need to change to linux, I
know)...anyway, I went through getting the APR setup and I believe I
have done so...based on when I start tomcat up, I get this
Adam Kaupisch wrote:
I am having trouble getting Comet to work and was hoping someone knows
what my problem is...
I am running 6.0.13 on windows XP (yea, I need to change to linux, I
know)...anyway, I went through getting the APR setup and I believe I
have done so...based on when I start
try the simplest thing first, upgrade to 6.0.16,
in terms of your config, you have tcnative-1.dll in your PATH, but you
haven't configured the APR connector, you have configured NIO (which
works for comet) and the regular blocking (which doesn't work for comet)
Filip
Adam Kaupisch wrote:
On 4/23/07, Martin Perez [EMAIL PROTECTED] wrote:
Any suggestions?
I would try to avoid using directly Object*Stream, to see what
happens, and verify the validity of the data which is sent and
received.
Rémy
-
To start a new
Hi Rémy,
Actually, without using Object*Stream everything seems to work. I'm
currently using raw I/O streams and the communication is ok.
I guess people on the list would be interesting to know that currently
doesn't work with Object*Streams, either when Object*Streams are not
specially famous
On 4/24/07, Martin Perez [EMAIL PROTECTED] wrote:
Hi Rémy,
Actually, without using Object*Stream everything seems to work. I'm
currently using raw I/O streams and the communication is ok.
I guess people on the list would be interesting to know that currently
doesn't work with Object*Streams,
Rémy Maucherat wrote:
On 4/3/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote:
yes, a proposal is coming up, my guess is that you will do a {public int
write(ByteBuffer)} on the CometEvent object. returns number of bytes
written, but nothing is set in stone yet
I hope that your proposal
Hi,
Thanks again for the reply. I can't reproduce the END event so probably
I was mistaken, sorry about that. It is indeed the ERROR/TIMEOUT event.
If an exception occurs during the handling of this event (an unforseen
runtime exception for example), then tomcat calls the event method again
Hi,
Another reason that I need to be able to throw the exception in the
BEGIN event is because for some requests there is no input, only output,
so I might never actually get a READ event (GET requests for long pieces
of data for example). However I do want to write output to the client as
it
On 4/3/07, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
Hi,
Thanks again for the reply. I can't reproduce the END event so probably
I was mistaken, sorry about that. It is indeed the ERROR/TIMEOUT event.
If an exception occurs during the handling of this event (an unforseen
runtime exception for
Hi,
Thanks for all the answers! :-)
It's good to know the way the events should be treated and interpreted.
It's quite different from how it's described on
http://tomcat.apache.org/tomcat-6.0-doc/aio.html, and the JavaDoc does
not really describe the spec either.
Using the sendError method
Sebastiaan van Erk wrote:
Hi,
Thanks for all the answers! :-)
It's good to know the way the events should be treated and
interpreted. It's quite different from how it's described on
http://tomcat.apache.org/tomcat-6.0-doc/aio.html, and the JavaDoc does
not really describe the spec either.
On 4/3/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote:
yes, a proposal is coming up, my guess is that you will do a {public int
write(ByteBuffer)} on the CometEvent object. returns number of bytes
written, but nothing is set in stone yet
I hope that your proposal does not include that
Hi,
Thanks for the response.
To get these adjustments, do I need to download tomcat from a subversion
(or CVS) repository?
I was also just discovered that in the 6.0.10 version that an exception
in the END event causes the END event to called again; this means that
an uncaught
On 4/2/07, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
Hi,
Thanks for the response.
To get these adjustments, do I need to download tomcat from a subversion
(or CVS) repository?
Yes.
I was also just discovered that in the 6.0.10 version that an exception
in the END event causes the END
On 4/2/07, Rémy Maucherat [EMAIL PROTECTED] wrote:
I was also just discovered that in the 6.0.10 version that an exception
in the END event causes the END event to called again; this means that
an uncaught RuntimeException could potentially cause Tomcat to go into a
loop of an infinite
Hi,
I'm trying to use Comet in tomcat 6.0.10, and have the following test class:
public class CometServlet extends HttpServlet implements CometProcessor {
public void event(final CometEvent event) throws IOException,
ServletException {
final HttpServletRequest request =
I have made some adjustments.
An exception there should produce an error report, and a sendError
should do the same. However, an event.close should simply end the
processing of the request without any change of the response state
(which will be whatever was set in the servlet).
Note: the
29 matches
Mail list logo
