Hi Bobby,
>> [...] We don't have anything in the web app that
>> does this directly, but we are using an ICEPush feature to push
>> changes to the user, and [...]
> Paying more attention to the logs now, I see these messages from
> ICEPush at startup:
>
> [#|2012-04-02T10:35:01.822-0400|INFO|glassfish3.1.2|org.icepush.servlet.EnvironmentAdaptingServlet|_ThreadID=21;_ThreadName=Thread-2;|Adapting
> to Servlet 3.0 AsyncContext environment|#]
>
> [#|2012-04-02T10:35:01.824-0400|INFO|glassfish3.1.2|org.icepush.servlet.AsyncAdaptingServlet|_ThreadID=21;_ThreadName=Thread-2;|Using
> Servlet 3.0 AsyncContext|#]
>
> [#|2012-04-02T10:35:01.865-0400|INFO|glassfish3.1.2|org.icepush.servlet.EnvironmentAdaptingServlet|_ThreadID=19;_ThreadName=Thread-2;|Adapting
> to Servlet 3.0 AsyncContext environment|#]
>
> [#|2012-04-02T10:35:01.866-0400|INFO|glassfish3.1.2|org.icepush.servlet.AsyncAdaptingServlet|_ThreadID=19;_ThreadName=Thread-2;|Using
> Servlet 3.0 AsyncContext|#]
>
> [#|2012-04-02T10:35:02.798-0400|INFO|glassfish3.1.2|org.icepush.servlet.EnvironmentAdaptingServlet|_ThreadID=22;_ThreadName=Thread-2;|Falling
> back to Thread Blocking environment|#]
>
> Does that "Falling back to Thread Blocking environment" mean that push
> isn't available by default in GF 3.1.2? This is starting to seem
> vaguely familiar.... Certainly "thread blocking" sounds like something
> that could cause a request to take more than 15 minutes. ;)
Looks like that. I wonder what's the reason to fallback to
thread-blocking...
Thanks.
WBR,
Alexey.