Summary: | Comet over HTTPS: END event recieved immeidately for the first few times | ||
---|---|---|---|
Product: | Tomcat 6 | Reporter: | Sudeep Pradhan <pradhans> |
Component: | Connectors | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | P2 | ||
Version: | 6.0.20 | ||
Target Milestone: | default | ||
Hardware: | PC | ||
OS: | Linux | ||
Attachments: | Source in TomcatCometHttps.tar.gz and conf in server-conf.tar.gz packaged in the uploaded tar.gz |
Description
Sudeep Pradhan
2011-07-15 21:59:52 UTC
I have tested this with the latest Tomcat 7.0.x code and it works as expected. A couple of notes for folks trying to use this test case. 1. It assumes it is running from within VMware's internal network so (unless you fancy changing employers) you'll need to remove the proxy info from Weatherman.java 2. It has a couple of dependencies you can just remove rather than spend time tracking down. If testing on Tomcat 7, remember that the Comet classes moved packages. On to testing with the latest 6.0.x OK, I do see errors on first access (although not quite the same) on 6.0.x. I'm investigating now. In the meantime, an upgrade to 7.0.19 should fix this for you. I have a patch that fixes this for 6.0.x. I have proposed this patch for the next 6.0.x release. Mark, Can I have the patch so that I can test it? Thanks, Sudeep (In reply to comment #4) > Can I have the patch so that I can test it? See STATUS.txt in the root of tc6.0.x source tree. A patch was "proposed" means that it has been added to the status file. The patch fixes the problem mentioned in the bug. There is another problem, END event is not raised when the client closes the connection abruptly. e.g. Ctrl-C on terminal running curl http client. Is this another bug? Fixed in 6.0.x and will be included in 6.0.33 onwards. |