tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 42198] - Insufficient synchronization for CometEvent.close
Date Tue, 24 Apr 2007 23:05:37 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42198>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42198





------- Additional Comments From remm@apache.org  2007-04-24 16:05 -------
This should be posted on the user list.

I doubt what you described corresponds to what actually happens (with the
exception of write being a noop after closing the stream - it is the same in a
regular servlet).

If you are playing with the Connection header, the client could assume things
and abruptly close the connection. You should not be playing with the connection
state (it's also true in a regular servlet), but it should not make any
difference as long as the client does not get confused.

After the END event, it is clearly mentioned that the request is done, and
objects will be recycled, so it's up to you to stop doing things with that
request (if you want to code more freely, you should use
org.apache.catalina.connector.RECYCLE_FACADES set to true, which will avoid all
invalid accesses).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message