> 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
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 GET is not supported
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.
T
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 get: HTTP method GET
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?
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 event.close();
Hi,
I am working on a scenario with browsers as clients.
The client does requests with JavaScript code like this:
req = new XMLHttpRequest();
req.onreadystatechange = handler;
req.open("post",
"/somecontext/somecometservlet/somerequest?param1=val1¶m2=val2" );
req.send(null);
We intenti
> -Original Message-
> From: Rémy Maucherat [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 02, 2007 11:13 PM
> On 5/2/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
> > It's a race condition and the problem occurs quite infrequently
> > (especially with small request bodies). The l
> -Original Message-
> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
> > Wouldn't every application which isn't as dumb as the chat example
> > (which does not care about the content it reads but simply passes it
> > back to it's clients) need to implement it's own mechanism to
On 5/2/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
It's a race condition and the problem occurs quite infrequently
(especially with small request bodies). The larger the request body of
the POST request, the more likely it is that the problem occurs. I was
testing at a few thousand request
Hi,
I have no problem to get POST parameter with NIO Connector at my
begin.event. With APR connector I also have POST parameter problems.
Strange! A my first request I get the POST parameter. The POST message
close the event and I got an exception after the end event.
It's a race condition
Hi
Am 02.05.2007 um 17:26 schrieb Sebastiaan van Erk:
Hi,
How about not arguing about everything ? It is your fault when
parameters are not processed. Tomcat will process parameters with
comet.
No, Comet will not process parameters in POST requests if you call
getParameter() in the BEGIN e
Reich, Matthias wrote:
-Original Message-
From: Sebastiaan van Erk [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 7:24 PM
To: Tomcat Users List
Subject: Re: Comet: problem with request.getParameter() in
Comet POST requests
GET parameters, ie parameters in the
Hi,
How about not arguing about everything ? It is your fault when
parameters are not processed. Tomcat will process parameters with
comet.
No, Comet will not process parameters in POST requests if you call
getParameter() in the BEGIN event and the request body has not yet
arrived. getParamete
On 5/2/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
Sorry about that, did not mean to say it is not possible to do a
request, wait, response with Comet. All I'm trying to say is that Comet
was not designed (at least, Filip stated this) for the async servlet
model, and I tried to point out so
Rémy Maucherat wrote:
On 5/2/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
What you seem to want is more in line with the "asynchronous servlet"
(request, wait, response), which Filip and Remy pointed out is not the
quite the same as Tomcat's Comet. Ideally, both models would be possible
thr
On 5/2/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
What you seem to want is more in line with the "asynchronous servlet"
(request, wait, response), which Filip and Remy pointed out is not the
quite the same as Tomcat's Comet. Ideally, both models would be possible
through single unified AP
> > Wouldn't every application which isn't as dumb as the chat example
> > (which does not care about the content it reads but simply passes it
> > back to it's clients) need to implement it's own mechanism to check
> > whether there is enough input available to start parsing a chunk of
> > data?
Hi,
Wouldn't every application which isn't as dumb as the chat example
(which does not care about the content it reads but simply passes it
back to it's clients) need to implement it's own mechanism to check
whether there is enough input available to start parsing a chunk of
data?
Either that
> -Original Message-
> From: Sebastiaan van Erk [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 27, 2007 7:24 PM
> To: Tomcat Users List
> Subject: Re: Comet: problem with request.getParameter() in
> Comet POST requests
>
>
> > GET parameters, ie p
Rémy Maucherat wrote:
On 4/27/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
> GET parameters, ie parameters in the URL will work.
> However, using Comet you shouldn't rely on parameters in the body, the
> body if for you usage, and your usage alone.
Seems to me that this is a pretty common u
On 4/27/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
> GET parameters, ie parameters in the URL will work.
> However, using Comet you shouldn't rely on parameters in the body, the
> body if for you usage, and your usage alone.
Seems to me that this is a pretty common use case though with AJA
GET parameters, ie parameters in the URL will work.
However, using Comet you shouldn't rely on parameters in the body, the
body if for you usage, and your usage alone.
Seems to me that this is a pretty common use case though with AJAX
server side push: request, wait, response.
Comet is used to
Sebastiaan van Erk wrote:
Rémy Maucherat wrote:
On 4/26/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
Hi,
If the body of the POST request is not present at the time of the
getParameter() call, it returns null even if the parameter value is
set.
Things don't work like this, obviously. Pa
Rémy Maucherat wrote:
On 4/26/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
Hi,
If the body of the POST request is not present at the time of the
getParameter() call, it returns null even if the parameter value is set.
Things don't work like this, obviously. Parameter parsing only occurs
On 4/26/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
Hi,
If the body of the POST request is not present at the time of the
getParameter() call, it returns null even if the parameter value is set.
Things don't work like this, obviously. Parameter parsing only occurs
if nothing used getRead
Hi,
If the body of the POST request is not present at the time of the
getParameter() call, it returns null even if the parameter value is set.
How to reproduce:
1) Send the headers of a POST request to the CometProcessor.
2) in the event() method of the CometProcessor use getParameter(); it
Rémy Maucherat wrote:
On 4/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Sebastiaan van Erk wrote:
> Hi,
>
> The fixes seem to work well, thanks again! :-)
Excellent, thanks for bringing it to my attention
And it was committed before tagging, not 5 minutes after as usually
happens.
On 4/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Sebastiaan van Erk wrote:
> Hi,
>
> The fixes seem to work well, thanks again! :-)
Excellent, thanks for bringing it to my attention
And it was committed before tagging, not 5 minutes after as usually
happens. I feel lucky today.
R
Sebastiaan van Erk wrote:
Hi,
The fixes seem to work well, thanks again! :-)
Excellent, thanks for bringing it to my attention
Filip
Regards,
Sebastiaan
Sebastiaan van Erk wrote:
Hi,
Thanks for the quick action. I'll test the new version right away. :-)
Regards,
Sebastiaan
Filip Hanik -
Hi,
The fixes seem to work well, thanks again! :-)
Regards,
Sebastiaan
Sebastiaan van Erk wrote:
Hi,
Thanks for the quick action. I'll test the new version right away. :-)
Regards,
Sebastiaan
Filip Hanik - Dev Lists wrote:
Sebastian,
I have checked in a fix to SVN. You can also work around
Hi,
Thanks for the quick action. I'll test the new version right away. :-)
Regards,
Sebastiaan
Filip Hanik - Dev Lists wrote:
Sebastian,
I have checked in a fix to SVN. You can also work around the problem
by not using the shared selector by adding
-Dorg.apache.tomcat.util.net.NioSelectorSha
Sebastian,
I have checked in a fix to SVN. You can also work around the problem by
not using the shared selector by adding
-Dorg.apache.tomcat.util.net.NioSelectorShared=false
to your command line
Filip
Filip Hanik - Dev Lists wrote:
definitely a bug, I will work on a fix right away.
Filip
S
definitely a bug, I will work on a fix right away.
Filip
Sebastiaan van Erk wrote:
Hi,
I have the following problem with Comet. I have a long request, and I
asynchronously write data to the output stream of the response while
the request is between the BEGIN and END/ERROR events. However, the
Hi,
I have the following problem with Comet. I have a long request, and I
asynchronously write data to the output stream of the response while the
request is between the BEGIN and END/ERROR events. However, the writes
do NOT occur while IN a READ request, but are triggered by other events
on
35 matches
Mail list logo
