"JRuby runtime management and pooling is done automatically by the
framework. In the case of Rails, runtimes are pooled. For Merb and other
Rack applications, a single runtime is created and shared for every
I just want to make sure that I understand this statement and its
implications for a Merb app.
Does this mean that a new Java thread is spun up for each request into
the Merb app.?
When do those threads go away?
What would it take to allow for JRuby runtime pooling for Merb apps. as
is (apparently) already done for Rails apps.?
To unsubscribe from this list, please visit: