passenger 3.0.14 → 3.0.15

data/doc/Users guide Apache.idmap.txt

@@ -124,81 +124,93 @@
 
 5.10. PassengerBufferResponse <on|off>	=>	passengerbufferresponse-on-off--1y7ilka
 
-5.11. Security options	=>	security-options-1pb75ho
+5.11. PassengerRollingRestarts <on|off>	=>	passengerrollingrestarts
 
-5.11.1. PassengerUserSwitching <on|off>	=>	passengeruserswitching-on-off--100dc63
+5.12. PassengerResistDeploymentErrors <on|off>	=>	passengerresistdeploymenterrors
 
-5.11.2. PassengerUser <username>	=>	passengeruser-username--iw6865
+5.13. Security options	=>	security-options-1pb75ho
 
-5.11.3. PassengerGroup <group name>	=>	passengergroup-group-name--1ciwtix
+5.13.1. PassengerUserSwitching <on|off>	=>	passengeruserswitching
 
-5.11.4. PassengerDefaultUser <username>	=>	passengerdefaultuser-username--nbjs8w
+5.13.2. PassengerUser <username>	=>	passengeruser
 
-5.11.5. PassengerDefaultGroup <group name>	=>	passengerdefaultgroup-group-name--1xwd1xj
+5.13.3. PassengerGroup <group name>	=>	passengergroup
 
-5.11.6. PassengerFriendlyErrorPages <on|off>	=>	passengerfriendlyerrorpages-on-off--rdq45f
+5.13.4. PassengerDefaultUser <username>	=>	passengerdefaultuser
 
-5.12. Resource control and optimization options	=>	resource-control-and-optimization-options-zu2f7u
+5.13.5. PassengerDefaultGroup <group name>	=>	passengerdefaultgroup
 
-5.12.1. PassengerMaxPoolSize <integer>	=>	passengermaxpoolsize-integer--am64q8
+5.13.6. PassengerFriendlyErrorPages <on|off>	=>	passengerfriendlyerrorpages
 
-5.12.2. PassengerMinInstances <integer>	=>	passengermininstances-integer--wegq6b
+5.14. Resource control and optimization options	=>	resource-control-and-optimization-options-zu2f7u
 
-5.12.3. PassengerMaxInstancesPerApp <integer>	=>	passengermaxinstancesperapp-integer--1pteawn
+5.14.1. PassengerMaxPoolSize <integer>	=>	passengermaxpoolsize-integer--am64q8
 
-5.12.4. PassengerPoolIdleTime <integer>	=>	passengerpoolidletime-integer--a3gunq
+5.14.10. PassengerPreStart <url>	=>	passengerprestart-url--1dvgku9
 
-5.12.5. PassengerMaxRequests <integer>	=>	passengermaxrequests-integer--ietgd0
+5.14.11. PassengerHighPerformance <on|off>	=>	passengerhighperformance-on-off--zgc547
 
-5.12.6. PassengerStatThrottleRate <integer>	=>	passengerstatthrottlerate-integer--13zx4xo
+5.14.2. PassengerMinInstances <integer>	=>	passengermininstances-integer--wegq6b
 
-5.12.7. PassengerPreStart <url>	=>	passengerprestart-url--1v76tcz
+5.14.3. PassengerMaxInstances <integer>	=>	passengermaxinstances
 
-5.12.8. PassengerHighPerformance <on|off>	=>	passengerhighperformance-on-off--36mw1l
+5.14.4. PassengerMaxInstancesPerApp <integer>	=>	passengermaxinstancesperapp
 
-5.13. Compatibility options	=>	compatibility-options-8jve5a
+5.14.5. PassengerPoolIdleTime <integer>	=>	passengerpoolidletime-integer--a3gunq
 
-5.13.1. PassengerResolveSymlinksInDocumentRoot <on|off>	=>	passengerresolvesymlinksindocumentroot-on-off--vblz7e
+5.14.6. PassengerMaxRequests <integer>	=>	passengermaxrequests
 
-5.13.2. PassengerAllowEncodedSlashes <on|off>	=>	passengerallowencodedslashes-on-off--1ud9a92
+5.14.7. PassengerMaxRequestTime <seconds>	=>	passengermaxrequesttime-seconds--7qnz3x
 
-5.14. Logging and debugging options	=>	logging-and-debugging-options-el2cuc
+5.14.8. PassengerMemoryLimit <integer>	=>	passengermemorylimit
 
-5.14.1. PassengerLogLevel <integer>	=>	passengerloglevel-integer--1lt2yhq
+5.14.9. PassengerStatThrottleRate <integer>	=>	passengerstatthrottlerate
 
-5.14.2. PassengerDebugLogFile <filename>	=>	passengerdebuglogfile-filename--pgj55c
+5.15. Compatibility options	=>	compatibility-options-8jve5a
 
-5.15. Ruby on Rails-specific options	=>	ruby-on-rails-specific-options-1t10wfu
+5.15.1. PassengerResolveSymlinksInDocumentRoot <on|off>	=>	passengerresolvesymlinksindocumentroot-on-off--1r0qcp8
 
-5.15.1. RailsAutoDetect <on|off>	=>	railsautodetect-on-off--tpigsd
+5.15.2. PassengerAllowEncodedSlashes <on|off>	=>	passengerallowencodedslashes-on-off--1y3s1ww
 
-5.15.2. RailsBaseURI <uri>	=>	railsbaseuri-uri--1txrw3k
+5.16. Logging and debugging options	=>	logging-and-debugging-options-el2cuc
 
-5.15.3. RailsEnv <string>	=>	railsenv-string--1b0xxvu
+5.16.1. PassengerLogLevel <integer>	=>	passengerloglevel-integer--1v67p8l
 
-5.15.4. RailsFrameworkSpawnerIdleTime <integer>	=>	railsframeworkspawneridletime-integer--1ai8dgq
+5.16.2. PassengerDebugLogFile <filename>	=>	passengerdebuglogfile-filename--1tfy4z9
 
-5.15.5. RailsAppSpawnerIdleTime <integer>	=>	railsappspawneridletime-integer--1awgog1
+5.16.3. PassengerDebugger <on|off>	=>	passengerdebugger-on-off--1lgdk7g
 
-5.16. Rack-specific options	=>	rack-specific-options-wk9qzt
+5.17. Ruby on Rails-specific options	=>	ruby-on-rails-specific-options-1t10wfu
 
