Re: Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is terminated
-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 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. Interesting. > *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? Dunno. 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk43SYQACgkQ9CaO5/Lv0PDBywCguWqxU8REeAWZ1nb3eoWpIn+k dq8AoILHO7wqmmFgBULZHtf4Rjsak9Xd =Fptp -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is terminated
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)). 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.* 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 Pradhan wrote: > Pid, > > I tried Tomcat 6.0.32.. no luck yet. Even ERROR event is not raised. Can you provide a simple example which exhibits this behaviour? > Also, I am seeing something weird (may not be related to this problem, but > think its worth mentioning). I am seeing stale response on a new connection > from curl. I validated this by changing the Accept Header from > application/xml to application/json, I get 1 response in xml format and then > the connection hangs. Then I do a Ctrl-C and re-try with json. I get the json > response. Are the request response object not recycled properly? What can be > the possible reason for this? What is stale? Take a thread dump when it hangs to see what the app is doing. p > Thanks, > Sudeep > > > -Original Message- > 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 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 is not cleaned >> up (I have connection registry for keeping track of clients). What can be >> the explanation for this scenario? >> >> Thanks, >> Sudeep > > > Are you able to upgrade to 6.0.32? There have been many fixes to the > NIO connector since 6.0.20 - not that this is necessarily your problem. > > Does the ERROR event fire when curl stops? > > > p > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is terminated
On 29/07/2011 18:33, Sudeep Pradhan wrote: > Pid, > > I tried Tomcat 6.0.32.. no luck yet. Even ERROR event is not raised. Can you provide a simple example which exhibits this behaviour? > Also, I am seeing something weird (may not be related to this problem, but > think its worth mentioning). I am seeing stale response on a new connection > from curl. I validated this by changing the Accept Header from > application/xml to application/json, I get 1 response in xml format and then > the connection hangs. Then I do a Ctrl-C and re-try with json. I get the json > response. Are the request response object not recycled properly? What can be > the possible reason for this? What is stale? Take a thread dump when it hangs to see what the app is doing. p > Thanks, > Sudeep > > > -Original Message- > 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 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 is not cleaned >> up (I have connection registry for keeping track of clients). What can be >> the explanation for this scenario? >> >> Thanks, >> Sudeep > > > Are you able to upgrade to 6.0.32? There have been many fixes to the > NIO connector since 6.0.20 - not that this is necessarily your problem. > > Does the ERROR event fire when curl stops? > > > p > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is terminated
Pid, I tried Tomcat 6.0.32.. no luck yet. Even ERROR event is not raised. Also, I am seeing something weird (may not be related to this problem, but think its worth mentioning). I am seeing stale response on a new connection from curl. I validated this by changing the Accept Header from application/xml to application/json, I get 1 response in xml format and then the connection hangs. Then I do a Ctrl-C and re-try with json. I get the json response. Are the request response object not recycled properly? What can be the possible reason for this? Thanks, Sudeep -Original Message- 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 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 is not cleaned > up (I have connection registry for keeping track of clients). What can be > the explanation for this scenario? > > Thanks, > Sudeep Are you able to upgrade to 6.0.32? There have been many fixes to the NIO connector since 6.0.20 - not that this is necessarily your problem. Does the ERROR event fire when curl stops? p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
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 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 is not cleaned > up (I have connection registry for keeping track of clients). What can be > the explanation for this scenario? > > Thanks, > Sudeep Are you able to upgrade to 6.0.32? There have been many fixes to the NIO connector since 6.0.20 - not that this is necessarily your problem. Does the ERROR event fire when curl stops? p - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomocat 6.0.20 Comet END Event *NOT RAISED* when connection is terminated
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 is not cleaned up (I have connection registry for keeping track of clients). What can be the explanation for this scenario? Thanks, Sudeep
