ok now it is properly configured(I was missing the slash at the end of the
tag), but Im still getting null for event subtypes. Any thoughts?
On Fri, Aug 1, 2014 at 11:18 AM, Elias Kopsiaftis wrote:
> ok looks like i have the configuration of
> org.apache.catalina.valves.CometConnectionManagerV
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 the e
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,
-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
Peter Warren wrote:
Could you indulge me and try the client with the sleep?
just did, worked exactly as before.
event: BEGIN, subtype: null
event: READ, subtype: null
Read 10 bytes: comet test for session: A01334D0AC22505DCD4B323820963FEC
read error
event: ERROR, subtype: TIMEOUT
> > Could you indulge me and try the client with the sleep?
> >
> just did, worked exactly as before.
> event: BEGIN, subtype: null
> event: READ, subtype: null
> Read 10 bytes: comet test for session: A01334D0AC22505DCD4B323820963FEC
> read error
> event: ERROR, subtype: TIMEOUT
Hmm, not sure whe
Peter Warren wrote:
Could you indulge me and try the client with the sleep?
just did, worked exactly as before.
event: BEGIN, subtype: null
event: READ, subtype: null
Read 10 bytes: comet test for session: A01334D0AC22505DCD4B323820963FEC
read error
event: ERROR, subtype: TIMEOUT
I see the e
Could you indulge me and try the client with the sleep?
I see the end event when there's a break/delay between sending a chunk
and sending the last chunk. It is legal http to send the last chunk
separately from preceding chunks, isn't it?
> getting a -1 on a inputstream.read is normal (even for
getting a -1 on a inputstream.read is normal (even for a regular
servlet). that means you've reached EOF and shouldn't read anymore.
I haven't tested with the sleep, and I did try with the cometgui, and
that worked as well.
Filip
Peter Warren wrote:
Is the read error expected behavior? I g
Is the read error expected behavior? I guess I didn't expect the
comet processor to send me a read event on a last chunk since there's
nothing to be read. I thought either a read error or an end event
after a last chunk indicated a problem. If the read error is ok,
then...
Did you try the clien
works just dandy, the timeout happens after quite some time of just waiting
Jan 28, 2008 2:33:31 PM org.apache.coyote.http11.Http11NioProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jan 28, 2008 2:33:31 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1005 ms
event
ector is a supported TC6 feature
Thanks
Martin
- Original Message -
From: "Peter Warren" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Friday, January 25, 2008 2:38 PM
Subject: Re: comet end event
I put up a war file at: http://www.nomad.org/comet_test.war.
I cant say implementing the
NIOConnector is a supported TC6 feature
Thanks
Martin
- Original Message -
From: "Peter Warren" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Friday, January 25, 2008 2:38 PM
Subject: Re: comet end event
> I put up a war file at: http
I put up a war file at: http://www.nomad.org/comet_test.war.
It includes the webapp, source for the comet servlet & client, and the
server.xml file. Let me know if I missed anything.
As I mentioned before, I've also used your cometgui.jar client and see
the end event generated when using it as w
even with your code, I wasn't able to replicate what you were seeing.
what I would need to see what's going on for you:
1. a war file with your comet server, and source code
2. a test client
3. your server.xml
Filip
Peter Warren wrote:
Thanks, Filip, for your time on this! I used your change
Thanks, Filip, for your time on this! I used your changes and still
get an END event. With your changes the client and socket are
definitely staying alive now. I stepped through the client code and
see the end event appear on the server as soon as I step through the
line that writes the 0crlfcrl
his list
are extremely responsive, patient, and helpful, and I really
appreciate it!
Hmm, in your test case did you set the HttpURLConnection to use
chunked transfers (setChunkedStreamingMode(...))? I find if I use
chunked transfers, the HttpURLConnection sends a "last chunk" messa
your test client is wrong,I've pasted in the correct one
only three changes
1. set the timeout so that the socket stays alive
2. keep reading data so that the socket stays alive
3. 0crlfcrlf as the last chunk
works as expected. to make a workable client, it should read until it
gets the last-ch
if (n > 0) {
> > System.out.println("Read " + n + " bytes: " + new
> > String(buf, 0, n) + " for session: "
> > + request.getSession(true).getId());
> > } else if (n < 0) {
>
cat Users List"
Sent: Tuesday, January 22, 2008 11:58 AM
Subject: Re: comet end event
> I'll take a look at this for you!
>
> Filip
>
> Peter Warren wrote:
> >> as I mentioned, the "last chunk" doesn't generate an END event, I
tried
> >>
this list
are extremely responsive, patient, and helpful, and I really
appreciate it!
Hmm, in your test case did you set the HttpURLConnection to use
chunked transfers (setChunkedStreamingMode(...))? I find if I use
chunked transfers, the HttpURLConnection sends a "last chunk" message
emely responsive, patient, and helpful, and I really
appreciate it!
Hmm, in your test case did you set the HttpURLConnection to use
chunked transfers (setChunkedStreamingMode(...))? I find if I use
chunked transfers, the HttpURLConnection sends a "last chunk" message
upon reading input from the ser
your responses. The contributors to this list
are extremely responsive, patient, and helpful, and I really
appreciate it!
Hmm, in your test case did you set the HttpURLConnection to use
chunked transfers (setChunkedStreamingMode(...))? I find if I use
chunked transfers, the HttpURLConnection sends
t
> > are extremely responsive, patient, and helpful, and I really
> > appreciate it!
> >
> > Hmm, in your test case did you set the HttpURLConnection to use
> > chunked transfers (setChunkedStreamingMode(...))? I find if I use
> > chunked transfers, the HttpURLConn
(...))? I find if I use
chunked transfers, the HttpURLConnection sends a "last chunk" message
upon reading input from the server, which generates a comet END event
on the server. If I don't use chunked transfers, no END event is
generated because no "last chunk" is sent by the c
, the HttpURLConnection sends a "last chunk" message
upon reading input from the server, which generates a comet END event
on the server. If I don't use chunked transfers, no END event is
generated because no "last chunk" is sent by the client.
Which brings up an option I
writes are possible, but they're not
when using HttpURLConnection because HttpURLConnection sends a "last
chunk" message when it's done with its request. "Last chunk"
generates a comet end event, which then requires that the connection
to the client be closed.
I gues
ent due to permission problems when trying to use sockets behind a
proxy.
I understand that asynchronous writes are possible, but they're not
when using HttpURLConnection because HttpURLConnection sends a "last
chunk" message when it's done with its request. "Last chunk"
o change my comet client to use HttpURLConnection
instead of Sockets. (Accessing ProxySelector from an applet to create
a socket with a proxy generates an AccessControlException.)
HttpURLConnection unfortunately sends a 0crlf when its input stream is
retrieved for reading. This generates a Com
ector from an applet to create
> > a socket with a proxy generates an AccessControlException.)
> >
> > HttpURLConnection unfortunately sends a 0crlf when its input stream is
> > retrieved for reading. This generates a Comet END event. Short of
> > closing the comet event, how can I mak
)
HttpURLConnection unfortunately sends a 0crlf when its input stream is
retrieved for reading. This generates a Comet END event. Short of
closing the comet event, how can I make the server stop notifying me
of END events? I can't close the comet event because I want to hold
onto the comet outpu
d for reading. This generates a Comet END event. Short of
closing the comet event, how can I make the server stop notifying me
of END events? I can't close the comet event because I want to hold
onto the comet output stream for use later to send data to the client.
>From the comet docs:
EventTy
37 matches
Mail list logo
