users@grizzly.java.net

Re: Grizzly 2.0 - big exception stack trace when force disconnect at client

From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Thu, 28 May 2009 10:32:58 +0200

Hi Ken,

the long exception is caused by RerunChainAction, returned from
postExecute.
I'll need to improve this, to not make stacktrace grow, but otherwise
it's ok.
Can you pls. file the issue?

Thanks.

WBR,
Alexey.

On May 28, 2009, at 9:47 , Ken--_at_newsgroupstats.hk wrote:

>
> Is it normal?
>
> http://www.nabble.com/file/p23756797/bigstacktrace.txt
> bigstacktrace.txt
>
> http://www.nabble.com/file/p23756797/EchoMessageFilter.java
> EchoMessageFilter.java
>
>
> --
> View this message in context: http://www.nabble.com/Grizzly-2.0---big-exception-stack-trace-when-force-disconnect-at-client-tp23756797p23756797.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>