JMX would be a perfect fit for this sort of management, but there's a lot more discussion and decisions to be made in this area. We're currently so focused on "JRuby SE" that the "JRuby EE" questions are not yet on the table.
I personally would love to make the future "JRuby VM" services JMX-aware,
On Mar 29, 2006, at 3:38 PM, Charles O Nutter wrote:
We've been planning to run Rails through a kind of "CGI Servlet"
that primes JRuby with appropriate environment for Rails to
execute, and then just pass requests right through (through BSF,
JSR223, and/or direct calls into the JRuby runti
We've been planning to run Rails through a kind of "CGI Servlet" that primes JRuby with appropriate environment for Rails to execute, and then just pass requests right through (through BSF, JSR223, and/or direct calls into the JRuby runtime). It should be fairly straightforward to map the incoming
I'm curious if there's been much thought+discussion about where
things go once the Rails scripts are running on JRuby ? Presumably
performance will limit the utility of a CGI-based model. Is the plan
to support a multithreaded FastCGI model, integrate with servlets
using JSR223, perhaps bot
