Rails - Dec 2005 - XP Apache FastCGI ok if RAILS_ENV="", crash when RAILS_ENV="production"

Dears,

Thanks to Demetrius (dema.ruby.com.br, see Taming FastCGI) I''ve a
running FastCGI  Rails 1.0 environment with :

- Win XP "Professional" (just brand name)
- Apache 2.0.55 (msi)
- Ruby for Apache 1.3.1
- Database backend is now Oracle 8.1

Everything run fine with default environment, I''m confused for
switching into ''production''.

By default RAILS_ENV is null, and my env is like explained by Deme :

FastCgiConfig -maxClassProcesses 1 -MaxProcesses 1 -minProcesses 1
-processSlack 1 \
  -initial-env PATH="c:/ruby/bin;C:/oracle/ora817/bin;[snip]
  -initial-env RUBYOPT=rubygems \
  -initial-env
MAGICK_CONFIGURE_PATH=C:/ruby/lib/ruby/gems/1.8/gems/RMagick-win32-1.9.2-mswin32/config

Also tried to add more process values.

This setup works fine, Webrick works fine also in -e production

By adding :
\
-initial-env RAILS_ENV="production"

Apache is going to moon by filling error log (cpu 100%) with messages like :


[notice] Child 196: Listening on port 80.
[warn] FastCGI: (dynamic) server ../public/dispatch.fcgi" started (pid
1004)
[warn] FastCGI: (dynamic) server /public/dispatch.fcgi" started (pid 2812)
FastCGI: scheduled the start of the last (dynamic) server
/public/dispatch.fcgi" process: reached dynamicMaxClassProcs (3)
[warn] FastCGI: (dynamic) server public/dispatch.fcgi" (pid 1004)
terminated with exit with status ''1''
[warn] FastCGI: (dynamic) server /public/dispatch.fcgi" (pid 2812)
terminated with exit with status ''1''
[warn] FastCGI: (dynamic) server /public/dispatch.fcgi" restarted (pid
3580)
[warn] FastCGI: (dynamic) server /public/dispatch.fcgi" (pid 3580)
terminated with exit with status ''1''
[warn] FastCGI: (dynamic) server /public/dispatch.fcgi" restarted (pid 624)
[warn] FastCGI: (dynamic) server /public/dispatch.fcgi" (pid 624)
terminated with exit with status ''1''

and plenty of :

[warn] FastCGI: (dynamic) server /public/dispatch.fcgi" has failed to
remain running for 30 seconds given 3 attempts, its restart interval
has been backed off to 600 seconds


Thanks,
Mathieu