-5.16.1. RackAutoDetect <on|off>	=>	rackautodetect-on-off--vl1lxy
+5.17.1. RailsAutoDetect <on|off>	=>	railsautodetect-on-off--tpigsd
 
-5.16.2. RackBaseURI <uri>	=>	rackbaseuri-uri--1to24pj
+5.17.2. RailsBaseURI <uri>	=>	railsbaseuri-uri--1txrw3k
 
-5.16.3. RackEnv <string>	=>	rackenv-string--vve9py
+5.17.3. RailsEnv <string>	=>	railsenv-string--1b0xxvu
 
-5.17. Deprecated options	=>	deprecated-options-pm9m57
+5.17.4. RailsFrameworkSpawnerIdleTime <integer>	=>	railsframeworkspawneridletime-integer--1ai8dgq
 
-5.17.1. RailsRuby	=>	railsruby-ht09ei
+5.17.5. RailsAppSpawnerIdleTime <integer>	=>	railsappspawneridletime-integer--1awgog1
 
-5.17.2. RailsUserSwitching	=>	railsuserswitching-1npx8y4
+5.18. Rack-specific options	=>	rack-specific-options-wk9qzt
 
-5.17.3. RailsDefaultUser	=>	railsdefaultuser-19j7n3m
+5.18.1. RackAutoDetect <on|off>	=>	rackautodetect-on-off--vl1lxy
 
-5.17.4. RailsAllowModRewrite	=>	railsallowmodrewrite-1vkziro
+5.18.2. RackBaseURI <uri>	=>	rackbaseuri-uri--1to24pj
 
-5.17.5. RailsSpawnMethod	=>	railsspawnmethod-1aljgpa
+5.18.3. RackEnv <string>	=>	rackenv-string--vve9py
+
+5.19. Deprecated options	=>	deprecated-options-pm9m57
+
+5.19.1. RailsRuby	=>	railsruby-ht09ei
+
+5.19.2. RailsUserSwitching	=>	railsuserswitching-1npx8y4
+
+5.19.3. RailsDefaultUser	=>	railsdefaultuser-19j7n3m
+
+5.19.4. RailsAllowModRewrite	=>	railsallowmodrewrite-1vkziro
+
+5.19.5. RailsSpawnMethod	=>	railsspawnmethod-1aljgpa
 
 5.2. PassengerRuby <filename>	=>	passengerruby-filename--1r3fv73
 
@@ -270,6 +282,8 @@
 
 7.4. Accessing individual application processes	=>	accessing-individual-application-processes-1p0j4jb
 
+7.5. Attaching an IRB console to an application process	=>	attaching-an-irb-console-to-an-application-process-1cma32j
+
 8. Tips	=>	tips-19cwwf7
 
 8.1. User switching (security)	=>	user-switching-security--8njx1x

data/doc/Users guide Apache.txt

@@ -980,6 +980,72 @@ The <<PassengerBufferResponse,PassengerBufferResponse>> directive should be turn
 if responses can be huge. Because entire responses are buffered in memory when turned on.
 =====================================================
 
+[[PassengerRollingRestarts]]
+=== PassengerRollingRestarts <on|off> ===
+**Available in Phusion Passenger Enterprise since version 3.0.0.**
+
+Enables or disables support for rolling restarts. Normally when you
+restart an application (by touching restart.txt), Phusion Passenger would
+shut down all application processes and spawn a new one. The spawning
+of a new application process could take a while, and any requests that
+come in during this time will be blocked until this first application
+process has spawned.
+
+But when rolling restarts are enabled, Phusion Passenger Enterprise will:
+
+1. Spawn a new process in the background.
+2. When it's done spawning, Phusion Passenger Enterprise will replace one of the old processes with this newly spawned one.
+3. Step 1 and 2 are repeated until all processes have been replaced.
+
+This way, visitors will not experience any delays when you are restarting your application. This allows you to, for example, upgrade your application often without degrading user experience.
+
+Rolling restarts have a few caveat however that you should be aware of:
+
+- Upgrading an application sometimes involves upgrading the database schema.
+  With rolling restarts, there may be a point in time during which processes
+  belonging to the previous version and processes belonging to the new version
+  both exist at the same time. Any database schema upgrades you perform must
+  therefore be backwards-compatible with the old application version.
+- Because there's no telling which process will serve a request, users may
+  not see changes brought about by the new version until all processes have
+  been restarted. It is for this reason that you should not use rolling
+  restarts in development, only in production.
+
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+ * In a `<Directory>` or `<Location>` block.
+ * In '.htaccess', if `AllowOverride Options` is on.
+
+In each place, it may be specified at most once. The default value is 'off'.
+
+=== PassengerResistDeploymentErrors <on|off> ===
+**Available in Phusion Passenger Enterprise since version 3.0.0.**
+
+Enables or disables resistance against deployment errors.
+
+Suppose you've upgraded your application and you've issues a command to restart it (by touching restart.txt), but the application code contains an error that prevents Phusion Passenger from successfully spawning a process (e.g. a syntax error). Phusion Passenger would normally display an error message in response to this.
+
+By enabling deployment error resistance, Phusion Passenger Enterprise would instead do this:
+
+- It passes the request to one of the existing application processes (that belong to the previous version of the application). The visitor will not see a Phusion Passenger process spawning error message.
+- It logs the error to the global web server error log file.
+- It sets an internal flag so that no processes for this application will be spawned (even when the current traffic would normally result in more processes being spawned) and no processes will be idle cleaned. Processes *could* still be shutdown because of other events, e.g. because their <<PassengerMemoryLimit,memory limit>> have been reached.
+
+This way, visitors will suffer minimally from deployment errors. Phusion Passenger will attempt to restart the application again next time restart.txt is touched.
+
+Enabling deployment error resistance only works if <<PassengerRollingRestarts,rolling restart>> is also enabled.
+
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+ * In a `<Directory>` or `<Location>` block.
+ * In '.htaccess', if `AllowOverride Options` is on.
+
+In each place, it may be specified at most once. The default value is 'off'.
+
 === Security options ===
 
 [[PassengerUserSwitching]]
@@ -1137,6 +1203,36 @@ The PassengerMinInstances option may occur in the following places:
 
 In each place, it may be specified at most once. The default value is '1'.
 
