search

tiger154 / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
1 stars 0 forks source link

Exception stack trace option #142

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Can we please have a choice about whether to print the exceptions stack trace 
or not?

The other day I got an exception that simply told me there was a problem with 
FastMap but it contained no information as to where exactly. So I had to go and 
replace one by one and restart the server every time in order to find the one 
place where the problem was.

Original issue reported on code.google.com by antiteis...@googlemail.com on 15 Nov 2011 at 2:39

GoogleCodeExporter commented 9 years ago 
Any news on this bug?

I am currently stuck with this message:
2011-11-26 19:23:31,044 ERROR - TCPConnector$ClientProcessor: 
NullPointerException in processPacket of connector TCPConnector: null

And without a stack-trace I have no idea where the problems is nor how to fix 
it.

Original comment by stojadin...@gmail.com on 26 Nov 2011 at 6:26

GoogleCodeExporter commented 9 years ago 
I managed to solve the problem by wrapping the entire code in my own 
WebSocketServerTokenListener implementations processToken method into a single 
try/catch block with ex.printStackTrace();

Original comment by stojadin...@gmail.com on 26 Nov 2011 at 7:12