https://bz.apache.org/bugzilla/show_bug.cgi?id=59398
james.s...@metaswitch.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #2 from james.s...@metaswitch.com ---
Thanks for the suggestion. Moving to the NIO connector does get us round this
issue but we hit https://bz.apache.org/bugzilla/show_bug.cgi?id=58646 and while
we could upgrade to tomcat 8.0.33 to fix this we're nervous about switching
from the APR connector to NIO connectors as we moved to APR for performance
reasons and at the stage we're at in our release cycle we can't change this.
It does feel like there is a fairly straight forward issue in tomcat though as
calling close on a PrintWriter twice should succeed, and shouldn't throw an
exception, as this is the documented behaviour.
(Also I don't feel like the fact that this is difficult to fix makes it
'invalid'... possibly it won't get fixed but we're not doing anything that
shouldn't be supported in tomcat as it's currently documented)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