+==== PassengerMaxInstances <integer> ====
+**Available in Phusion Passenger Enterprise since version 3.0.0.**
+
+The maximum number of application processes that may simultaneously exist
+for an application. This helps to make sure that a single application
+will not occupy all available slots in the application pool.
+
+This value must be less than <<PassengerMaxPoolSize,PassengerMaxPoolSize>>. A value of 0
+means that there is no limit placed on the number of processes a single application
+may spawn, i.e. only the global limit of <<PassengerMaxPoolSize,PassengerMaxPoolSize>>
+will be enforced.
+
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+
+In each place, it may be specified at most once. The default value is '0'.
+
+.Practical usage example
+[TIP]
+===========================================================================
+Suppose that you're hosting two web applications on your server, a personal
+blog and an e-commerce website. You've set <<PassengerMaxPoolSize,PassengerMaxPoolSize>>
+to 10. The e-commerce website is more important to you. You can then set
+'PassengerMaxInstances' to 3 for your blog, so that it will never spawn more
+than 3 processes, even if it suddenly gets a lot of traffic. Your e-commerce website
+on the other hand will be free to spawn up to 10 processes if it gets a lot of traffic.
+===========================================================================
+
 ==== PassengerMaxInstancesPerApp <integer> ====
 The maximum number of application processes that may simultaneously exist
 for a single application. This helps to make sure that a single application
@@ -1150,6 +1246,40 @@ will be enforced.
 This option may only occur once, in the global server configuration.
 The default value is '0'.
 
+.Practical usage example
+[TIP]
+===========================================================================
+Suppose that you're hosting two blogs (blog A and B) on your server, and that
+you've set <<PassengerMaxPoolSize,PassengerMaxPoolSize>> to 10. Under normal
+circumstances, if blog A suddenly gets a lot of traffic, then A will use all 10
+pool slots. If blog B suddenly gets some traffic, then it will only be able to
+use 1 pool slot (forcefully releasing 1 slot from A) until A's traffic has
+settled down and it has released more pool slots.
+
+If you consider both blogs equally important, then you can set
+'PassengerMaxInstancesPerApp' to 5. This way, both blogs will never use more
+than 5 pool slots.
+===========================================================================
+
+.Relation with PassengerMaxInstances
+[NOTE]
+===========================================================================
+Unlike <<PassengerMaxInstances,PassengerMaxInstances>>, this configuration
+option is global and applies to all applications. 'PassengerMaxInstances' on the
+other hand is per-virtual host.
+
+Suppose that you're hosting two web applications on your server, a personal
+blog and an e-commerce website. You've set <<PassengerMaxPoolSize,PassengerMaxPoolSize>>
+to 10. The e-commerce website is more important to you. You can then set
+'PassengerMaxInstances' to 3 for your blog, so that it will never use more than
+3 pool slots, even if it suddenly gets a lot of traffic. Your e-commerce website
+on the other hand will be free to use up all 10 slots if it gets a lot of traffic.
+
+In summary, 'PassengerMaxInstancesPerApp' divides the pool equally among the
+different web applications, while 'PassengerMaxInstances' allows one to divide
+the pool unequally, according to each web application's relative importance.
+===========================================================================
+
 [[PassengerPoolIdleTime]]
 ==== PassengerPoolIdleTime <integer> ====
 The maximum number of seconds that an application process may be idle. That is,
@@ -1205,6 +1335,114 @@ problem in your application rather than relying on these directives as a
 measure to avoid memory leaks.
 =====================================================
 
+[[PassengerMaxRequestTime]]
+==== PassengerMaxRequestTime <seconds> ====
+**Available in Phusion Passenger Enterprise since version 3.0.0.**
+
+The maximum amount of time, in seconds, that an application process may take
+to process a request. If the request takes longer than this amount of time,
+then the application process will be forcefully shut down, and possibly
+restarted upon the next request. A value of 0 means that there is no time limit.
+
+This option is useful for preventing your application from freezing for an
+indefinite period of time.
+
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+ * In a `<Directory>` or `<Location>` block.
+ * In '.htaccess', if `AllowOverride Limits` is on.
+
+In each place, it may be specified at most once. The default value is '0'.
+
+.Example
+Suppose that most of your requests are known to finish within 2 seconds.
+However, there is one URI, '/expensive_computation', which is known to take up
+to 10 seconds. You can then configure Phusion Passenger as follows:
+
+----------------------------------------------
+<VirtualHost *:80>
+    ServerName www.example.com
+    DocumentRoot /webapps/my_app/public
+    
+    PassengerMaxRequestTime 2
+    <Location /expensive_computation>
+        PassengerMaxRequestTime 10
+    </Location>
+</VirtualHost>
+----------------------------------------------
+
+If a request to '/expensive_computation' takes more than 10 seconds,
+or if a request to any other URI takes more than 2 seconds,
+then the corresponding application process will be forced to shutdown.
+
+[CAUTION]
+=====================================================
+The <<PassengerMaxRequestTime,PassengerMaxRequestTime>> directive should be
+considered as a workaround for misbehaving applications. It is advised that you
+fix the problem in your application rather than relying on these directives as a
+measure to avoid freezing applications.
+=====================================================
+
+[[PassengerMemoryLimit]]
+==== PassengerMemoryLimit <integer> ====
+**Available in Phusion Passenger Enterprise since version 3.0.0.**
+
+The maximum amount of memory that an application process may use, in megabytes.
+Once an application process has surpassed its memory limit, it will process
+all the requests currently present in its queue and then shut down.
+A value of 0 means that there is no maximum: the application's memory usage
+will not be checked.
+
+This option is useful if your application is leaking memory. By shutting
+it down, all of its memory is guaranteed to be freed by the operating system.
+
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+ * In a `<Directory>` or `<Location>` block.
+ * In '.htaccess', if `AllowOverride Limits` is on.
+
+In each place, it may be specified at most once. The default value is '200'.
+
+[NOTE]
+.A word about permissions
+=====================================================
+The <<PassengerMemoryLimit,PassengerMemoryLimit>> directive requires that the
+user that the application is running as (see <<PassengerUserSwitching,PassengerUserSwitching>>)
+to have access to the `/proc` file system, or to be able to inspect its status
+with `ps` (which on Linux and FreeBSD systems basically means the same thing, since `ps`
+reads process information from `/proc`). Therefore, on servers running with
+tight permissions on `/proc`, this directive may not work. If you wish to use
+this directive and your `/proc` permissions are too tight, then please consider
+untightening the permissions.
+=====================================================
+
+[TIP]
+.FreeBSD and `/proc`
+=====================================================
+On many FreeBSD systems, `/proc` is not mounted by default. `/proc` *must* be
+mounted in order for <<PassengerMemoryLimit,PassengerMemoryLimit>> to work.
+
+It is also advised that you mount `/proc` with the `linprocfs` filesystem type
+instead of the regular FreeBSD `proc` filesystem type. The `linprocfs` filesystem
+type allows Phusion Passenger to read memory information from `/proc` directly,
+which is very fast. If you mount `/proc` with a different filesystem type, then
+Phusion Passenger must resort to querying memory information from the `ps` command,
+which is a lot slower.
+=====================================================
+
+[CAUTION]
+=====================================================
+The <<PassengerMaxRequests,PassengerMaxRequests>> and
+<<PassengerMemoryLimit,PassengerMemoryLimit>> directives should be considered
+as workarounds for misbehaving applications. It is advised that you fix the
+problem in your application rather than relying on these directives as a
+measure to avoid memory leaks.
+=====================================================
+
 ==== PassengerStatThrottleRate <integer> ====
 By default, Phusion Passenger performs several filesystem checks (or, in
 programmers jargon, 'stat() calls') each time a request is processed:
