Here's a first attempt at getting Process::Status working.- == not implemented- other methods not impled, but perhaps not necessary- We have obviously not used Process much up to now, but I added commented-out method defs for everything C Ruby supports
- need unit tests for Process::Status (likely
I think I found my issue...running under linux, the shell substitutes its own $? when the -e bit is double-quoted.[EMAIL PROTECTED]:~/testrails/test4$ ruby -e 'fork { exit 99 }; Process.wait; p $?.class'Process::Status
[EMAIL PROTECTED]:~/testrails/test4$ ruby -e "fork { exit 99 }; Process.wait; p
On Mon, 26 Jun 2006, Charles O Nutter defenestrated me:
>
>The plugin script fails (as perhaps do others) because we do not
>return a Process::Status object when executing an external process; we
>return a Fixnum.
>Process::Status defines a success? method which Rails is using. Th
Not as far as I can tell (and it would be a little weird anyway).On 6/26/06, Thomas E Enebo <[EMAIL PROTECTED]> wrote:
Is it possible that the fixnum in 1.8.4 has a success? method defined?-Tom
-- Charles Oliver Nutter @ headius.blogspot.comJRuby Developer @ www.jruby.orgApplication Architect @
Is it possible that the fixnum in 1.8.4 has a success? method defined?
-Tom
On Mon, 26 Jun 2006, Charles O Nutter defenestrated me:
>
>The plugin script fails (as perhaps do others) because we do not
>return a Process::Status object when executing an external process; we
>return a
The plugin script fails (as perhaps do others) because we do not return a Process::Status object when executing an external process; we return a Fixnum.Process::Status defines a success? method which Rails is using. That blows up with a NoMethodError, which Rails of course swallows.
The fix is to m
I will look at this tonight if it is not solved by then by some other
industrious person...
-Tom
On Mon, 26 Jun 2006, Nick Sieger defenestrated me:
>
> I've got things set up in my svn repo such that you pull down my
> ActiveRecord JDBC adapter as a Rails plugin. Although it appears that
> usi
I've got things set up in my svn repo such that you pull down my
ActiveRecord JDBC adapter as a Rails plugin. Although it appears that
using 'script/plugin' inside of JRuby may have some issues. So for
now, use C Ruby. Inside your Rails app, do:
ruby script/plugin install
http://svn.calderspher
Nevermind..it's still around. And I'm walking away from it NOW.On 4/13/06, Charles O Nutter <[EMAIL PROTECTED]
> wrote:Another FYI, making the CGI servlet single-threaded seemed to resolve the intermittent error.
On 4/13/06, Charles O Nutter <
[EMAIL PROTECTED]> wrote:FYI, this is running under To
Another FYI, making the CGI servlet single-threaded seemed to resolve the intermittent error.On 4/13/06, Charles O Nutter <
[EMAIL PROTECTED]> wrote:FYI, this is running under Tomcat
5.5.On 4/13/06, Charles O Nutter <
[EMAIL PROTECTED]> wrote:
Ok, I lied, it goes from 11 seconds down to about 2 s
FYI, this is running under Tomcat 5.5.On 4/13/06, Charles O Nutter <[EMAIL PROTECTED]> wrote:
Ok, I lied, it goes from 11 seconds down to about 2 seconds. Still, it shows how much overhead there is starting up Rails, and also shows that we're slow...but not molasses slow.Attached is a very ugly pat
Ok, I lied, it goes from 11 seconds down to about 2 seconds. Still, it shows how much overhead there is starting up Rails, and also shows that we're slow...but not molasses slow.Attached is a very ugly patch containing a CGI servlet and some JRuby hacks to support it. It seems to work pretty well,
I've got a "pseudo-FastCGI" servlet I'm playing with now...but it's
pretty canned and far from something real. However, it cuts the time to
make the /rails_info/properties request from ten seconds down to under
a second (on this 2.6G Opteron).I'll post it in a few minutes as food for thought.On 4/1
On Thursday 13 April 2006 07:06 pm, Charles O Nutter wrote:
> I know that perhaps some of you don't read my blog (for shame!) so I'll
> make a little announcement here too.
>
> Last night I successfully got Rails to handle a request running under
> JRuby. There were only a few additional fixes and
I know that perhaps some of you don't read my blog (for shame!) so I'll make a little announcement here too.Last night I successfully got Rails to handle a request running under JRuby. There were only a few additional fixes and tweaks necessary to make it work, along with wiring it up as a CGI (yea
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
19 matches
Mail list logo
