similar to: Mongrel Pre-Release 0.3.13 -- Katana Suicide Concurrency

Hello Everyone, Francois Simond inadvertently found a way to replicate a rare but deadly bug right as I was working up the official release of Mongrel 0.3.13. This bug only happened to a few people, but thanks to the wonderful fuzzing tool Apache Bench[1] he could replicate the slow select starvation people were seeing. TESTING This bug is now fixed in the current pre-release, and I''d

Hi Zed or anyone that is also looking at Mongrel, Just want to report something that, although doesn''t crash mongrel, is rather annoying. I am running the latest Mongrel 0.3.13.3 - ruby version on cygwin (yeah, poor me). When I start mongrel_rails with ActiveRecord::Base.allow_concurrency = true in environment.rb, I see a lot of "Error sending file

Hello all, Are you aware of the rails ActionController::Base.allow_concurrency option ? If this option is true, rails is able to process simultaneous multiples actions. It appears that rails is thread-safe (if the user application is), and that this option is mostly unknown. Webrick take care of this option in rails-1.1.2/lib/webrick_server.rb at line 80 : REQUEST_MUTEX.lock unless

Hi, I just found something weird for mongrel with static files. Performance endlessly decreases if mongrel serve static files from simultaneous requests : Here is the test setup: Ruby on Rails Mongrel (tested with 1.3.12.4 and 1.3.13-pre installed today) Ubuntu dapper, compiled ruby 1.8.4. http client : while true; do ab -n 1000 -c 30 http://localhost:3000/ 2>/dev/null | grep

Hi. I''m trying to authenticate users against database''s user/roles (PostgreSql), instead use an almighty user set in database.yml Can i use ActiveRecord::Base.establish_conection() method? And is this related whit ActiveRecord::Base.allow_concurrency = true and ActiveRecord::Base.verify_active_connections? I know about issues related with this point (Katana Suicide Concurrency),

Hello Zed ! Do you knows or plan a way to spawn mongrel processes on demand ? I''m studying options to build an affordable but solid shared hosting solution. You wrote something very promising in your "NEXT STEPS", A combination of the ''"mostly C version'' and the mongrel_cluster replacement would be an elegant method to save much RAM on servers (until

Hello Zed ! I''ve experimented a simple but limited performance tweak in the mongrel rails loader. With the following apache 2.2 mod proxy loadbalancer setup : # Redirect all non-static requests to cluster RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L] We can assume that mongrel is called only when the

Hello Windows Users! I have finally got my new computer with it''s win32 build working and have just done the first pre-release for 0.3.13 that has win32 support. *** All win32 users should try to grab the pre-release and tell me if it works. *** You can install it with: $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ >From EITHER win32 or any other platform

Hey Folks, I''ve been holding off the official 0.3.13 release so that Luis can get the win32 side very nice and clean. We fixed a major problem last night so it''s only a short time before we get it out. Luis is working really hard on it, so just be patient. In the meantime, I''ve been doing a code audit of the Mongrel code as it is now and fixing any little things I

Just a quick note for a few new features/fixes available on the Mongrel pre-release and a new document that covers nearly all the big features and configurations for Mongrel. First, the document is http://mongrel.rubyforge.org/docs/howto.html and it covers: * All the start command options including the fresh -G option to generate a config for -C. * The format and usage of the MIME type file (-m

Hello Mongrel Fans, After about a Month of busy work, bad computers, moving half my house across the country, and other dramas, I''m finally pushing out the next release of Mongrel. This pre-release has lots of little goodies and the start of some documentation that should get everyone primed for the big "Mongrel 0.4 Enterprisey Edition 1.2" coming real soon now. INSTALLING

Finally! I''ve released Mongrel 0.3.13 OFFICIALLY to the public for better or worse. This release is pretty huge compared to previous releases. It''s got oodles of fixes, design improvements, hosting enhancements, win32 changes, and the release even works with the latest cygwin. Read all about it at http://mongrel.rubyforge.org/news.html GETTING 0.3.13 Most people do this:

Hi Folks, This is another pre-release announcement with lots of goodies for people to test and play with. At this rate the 0.3.13 release may just turn into 0.4. GETTING IT Pretty simple, just gem install mongrel --source=http://mongrel.rubyforge.org/releases/ You can get more information at http://mongrel.rubyforge.org/ WHAT''S IN IT This release has lots of little things, mostly

I am currently experiencing concurrency issues after moving from MySQL to SQLite. My original program worked fined using MySQL but is now returning "SQLite3::BusyException" errors. The same result happens whether or not I enable the allow_concurrency flag. If I do manually acquire a lock on the SQLite DB the problem would disapear, but I thought that rails was supposed to handle this

Just a quick note for a few new features/fixes available on the Mongrel pre-release and a new document that covers nearly all the big features and configurations for Mongrel. First, the document is http://mongrel.rubyforge.org/docs/howto.html and it covers: * All the start command options including the fresh -G option to generate a config for -C. * The format and usage of the MIME type file (-m

Hey, I have just a few observations to report about the new version of Mongrel (0.3.13) on Win32. 1. When installing a new service, I have to use -N instead of -n to set the name of my app. The help file (-h option) has this right but the examples and such on the website all use -n. 2. The website documentation on the Win32 howto lists service::delete as a command but it should be

Hi, I use Mongrel to serve my Rails applications on my server, but how can I serve more than one application with one mongrel server? Thanks. -jec -- Best regards / Salutations. Jean-Eric Cuendet Senior developer / Technical support Riskpro Technologies SA Av. Louis-Ruchonnet 2 CH-1003 Lausanne Switzerland Direct : +41 21 637 0123 Principal : +41 21 637 0110 Fax : +41 21 637 0111

Hi, I''m trying to use mongrel 0.3.13 with Rail 1.0 Believe it or not, on OS/X it works well for weeks at a time. On linux I''m getting Input/output errors after anything from a few hours to days, never more than a week. Once they start they don''t stop. The only pattern I''ve seen is that it always (seems) to happen while rendering an rhtml file.

Hi guys, I have a funny problem that only occurs in FF1.0.x but works fine and dandy in FF1.5. I''d thought its me screwing up with the JS... but even this " What time is it <http://www.onlamp.com/pub/a/onlamp/2005/06/09/rails_ajax.html>" doesn''t work with until I downgrade to Mongrel 0.3.12.4. I don''t like/use FF1.0 too.. but too bad for me

Hi, On os x.3.9, with ruby 1.8.4 installed through darwinports and mongrel through gems, everything works until I restart: mongrel_rails restart adds the logs: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails start -p 3001 -d /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13/bin/mongrel_rails:134: in