Task #3145
Story #2763: WebTester is unresponsive and seems to hang
remove out.close() from TestRunnerHttpServlet
Status:
Closed
Priority:
Normal
Assignee:
Category:
d1_integration
Target version:
Start date:
2012-08-17
Due date:
% Done:
100%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
common practice is not to call close, and I found speculation that a double-close() could cause tomcat thread handling issues.
http://stackoverflow.com/questions/1829784/should-i-close-the-servlet-outputstream.
removed as of revision 9946 of WebTester, with no harm.
History
#1 Updated by Rob Nahf about 12 years ago
- Target version changed from Sprint-2012.39-Block.5.4 to Sprint-2012.41-Block.6.1
#2 Updated by Rob Nahf about 12 years ago
- Target version deleted (
Sprint-2012.41-Block.6.1)
#3 Updated by Rob Nahf about 10 years ago
- Target version set to Maintenance Backlog
