On Sat, Apr 24, 2010 at 1:30 AM, Edwin Shin <[email protected]> wrote: > > I was able to duplicate the error you saw, using rvm to run 1.8.7- > p249. I was running the ruby that ships with Snow Leopard (1.8.7- > p173). What I don't understand is that using the system ruby, I can't > duplicate the error. > > $ rvm system && ruby -v > ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] > > but using rvm with either p249 or p173, I can reproduce the 500 you > reported. For example: > $ rvm 1.8.7-p173 && ruby -v > ruby 1.8.7 (2009-06-08 patchlevel 173) [i686-darwin10.3.0] > > Same 500 error. > > If I switch back to system (rvm system), I get the error I originally > reported, not the 500. > > I've only started using rvm since today (after reading your post about > jetty-rackup) so I've not seen this 500 error before.
Hello Edwin, I gave it a try this morning. I wanted to determine which file triggered the "bad descriptor" in my 500 log. I decorated the error emitting the bad descriptor exception to let it tell which file is the culprit instead of dumbly saying "the here is something wrong with a gem". But not success. Apr 24, 2010 11:47:23 AM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive _ruote.war Gemfile changed since you last locked. Please run `bundle lock` to relock. Maybe it's not happy I tampered with jruby-stdlib-1.4.0.jar. I could try this lock trick inside of the unpacked _ruote/ This is pain. I have other work scheduled for the week-end. I can't do much for now. Best regards, John -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
