Re: [xSocket-develop] xSocket 2.7 STILL swallowing exceptions

[Jonas M. <sa...@gm...>]

Any exception that comes from onData() , onConnect() etc is swallowed and
logged like this;

HandlerAdapter : [ae0c487b124ca0e078019bbf914S3] runtime exception occured
while performing onData multithreaded
com.ssb.swimmer2.SwimmerServer#24230975 java.lang.RuntimeException:
java.lang.IllegalMonitorStateException

What I expect to happen when my code throws a RuntimeException without
catching somewhere it is that it should terminate the application...



On Thu, Nov 5, 2009 at 4:12 PM, Gregor Roth <gre...@gm...> wrote:

> Hello Jonas,
>
>
> I will go through the code, looking for such places. It will be great, if
> you give me some input.
>
>
> Thanks
>
> Gregor
>
>
> ----- Original Message -----
>
> From: Jonas Minnberg
>
> Sent: 11/05/09 02:51 pm
>
> To: xso...@li...
>
> Subject: [xSocket-develop] xSocket 2.7 STILL swallowing exceptions
>
>
>
> My biggest gripe with xSocket is still there; that it catches all
> exceptions thrown in application code and just logs it as a warning.
> Why, o why is that so? It makes finding problems in your code so much
> harder, especially since it doesn't print the stack trace.
>
> // Jonas
>
>
>
>