The server log is emitting:
"Starting Grizzly Framework 1.9.18-k"
When you look at this setting in the GlassFish Administration UI you see a
description that states, "The maximum amount of time that a thread can
remain idle in the pool. After this time expires, the thread is removed from
the pool."
This is not at all the behavior I observe in this case. The thread has been
assigned to the Jersey client request which is a long running request, its
not idle in a pool. Yet if the long running process being run by this thread
exceed this timeout value GF send it an interrupt.
So either this is a bug or the documentation needs to correctly describe
what this value means.
Thnx,
-Noah
On Tue, Aug 3, 2010 at 11:21 AM, Oleksiy Stashok <Oleksiy.Stashok_at_sun.com>wrote:
> Strange, the timeout we're discussing here should be controlled by:
> <http request-timeout-seconds="..." >
>
> Can you pls. check in the domain.xml the Grizzly version, which is used?
> Search for the line containing "Starting Grizzly Framework".
>
> Thank you.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>