search

google-code-export / rocket-gwt

Automatically exported from code.google.com/p/rocket-gwt
1 stars 1 forks source link

Use logger instead of printStackTrace to syso. #56

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Break comet connection (e.g. shutdown browser)

What is the expected output? What do you see instead?
This is a normal situation and shouldn't cause printStackTrace-s on the
syso. This makes logs more difficult to read and hides real problems.
Currently print stack traces are done in methods of InputOutput and in
CometServerServlet.doGet.

What version of the product are you using? On what operating system?
Rocket 0.56

Original issue reported on code.google.com by Marcin.A...@gmail.com on 18 Nov 2008 at 1:46

GoogleCodeExporter commented 9 years ago 
Do you mean you want the stack trace dumps removed ?

Original comment by miroslav...@gmail.com on 2 Dec 2008 at 8:34

GoogleCodeExporter commented 9 years ago 
yes, or replaced with logger statements (e.g. log4j) so that it is possible to 
turn
them off - as these happen during normal system operation and should not be 
treated
as real errors - reading log files is a bit tough now as there are lots of stack
trace dumps which are not real errors.

Original comment by Marcin.A...@gmail.com on 2 Dec 2008 at 12:00