I personally would love to make the future "JRuby VM" services JMX-aware, so they can be hooked up and managed just like other JMX services. The thread scheduler is an easy match, as would be a possible asynchronous IO subsystem and DRb remoting services. There's a lot of cool stuff we could bring to Ruby.
On 3/29/06, Marc Hadley <[EMAIL PROTECTED]> wrote:
On Mar 29, 2006, at 3:38 PM, Charles O Nutter wrote:
> As for your second paragraph, I'm sure there are options available.
> When I last rewrote the threading subsystem and starting thinking
> about m:n threading, I realized that we'll also want to be able to
> provide a container-managed thread pool for JRuby to execute under
> and provide management capabilities for the JRuby thread scheduler
> itself. Those two items should provide better support for "killing
> off" a bad Rails request running in JRuby.
Were you thinking of using the new JMX stuff in Java SE 5.0 for that ?
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
