users@grizzly.java.net

grizzly in glassfish running on Amazon doesn't call onInterrupt every time after expiration delay

From: <sarmishev_at_netgear.com>
Date: Thu, 21 Feb 2013 00:47:03 +0000 (GMT)

We are running glassfish 2.1 on Amazon AWS cloud on the RedHat Linux
and using Grizzly 1.0.40 to serve our long polling requests. We are
using async IO and setup CometContext expiration delay to be 2 minutes.
That suppose to hit our onInterrupt handler every 2 minutes. We have
normal Grizzly 2 minutes onInterrupt call when running on our
development Ubuntu server but on Amazon RedhAT it is such non-regular
call for onInterrupt. Anybody has experience on running Grizzly on
Amazon? Any ideas what might be wrong?
More details
Here is a log from initialization
Grizzly 1.0.40 running on Linux-2.6.32-279.19.1.el6.x86_64 under JDK
version: 1.6.0_24-Sun Microsystems Inc.
         port: 8080
         socket-tcp-no-delay-enabled: true
         socket-keep-alive-enabled: false
         socket-linger: -1
         socket-oob-inline-enabled: false
         default-write-timeout-millis: 30000
         maxThreads: 1200
         ByteBuffer size: 4096
         useDirectByteBuffer: 8192
         maxKeepAliveRequests: 20000
         keepAliveTimeoutInSeconds: 60
         Static File Cache enabled: false
         Pipeline :
com.sun.enterprise.web.connector.grizzly.LinkedListPipeline
         Round Robin Selector Algorithm enabled: false
         Round Robin Selector pool size: 1
         Asynchronous Request Processing enabled: true|#]

Thankss,
-Sergey