@@ -1605,6 +1843,30 @@ error messages should be written to instead.
 
 This option may only occur once, in the global server configuration.
 
+==== PassengerDebugger <on|off> ====
+**Available in Phusion Passenger Enterprise since version 3.0.0.**
+
+Turns support for application debugging on or off. In case of Ruby applications,
+turning this option on will cause them to load the `ruby-debug` gem (when on Ruby 1.8)
+or the `debugger` gem (when on Ruby 1.9). If you're using Bundler, you should add
+this to your Gemfile:
+
+-------------------------------------------
+gem 'ruby-debug', :platforms => :ruby_18
+gem 'debugger', :platforms => :ruby_19
+-------------------------------------------
+
+Once debugging is turned on, you can use the command `passenger-irb --debug <PID>` to attach an rdebug console to the application process with the given PID. Attaching will succeed once the application process executes a `debugger` command.
+
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+ * In a `<Directory>` or `<Location>` block.
+ * In '.htaccess', if `AllowOverride Options` is on.
+
+In each place, it may be specified at most once. The default value is 'off'.
+
 
 === Ruby on Rails-specific options ===
 

data/doc/Users guide Nginx.html

@@ -1989,9 +1989,132 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>smart-lv2</em>.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_important_deployment_options" data-comment-topic="important-deployment-options-av567">5.4. Important deployment options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="PassengerRollingRestarts" data-comment-topic="passenger-rolling-restarts">5.4. passenger_rolling_restarts &lt;on|off&gt;</h3>
+<div class="paragraph"><p><strong>Available in Phusion Passenger Enterprise since version 3.0.0.</strong></p></div>
+<div class="paragraph"><p>Enables or disables support for rolling restarts. Normally when you
+restart an application (by touching restart.txt), Phusion Passenger would
+shut down all application processes and spawn a new one. The spawning
+of a new application process could take a while, and any requests that
+come in during this time will be blocked until this first application
+process has spawned.</p></div>
+<div class="paragraph"><p>But when rolling restarts are enabled, Phusion Passenger Enterprise will:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Spawn a new process in the background.
+</p>
+</li>
+<li>
+<p>
+When it’s done spawning, Phusion Passenger Enterprise will replace one of the old processes with this newly spawned one.
+</p>
+</li>
+<li>
+<p>
+Step 1 and 2 are repeated until all processes have been replaced.
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>This way, visitors will not experience any delays when you are restarting your application. This allows you to, for example, upgrade your application often without degrading user experience.</p></div>
+<div class="paragraph"><p>Rolling restarts have a few caveat however that you should be aware of:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Upgrading an application sometimes involves upgrading the database schema.
+  With rolling restarts, there may be a point in time during which processes
+  belonging to the previous version and processes belonging to the new version
+  both exist at the same time. Any database schema upgrades you perform must
+  therefore be backwards-compatible with the old application version.
+</p>
+</li>
+<li>
+<p>
+Because there’s no telling which process will serve a request, users may
+  not see changes brought about by the new version until all processes have
+  been restarted. It is for this reason that you should not use rolling
+  restarts in development, only in production.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_passenger_resist_deployment_errors_lt_on_off_gt" data-comment-topic="passenger-resist-deployment-errors-on-off--k9yf1">5.5. passenger_resist_deployment_errors &lt;on|off&gt;</h3>
+<div class="paragraph"><p><strong>Available in Phusion Passenger Enterprise since version 3.0.0.</strong></p></div>
+<div class="paragraph"><p>Enables or disables resistance against deployment errors.</p></div>
+<div class="paragraph"><p>Suppose you’ve upgraded your application and you’ve issues a command to restart it (by touching restart.txt), but the application code contains an error that prevents Phusion Passenger from successfully spawning a process (e.g. a syntax error). Phusion Passenger would normally display an error message in response to this.</p></div>
+<div class="paragraph"><p>By enabling deployment error resistance, Phusion Passenger Enterprise would instead do this:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+It passes the request to one of the existing application processes (that belong to the previous version of the application). The visitor will not see a Phusion Passenger process spawning error message.
+</p>
+</li>
+<li>
+<p>
+It logs the error to the global web server error log file.
+</p>
+</li>
+<li>
+<p>
+It sets an internal flag so that no processes for this application will be spawned (even when the current traffic would normally result in more processes being spawned) and no processes will be idle cleaned. Processes <strong>could</strong> still be shutdown because of other events, e.g. because their <a href="#PassengerMemoryLimit">memory limit</a> have been reached.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>This way, visitors will suffer minimally from deployment errors. Phusion Passenger will attempt to restart the application again next time restart.txt is touched.</p></div>
+<div class="paragraph"><p>Enabling deployment error resistance only works if <a href="#PassengerRollingRestarts">rolling restart</a> is also enabled.</p></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_important_deployment_options" data-comment-topic="important-deployment-options-av567">5.6. Important deployment options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_enabled_lt_on_off_gt" data-comment-topic="passenger-enabled-on-off--1rpb2t7">5.4.1. passenger_enabled &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_enabled_lt_on_off_gt" data-comment-topic="passenger-enabled-on-off--1rpb2t7">5.6.1. passenger_enabled &lt;on|off&gt;</h4>
 <div class="paragraph"><p>This option may be specified in the <em>http</em> configuration block, a
 <em>server</em> configuration block, a <em>location</em> configuration block or
 an <em>if</em> configuration scope, to enable or disable Phusion Passenger
