Hmm. That isn't the signal processing. It seems that thread still lives, which is why Java won't shut down. I'm not sure if my evaluation of the block in the new thread actually completes, or maybe leaves the other thread hanging? Could you take a look, when you have the time? I've probably not done it completely correct, now that I think about it. The right way would have been to create a new RubyThread and use that... =/
/O At 18:18 2006-06-16, you wrote: >I had the following issue under linux with all the recent patches applied. > >When I tried to C-c out of webrick, I saw this and then it sat there: > >[2006-06-16 11:14:09] INFO going to shutdown ... > >When I C-z'ed it and forcibly killed it, it output this: > >[2006-06-16 11:16:33] INFO WEBrick::HTTPServer#start done. > >Perhaps the Signal stuff is interfering with the normal teardown of Java? >I have not tried without, and I have to move on to real work now... > >-- >Charles Oliver Nutter @ <http://headius.blogspot.com>headius.blogspot.com >JRuby Developer @ <http://jruby.sourceforge.net>jruby.sourceforge.net >Application Architect @ <http://www.ventera.com>www.ventera.com >_______________________________________________ >Jruby-devel mailing list >Jruby-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/jruby-devel _______________________________________________ Jruby-devel mailing list Jruby-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jruby-devel
