tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 53391] CometEvent.close() doesn't close socket when called from different thread
Date Mon, 11 Jun 2012 14:21:32 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53391

Mark Thomas <markt@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from Mark Thomas <markt@apache.org> ---
This report is invalid. event.close() does not close the socket in either case
a) nor case b). Nor should it. I have added some unit tests that confirm this
behaviour. I have also added a unit test that confirms setting the connection:
close header in the response does result in the connection being closed.

Without a test case that demonstrates otherwise, the most likely cause of the
behaviour described in this bug report is an application bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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


Mime
View raw message