search for: mongrel_experimental

Hi, I wanted to try out Edge Rails 3 today and hit a serious problem trying to run mongrel. script/rails server mongrel just hangs. Interrupting and looking up the spot of the lockup revealed $LOAD_PATH.unshift ''projects/mongrel_experimental/lib/'' Mongrel::Gems.require ''mongrel_experimental'', ">=#{Mongrel::Const::MONGREL_VERSION}" at the bottom of mongrel.rb. This executes Mongrel::Gems.require which contains this wonderful ($%^##&#) infinite loop: begin # ActiveSupport breaks ''r...

......) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping, cgiwrapper...) * How many mongrel routes and handlers per route registered (if you don''t know, it''s probably <= 2) * Any Mongrel plugins used (mongrel_upload_progress, mongrel_gzip, mongrel_cow_cluster, mongrel_experimental...) * Mongrel runners used (mongrel_rails, mongrel::cluster, mongrel_service, RV, others... please be *very specific* about which options of the runner you use. For example, some people use mongrel::cluster but only for the --clean functionality, not for the clustering). * Number of mongrels per se...

I first tried a simple gem ''mongrel'' Then later the solution found here http://jan.varwig.org/archive/rails-3-and-mongrel gem "mongrel" gem "cgi_multipart_eof_fix" gem "fastthread" gem "mongrel_experimental" But still can''t get it to work... Anyone? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to ruby...

Hi all, 1.0.2 final will drop as soon as I get the win32 builds from Luis. Watch for it. In the future we won''t do RCs but will just make point releases, because no one really installed them except for ourselves. This is what Zed used to do and what we should have done all along. Note that the bug tracker is empty:

...b_init.rb ... Connecting to database... Thu, 13 Dec 2007 03:22:38 GMT: loading gem ''merb_activerecord'' from config/dependencies.rb:16 ... Loading Application... --- - /usr/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib - /home/francois/src/florian-opsdb/trunk/amara/lib - projects/mongrel_experimental/lib/ - /home/francois/src/florian-opsdb/trunk/amara/lib - /home/francois/src/florian-opsdb/trunk/amara/app/controllers - /home/francois/src/florian-opsdb/trunk/amara/app/models - /home/francois/src/florian-opsdb/trunk/amara/framework - /usr/lib/ruby/gems/1.8/gems/abstract-1.0.0/bin - /usr/lib/ruby/...

Hello Mongrels, Mongrel 1.1 is out with fullblown JRuby support, some reorganization, and some bugfixes. Also, Mongrel_cluster has been updated to 1.0.4. Go subscribe to the all-new news feed, because we probably won''t announce to the list anymore: http://mongrel.rubyforge.org/rss.xml Thanks Evan, and the Mongrel Team -- Evan Weaver Cloudburst, LLC

Hi Zed, I checked in a pure-Ruby URI classifier to Mongrel trunk. Ola''s Java port of the TST had some bug, and I don''t think it''s necessary in the first place. The Ruby classifier is around 25 lines instead of the 400-odd lines for the C extension and the 200-odd for the Java extension. It uses a Regexp which is perhaps shady: @matcher = Regexp.new(routes.map do

Hey so, People are asking about Mongrel Ruby 1.9 compatibility. Isn''t the point of 1.9 for library developers to have time to get ready for 2.0? It''s not like 1.9 is a production release. Evan -- Evan Weaver Cloudburst, LLC