@@ -2003,7 +2126,7 @@ and <a href="#deploying_a_rack_app">Deploying a Rack-based Ruby application</a>
 for examples.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerBaseURI" data-comment-topic="passenger-base-uri-uri--1xtuo50">5.4.2. passenger_base_uri &lt;uri&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerBaseURI" data-comment-topic="passenger-base-uri-uri--1xtuo50">5.6.2. passenger_base_uri &lt;uri&gt;</h4>
 <div class="paragraph"><p>Used to specify that the given URI is an distinct application that should
 be served by Phusion Passenger. This option can be used for both Rails and
 Rack applications. See <a href="#deploying_rails_to_sub_uri">Deploying Rails to a sub URI</a>
@@ -2036,9 +2159,9 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_connection_handling_options" data-comment-topic="connection-handling-options-8jgq90">5.5. Connection handling options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_connection_handling_options" data-comment-topic="connection-handling-options-8jgq90">5.7. Connection handling options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerUseGlobalQueue" data-comment-topic="passenger-use-global-queue-on-off--14h9n22">5.5.1. passenger_use_global_queue &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerUseGlobalQueue" data-comment-topic="passenger-use-global-queue-on-off--14h9n22">5.7.1. passenger_use_global_queue &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Turns the use of global queuing on or off.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
 <div class="ulist"><ul>
@@ -2145,7 +2268,7 @@ process that becomes available will take from the queue, and so this
 “queuing-behind-long-running-request” problem will never occur.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_ignore_client_abort_lt_on_off_gt" data-comment-topic="passenger-ignore-client-abort-on-off--19bapt2">5.5.2. passenger_ignore_client_abort &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_ignore_client_abort_lt_on_off_gt" data-comment-topic="passenger-ignore-client-abort">5.7.2. passenger_ignore_client_abort &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Normally, when the HTTP client aborts the connection (e.g. when the user clicked on "Stop"
 in the browser), the connection with the application process will be closed too. If the
 application process continues to send its response, then that will result in EPIPE errors
@@ -2181,7 +2304,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_set_cgi_param_lt_cgi_environment_name_gt_lt_value_gt" data-comment-topic="passenger-set-cgi-param-cgi-environment-name-value--rx9gc0">5.5.3. passenger_set_cgi_param &lt;CGI environment name&gt; &lt;value&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_set_cgi_param_lt_cgi_environment_name_gt_lt_value_gt" data-comment-topic="passenger-set-cgi-param-cgi-environment-name-value--rx9gc0">5.7.3. passenger_set_cgi_param &lt;CGI environment name&gt; &lt;value&gt;</h4>
 <div class="paragraph"><p>Allows one to define additional CGI environment variables to pass to the backend
 application. This is equivalent to ngx_http_fastcgi_module’s <em>fastcgi_param</em>
 directive, and is comparable to ngx_http_proxy_module’s <em>proxy_set_header</em> option.
@@ -2232,7 +2355,7 @@ In an <em>if</em> configuration scope.
 </ul></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_pass_header_lt_header_name_gt" data-comment-topic="passenger-pass-header-header-name--1cg31je">5.5.4. passenger_pass_header &lt;header name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_pass_header_lt_header_name_gt" data-comment-topic="passenger-pass-header-header-name--1cg31je">5.7.4. passenger_pass_header &lt;header name&gt;</h4>
 <div class="paragraph"><p>Some headers generated by backend applications are not forwarded to the HTTP client,
 e.g. <em>X-Accel-Redirect</em> which is directly processed by Nginx and then discarded from
 the final response. This directive allows one to force Nginx to pass those headers
@@ -2270,7 +2393,7 @@ In an <em>if</em> configuration scope.
 </ul></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffer_response_lt_on_off_gt" data-comment-topic="passenger-buffer-response-on-off--1twmh51">5.5.5. passenger_buffer_response &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffer_response_lt_on_off_gt" data-comment-topic="passenger-buffer-response">5.7.5. passenger_buffer_response &lt;on|off&gt;</h4>
 <div class="paragraph"><p>When turned on, application-generated responses are buffered in memory and also on
 disk if the response is larger than a certain threshold. By buffering responses,
 protection is provided against slow HTTP clients that can not read your response
@@ -2343,27 +2466,27 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>on</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffer_size" data-comment-topic="passenger-buffer-size-1jfkq87">5.5.6. passenger_buffer_size</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffer_size" data-comment-topic="passenger-buffer-size-1jfkq87">5.7.6. passenger_buffer_size</h4>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffers" data-comment-topic="passenger-buffers-12q1he5">5.5.7. passenger_buffers</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_buffers" data-comment-topic="passenger-busy-buffers">5.7.7. passenger_buffers</h4>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_busy_buffer_size" data-comment-topic="passenger-busy-buffer-size-1gde265">5.5.8. passenger_busy_buffer_size</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_busy_buffer_size" data-comment-topic="passenger-busy-buffer-size-124sj61">5.7.8. passenger_busy_buffer_size</h4>
 <div class="paragraph"><p>These options have the same effect as proxy_module’s similarly named options.
 They can be used to modify the maximum allowed HTTP header size.</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_security_options" data-comment-topic="security-options-1bv93g4">5.6. Security options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_security_options" data-comment-topic="security-options-1bv93g4">5.8. Security options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerUserSwitching" data-comment-topic="passenger-user-switching-on-off--1p37u3l">5.6.1. passenger_user_switching &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerUserSwitching" data-comment-topic="passenger-user-switching-on-off--1p37u3l">5.8.1. passenger_user_switching &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Whether to enable <a href="#user_switching">user switching support</a>.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.
 The default value is <em>on</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_user_lt_username_gt" data-comment-topic="passenger-user-username--b06ur7">5.6.2. passenger_user &lt;username&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_user_lt_username_gt" data-comment-topic="passenger-user-username--b06ur7">5.8.2. passenger_user &lt;username&gt;</h4>
 <div class="paragraph"><p>If <a href="#user_switching">user switching support</a> is enabled, then Phusion Passenger will
 by default run the web application as the owner of the file <em>config/environment.rb</em>
 (for Rails apps) or <em>config.ru</em> (for Rack apps). This option allows you to override
@@ -2395,7 +2518,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_user_lt_group_name_gt" data-comment-topic="passenger-user-group-name--1fco4j7">5.6.3. passenger_user &lt;group name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_group_lt_group_name_gt" data-comment-topic="passenger-user-group-name--1fco4j7">5.8.3. passenger_group &lt;group name&gt;</h4>
 <div class="paragraph"><p>If <a href="#user_switching">user switching support</a> is enabled, then Phusion Passenger will
 by default run the web application as the primary group of the owner of the file
 <em>config/environment.rb</em> (for Rails apps) or <em>config.ru</em> (for Rack apps). This option
