tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is terminated
Date Tue, 02 Aug 2011 00:49:08 GMT
Hash: SHA1


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 you respond with LOTS more
information? Maybe a copy/paste of your terminal where you invoke curl
and kill the process.

> I am not seeing this behavior for HTTP. It occurs only for HTTPS.


> *Though the problem of END event not being raise still happens for 
> HTTP even with Tomcat 6.0.32.*

So, it happens for HTTP or HTTPS? Or both? Or only one under certain
circumstances? It's really hard to get a clear description, here.

> Is this a bug?


FWIW, I wouldn't expect to see curl receiving any responses from Tomcat
after you do a CTRL-C. That should send a SIGKILL to the process and
terminate it before it has a chance to tell the server it's
disconnecting. Tomcat may fire an END event that the client does not see.

You throw the term "console" around loosely... did you mean the
"console" where curl is running or the console where you are watching
some kind of log file on the server?

In neither circumstance would I expect you to see any evident of events:
if you're talking about killing the client, then the client does not see
any more events. If you are talking about killing the log file, then you
aren't looking at the log file anymore. *shrug*

- -chris

Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message