Mark,
Just looking at the warning message I can say what really might be going
on. Perhaps someone from grizzly team can comment on this particular issue.
In the meantime can you give the latest glassfish gem (not released yet)
a try? It will be released soon after more testing but it has latest
stable Grizzly and glassfish v3 kernel bits. I think its worth a try.
Get build#120 from
http://hudson.glassfish.org/job/glassfish-gem-build/.
If the latest gem does not fix your problem, can you send the thread
dump? kill -QUIT pid or ctrl + \
-vivek.
Mark Westling wrote:
> I'm running my Rails project using the Glassfish v3 gem and if there's
> no activity for an hour or two hours, the next request hangs and logs
> the following error:
>
> Nov 11, 2009 3:15:44 AM com.sun.grizzly.config.GrizzlyServiceListener
> WARNING: Interrupting idle Thread: http80-WorkerThread(0)
>
> I'm using the default parameters in the glassfish.yml configuration
> file. This occurs in both daemon and non-daemon mode. The only
> unusual thing I might be doing is creating (and closing) several
> processing threads during some requests to take advantage of multiple
> cores for lengthy computations, but the problem seems to occur even if
> I don't run any thread-creation processes after a restart. In other
> words, I can restart glassfish, wait a few hours with no requests, and
> see the same error.
>
> Configuration:
> jruby 1.4.0 (ruby 1.8.7 patchlevel 174) (2009-11-02 69fbfa3) (Java
> HotSpot(TM) Client VM 1.6.0_18-ea) [i386-java]
> rails 2.3.3
> glassfish gem 0.9.5
> database adapter: jdbcmysql
> Linux version 2.6.18-164.el5PAE
> (mockbuild_at_x86-002.build.bos.redhat.com
> <mailto:mockbuild_at_x86-002.build.bos.redhat.com>) (gcc version 4.1.2
> 20080704 (Red Hat 4.1.2-46)) #1 SMP
>
> Any suggestions?
>
> --Mark
>