@@ -2429,7 +2552,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerDefaultUser" data-comment-topic="passenger-default-user-username--1h6cdmf">5.6.4. passenger_default_user &lt;username&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerDefaultUser" data-comment-topic="passenger-default-user-username--1h6cdmf">5.8.4. passenger_default_user &lt;username&gt;</h4>
 <div class="paragraph"><p>Phusion Passenger enables <a href="#user_switching">user switching support</a> by default.
 This configuration option allows one to specify the user that applications must
 run as, if user switching fails or is disabled.</p></div>
@@ -2437,7 +2560,7 @@ run as, if user switching fails or is disabled.</p></div>
 The default value is <em>nobody</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerDefaultGroup" data-comment-topic="passenger-default-group-group-name--1qxn2qa">5.6.5. Passenger_default_group &lt;group name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerDefaultGroup" data-comment-topic="passenger-default-group-group-name--1qxn2qa">5.8.5. Passenger_default_group &lt;group name&gt;</h4>
 <div class="paragraph"><p>Phusion Passenger enables <a href="#user_switching">user switching support</a> by default.
 This configuration option allows one to specify the group that applications must
 run as, if user switching fails or is disabled.</p></div>
@@ -2446,7 +2569,7 @@ The default value is the primary group of the user specifified by
 <a href="#PassengerDefaultUser">passenger_default_user</a>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_friendly_error_pages_lt_on_off_gt" data-comment-topic="passenger-friendly-error-pages-on-off--27mews">5.6.6. passenger_friendly_error_pages &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_friendly_error_pages_lt_on_off_gt" data-comment-topic="passenger-friendly-error-pages-on-off--1ti1a0e">5.8.6. passenger_friendly_error_pages &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Phusion Passenger can display friendly error pages whenever an application fails
 to start. This friendly error page presents the startup error message, some
 suggestions for solving the problem, and a backtrace. This feature is very useful
@@ -2481,9 +2604,9 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_resource_control_and_optimization_options" data-comment-topic="resource-control-and-optimization-options-xd7evs">5.7. Resource control and optimization options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_resource_control_and_optimization_options" data-comment-topic="resource-control-and-optimization-options-xd7evs">5.9. Resource control and optimization options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMaxPoolSize" data-comment-topic="passenger-max-pool-size-integer--3jzefs">5.7.1. passenger_max_pool_size &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMaxPoolSize" data-comment-topic="passenger-max-pool-size-integer--3jzefs">5.9.1. passenger_max_pool_size &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of <a href="#application_process">application processes</a> that may
 simultanously exist. A larger number results in higher memory usage,
 but improved ability to handle concurrent HTTP clients.</p></div>
@@ -2510,7 +2633,7 @@ by about 33%, and it’s not hard to install.</td>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMinInstances" data-comment-topic="passenger-min-instances-integer--uclykt">5.7.2. passenger_min_instances &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMinInstances" data-comment-topic="passenger-min-instances-integer--uclykt">5.9.2. passenger_min_instances &lt;integer&gt;</h4>
 <div class="paragraph"><p>This specifies the minimum number of application processes that should exist for a
 given application. You should set this option to a
 non-zero value if you want to avoid potentially long startup times after a website
@@ -2585,7 +2708,58 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>1</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_max_instances_per_app_lt_integer_gt" data-comment-topic="passenger-max-instances-per-app-integer--1p7q3cf">5.7.3. passenger_max_instances_per_app &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_max_instances_lt_integer_gt" data-comment-topic="passenger-max-instances">5.9.3. passenger_max_instances &lt;integer&gt;</h4>
+<div class="paragraph"><p><strong>Available in Phusion Passenger Enterprise since version 3.0.0.</strong></p></div>
+<div class="paragraph"><p>The maximum number of application processes that may simultaneously exist
+for an application. This helps to make sure that a single application
+will not occupy all available slots in the application pool.</p></div>
+<div class="paragraph"><p>This value must be less than <a href="#PassengerMaxPoolSize">passenger_max_pool_size</a>. A value of 0
+means that there is no limit placed on the number of processes a single application
+may spawn, i.e. only the global limit of <a href="#PassengerMaxPoolSize">passenger_max_pool_size</a>
+will be enforced.</p></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>0</em>.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/tip.png" alt="Tip">
+</td>
+<td class="content">
+<div class="title">Practical usage example</div>
+<div class="paragraph"><p>Suppose that you’re hosting two web applications on your server, a personal
+blog and an e-commerce website. You’ve set <a href="#PassengerMaxPoolSize">passenger_max_pool_size</a>
+to 10. The e-commerce website is more important to you. You can then set
+<em>passenger_max_instances</em> to 3 for your blog, so that it will never spawn more
+than 3 processes, even if it suddenly gets a lot of traffic. Your e-commerce website
+on the other hand will be free to spawn up to 10 processes if it gets a lot of traffic.</p></div>
+</td>
+</tr></table>
+</div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_max_instances_per_app_lt_integer_gt" data-comment-topic="passenger-max-instances-per-app-integer--1xhbbne">5.9.4. passenger_max_instances_per_app &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of application processes that may simultaneously exist
 for a single application. This helps to make sure that a single application
 will not occupy all available slots in the application pool.</p></div>
@@ -2597,7 +2771,7 @@ will be enforced.</p></div>
 The default value is <em>0</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerPoolIdleTime" data-comment-topic="passenger-pool-idle-time-integer--xcw65o">5.7.4. passenger_pool_idle_time &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerPoolIdleTime" data-comment-topic="passenger-pool-idle-time-integer--xcw65o">5.9.5. passenger_pool_idle_time &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of seconds that an application process may be idle. That is,
 if an application process hasn’t received any traffic after the given number of
 seconds, then it will be shutdown in order to conserve memory.</p></div>
@@ -2619,7 +2793,7 @@ applications, each which must be available at all times.</p></div>
 The default value is <em>300</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMaxRequests" data-comment-topic="passenger-max-requests-integer--sgzint">5.7.5. passenger_max_requests &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMaxRequests" data-comment-topic="passenger-max-requests">5.9.6. passenger_max_requests &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of requests an application process will process. After
 serving that many requests, the application process will be shut down and
 Phusion Passenger will restart it. A value of 0 means that there is no maximum:
