https://bz.apache.org/bugzilla/show_bug.cgi?id=63879
--- Comment #6 from Michael Bazos <michael.ba...@priceline.com> --- I agree switching to TRACE is the best option. Also it might be helpful to not throw new Exception(); as this produces this message "java.lang.Exception: null" If you are going to have this it might be best to provide a message to let people know this is intended and testing. This issue came up as it was forwarded to me by another team at my company and my response was it's fine it's `DEBUG` but I also feel seeing a stack trace like this can clue to some potential issue happening or maybe something not being done in an optimal way. Either way I think checking the rest of the code base in NIO and NIO2 for this pattern and switching the statements to TRACE at a minimum should be fine. -- 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
