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 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 client with the 50 ms sleep?  The client code has a
commented block that says: uncomment sleep to get END event instead of
read error.  Adding the sleep generates the end event for me.

Also, did you try with your cometgui client?  As I mentioned,
submitting a chunk and then separately submitting an end chunk
generates an end event for me.  If I send the two chunks together, I
get the read error.

Peter

On Jan 28, 2008 1:37 PM, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
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: BEGIN, subtype: null
event: READ, subtype: null
Read 10 bytes: comet test for session: D4BC1A6D7AC7F30C1A475FB7FFB2B4DB
read error
event: ERROR, subtype: TIMEOUT

If you are unsure if you have messed up Tomcat binaries, then I would
test this one
http://people.apache.org/~fhanik/tomcat/tomcat-5.5/v5.5.26/bin/

these are not an official version, but you can test it out and see how
your test works

Filip


Peter Warren wrote:
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 well.  If I submit a chunk
and the last chunk (0crlfcrlf) together, I see a read error on the
server.  If I submit a chunk and then submit the last chunk in two
separate submissions, I see an end event on the server.

Peter

On Jan 24, 2008 12:44 PM, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:

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


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to