@@ -2667,7 +2841,163 @@ measure to avoid memory leaks.</p></div>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerPreStart" data-comment-topic="passenger-pre-start-url--qeevln">5.7.6. passenger_pre_start &lt;url&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMaxRequestTime" data-comment-topic="passenger-max-request-time-seconds--1qod9kg">5.9.7. passenger_max_request_time &lt;seconds&gt;</h4>
+<div class="paragraph"><p><strong>Available in Phusion Passenger Enterprise since version 3.0.0.</strong></p></div>
+<div class="paragraph"><p>The maximum amount of time, in seconds, that an application process may take
+to process a request. If the request takes longer than this amount of time,
+then the application process will be forcefully shut down, and possibly
+restarted upon the next request. A value of 0 means that there is no time limit.</p></div>
+<div class="paragraph"><p>This option is useful for preventing your application from freezing for an
+indefinite period of time.</p></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>0</em>.</p></div>
+<div class="paragraph">
+<div class="title">Example</div>
+<p>Suppose that most of your requests are known to finish within 2 seconds.
+However, there is one URI, <em>/expensive_computation</em>, which is known to take up
+to 10 seconds. You can then configure Phusion Passenger as follows:</p>
+</div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>server {
+    listen 80;
+    server_name www.example.com;
+    root /webapps/my_app/public;
+    passenger_enabled on;
+    passenger_max_request_time 2;
+    location /expensive_compuation {
+        passenger_enabled on;
+        passenger_max_request_time 10;
+    }
+}</pre>
+</div>
+</div>
+<div class="paragraph"><p>If a request to <em>/expensive_computation</em> takes more than 10 seconds,
+or if a request to any other URI takes more than 2 seconds,
+then the corresponding application process will be forced to shutdown.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/caution.png" alt="Caution">
+</td>
+<td class="content">
+<div class="paragraph"><p>The <a href="#PassengerMaxRequestTime">passenger_max_request_time</a> directive should be
+considered as a workaround for misbehaving applications. It is advised that you
+fix the problem in your application rather than relying on these directives as a
+measure to avoid freezing applications.</p></div>
+</td>
+</tr></table>
+</div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerMemoryLimit" data-comment-topic="passenger-memory-limit-integer--1ry7dwx">5.9.8. passenger_memory_limit &lt;integer&gt;</h4>
+<div class="paragraph"><p>The maximum amount of memory that an application process may use, in megabytes.
+Once an application process has surpassed its memory limit, it will process
+all the requests currently present in its queue and then shut down.
+A value of 0 means that there is no maximum: the application’s memory usage
+will not be checked.</p></div>
+<div class="paragraph"><p>This option is useful if your application is leaking memory. By shutting
+it down, all of its memory is guaranteed to be freed by the operating system.</p></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>200</em>.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">
+<div class="title">A word about permissions</div>
+<div class="paragraph"><p>The <a href="#PassengerMemoryLimit">passenger_memory_limit</a> directive requires that the
+user that the application is running as (see <a href="#PassengerUserSwitching">passenger_user_switching</a>)
+to have access to the <span class="monospaced">/proc</span> file system, or to be able to inspect its status
+with <span class="monospaced">ps</span> (which on Linux and FreeBSD systems basically means the same thing, since <span class="monospaced">ps</span>
+reads process information from <span class="monospaced">/proc</span>). Therefore, on servers running with
+tight permissions on <span class="monospaced">/proc</span>, this directive may not work. If you wish to use
+this directive and your <span class="monospaced">/proc</span> permissions are too tight, then please consider
+untightening the permissions.</p></div>
+</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/tip.png" alt="Tip">
+</td>
+<td class="content">
+<div class="title">FreeBSD and <span class="monospaced">/proc</span>
+</div>
+<div class="paragraph"><p>On many FreeBSD systems, <span class="monospaced">/proc</span> is not mounted by default. <span class="monospaced">/proc</span> <strong>must</strong> be
+mounted in order for <a href="#PassengerMemoryLimit">passenger_memory_limit</a> to work.</p></div>
+<div class="paragraph"><p>It is also advised that you mount <span class="monospaced">/proc</span> with the <span class="monospaced">linprocfs</span> filesystem type
+instead of the regular FreeBSD <span class="monospaced">proc</span> filesystem type. The <span class="monospaced">linprocfs</span> filesystem
+type allows Phusion Passenger to read memory information from <span class="monospaced">/proc</span> directly,
+which is very fast. If you mount <span class="monospaced">/proc</span> with a different filesystem type, then
+Phusion Passenger must resort to querying memory information from the <span class="monospaced">ps</span> command,
+which is a lot slower.</p></div>
+</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/caution.png" alt="Caution">
+</td>
+<td class="content">
+<div class="paragraph"><p>The <a href="#PassengerMaxRequests">passenger_max_requests</a> and
+<a href="#PassengerMemoryLimit">passenger_memory_limit</a> directives should be considered
+as workarounds for misbehaving applications. It is advised that you fix the
+problem in your application rather than relying on these directives as a
+measure to avoid memory leaks.</p></div>
+</td>
+</tr></table>
+</div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="PassengerPreStart" data-comment-topic="passenger-pre-start-url--1f2phk7">5.9.9. passenger_pre_start &lt;url&gt;</h4>
 <div class="paragraph"><p>By default, Phusion Passenger does not start any application processes until said
 web application is first accessed. The result is that the first visitor of said
 web application might experience a small delay as Phusion Passenger is starting
@@ -2882,9 +3212,9 @@ the request ending up at a different web server in the cluster.</p></div>
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_logging_and_debugging_options" data-comment-topic="logging-and-debugging-options-14e91ni">5.8. Logging and debugging options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_logging_and_debugging_options" data-comment-topic="logging-and-debugging-options-14e91ni">5.10. Logging and debugging options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_log_level_lt_integer_gt" data-comment-topic="passenger-log-level-integer--17snhon">5.8.1. passenger_log_level &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_log_level_lt_integer_gt" data-comment-topic="passenger-log-level-integer--17snhon">5.10.1. passenger_log_level &lt;integer&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify how much information Phusion Passenger should
 write to the Nginx error log file. A higher log level value means that more
 information will be logged.</p></div>
@@ -2917,17 +3247,56 @@ information will be logged.</p></div>
 The default is <em>0</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_debug_log_file_lt_filename_gt" data-comment-topic="passenger-debug-log-file-filename--21ubaj">5.8.2. passenger_debug_log_file &lt;filename&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_debug_log_file_lt_filename_gt" data-comment-topic="passenger-debug-log-file-filename--21ubaj">5.10.2. passenger_debug_log_file &lt;filename&gt;</h4>
 <div class="paragraph"><p>By default Phusion Passenger debugging and error messages are written to the global
 web server error log. This option allows one to specify the file that debugging and
 error messages should be written to instead.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.</p></div>
 </div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_passenger_debugger_lt_on_off_gt" data-comment-topic="passenger-debugger-on-off--1wkuq85">5.10.3. passenger_debugger &lt;on|off&gt;</h4>
+<div class="paragraph"><p><strong>Available in Phusion Passenger Enterprise since version 3.0.0.</strong></p></div>
+<div class="paragraph"><p>Turns support for application debugging on or off. In case of Ruby applications,
+turning this option on will cause them to load the <span class="monospaced">ruby-debug</span> gem (when on Ruby 1.8)
+or the <span class="monospaced">debugger</span> gem (when on Ruby 1.9). If you’re using Bundler, you should add
+this to your Gemfile:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>gem 'ruby-debug', :platforms =&gt; :ruby_18
+gem 'debugger', :platforms =&gt; :ruby_19</pre>
+</div>
+</div>
+<div class="paragraph"><p>Once debugging is turned on, you can use the command <span class="monospaced">passenger-irb --debug &lt;PID&gt;</span> to attach an rdebug console to the application process with the given PID. Attaching will succeed once the application process executes a <span class="monospaced">debugger</span> command.</p></div>
+<div class="paragraph"><p>This option may occur in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the <em>http</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>server</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <em>location</em> configuration block.
+</p>
+</li>
+<li>
+<p>
+In an <em>if</em> configuration scope.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
+</div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_ruby_on_rails_specific_options" data-comment-topic="ruby-on-rails-specific-options-12vfokt">5.9. Ruby on Rails-specific options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_ruby_on_rails_specific_options" data-comment-topic="ruby-on-rails-specific-options-12vfokt">5.11. Ruby on Rails-specific options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="RailsEnv" data-comment-topic="rails-env-string--jlh7v9">5.9.1. rails_env &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="RailsEnv" data-comment-topic="rails-env-string--jlh7v9">5.11.1. rails_env &lt;string&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify the default <span class="monospaced">RAILS_ENV</span> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
 <div class="ulist"><ul>
@@ -2955,7 +3324,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>production</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_rails_framework_spawner_idle_time_lt_integer_gt" data-comment-topic="rails-framework-spawner-idle-time-integer--q5ljd5">5.9.2. rails_framework_spawner_idle_time &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_rails_framework_spawner_idle_time_lt_integer_gt" data-comment-topic="rails-framework-spawner-idle-time-integer--q5ljd5">5.11.2. rails_framework_spawner_idle_time &lt;integer&gt;</h4>
 <div class="paragraph"><p>The FrameworkSpawner server (explained in <a href="#spawning_methods_explained">Spawning methods explained</a>) has an idle timeout, just like the backend processes spawned by
 Phusion Passenger do. That is, it will automatically shutdown if it hasn’t done
 anything for a given period.</p></div>
@@ -2994,7 +3363,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>1800</em> (30 minutes).</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_rails_app_spawner_idle_time_lt_integer_gt" data-comment-topic="rails-app-spawner-idle-time-integer--1xjqe4b">5.9.3. rails_app_spawner_idle_time &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_rails_app_spawner_idle_time_lt_integer_gt" data-comment-topic="rails-app-spawner-idle-time-integer--1xjqe4b">5.11.3. rails_app_spawner_idle_time &lt;integer&gt;</h4>
 <div class="paragraph"><p>The ApplicationSpawner server (explained in <a href="#spawning_methods_explained">Spawning methods explained</a>) has an idle timeout, just like the backend processes spawned by
 Phusion Passenger do. That is, it will automatically shutdown if it hasn’t done
 anything for a given period.</p></div>
@@ -3034,9 +3403,9 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_rack_specific_options" data-comment-topic="rack-specific-options-13yvdxs">5.10. Rack-specific options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_rack_specific_options" data-comment-topic="rack-specific-options-13yvdxs">5.12. Rack-specific options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="RackEnv" data-comment-topic="rack-env-string--tqmrt0">5.10.1. rack_env &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="RackEnv" data-comment-topic="rack-env-string--tqmrt0">5.12.1. rack_env &lt;string&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify the default <span class="monospaced">RACK_ENV</span> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
 <div class="ulist"><ul>
@@ -3065,11 +3434,11 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_deprecated_options" data-comment-topic="deprecated-options-1dtzo0g">5.11. Deprecated options</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_deprecated_options" data-comment-topic="deprecated-options-1dtzo0g">5.13. Deprecated options</h3>
 <div class="paragraph"><p>The following options have been deprecated, but are still supported for backwards
 compatibility reasons.</p></div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_rails_spawn_method" data-comment-topic="rails-spawn-method-17vdnpt">5.11.1. rails_spawn_method</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h4 id="_rails_spawn_method" data-comment-topic="rails-spawn-method-17vdnpt">5.13.1. rails_spawn_method</h4>
 <div class="paragraph"><p>Deprecated in favor of <a href="#PassengerSpawnMethod">passenger_spawn_method</a>.</p></div>
 </div>
 </div>
@@ -3353,6 +3722,11 @@ through the <em>X-Passenger-Connect-Password</em> HTTP header, like this:</p></d
 </div>
 </div>
 </div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><h3 id="_attaching_an_irb_console_to_an_application_process" data-comment-topic="attaching-an-irb-console-to-an-application-process-d36enw">6.5. Attaching an IRB console to an application process</h3>
+<div class="paragraph"><p><strong>Available in Phusion Passenger Enterprise since version 3.0.0.</strong></p></div>
+<div class="paragraph"><p>You can attach an IRB console to any application process and inspect its state by executing arbitrary Ruby code. Do this by invoking <span class="monospaced">passenger-irb &lt;PID&gt;</span> where <em>&lt;PID&gt;</em> is the PID of the application process you wish to inspect. Note that the IRB console is currently only available for Ruby apps, not for apps in any other languages.</p></div>
+</div>
 </div>
 </div>
 <div class="sect1">
@@ -4099,7 +4473,7 @@ has no effect.</p></div>
 <div id="footnotes"><hr></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2012-07-21 20:27:37 CEST
+Last updated 2012-08-01 13:31:01 CEST
 </div>
 </div>
 <script>/*! jQuery v1.7.1 jquery.com | jquery.org/license */