Document additional session store options (TORQUE-1013)
Restart services after a zero-downtime deployment of the services runtime (TORQUE-819)
Document zero-downtime deployments (TORQUE-819)
Somehow tabs made their way into some of the source files - convert to spaces
Increase max .receive time on jobs_timeout_spec to account for full GCs during integs
Close AR connections when finished with work in non-web threads (TORQUE-929)
Clear all AR connections when tearing down runtimes (TORQUE-1061)
Update remote VisualVM docs to work with latest TorqueBox (TORQUE-1039)
Add basic Rails4 integration test (TORQUE-1115)
Try to be a bit more robust at handling JMX errors when restarting runtimes during integs
More upping of receive timeouts for integs
Log runtime destroying as well as creation
Wrap the runtime restart scanner in a try/catch block (TORQUE-819)

This is just to ensure the scanner doesn't die if an error happens
during a scan.
Fix some runtime memory leaks exposed by the zero-downtime deployments (TORQUE-819)

Once zero-downtime deployments added restarting of services, it
exposed a couple of places where we could hold onto Ruby objects from
previous service runtimes.

This also fixing a potential leak in the SharedPool restart
implementation that could result from restarting the pool multiple
times before the runtime from the first restart gets retired.
Remove another potential runtime memory leak from zero-downtime implementation (TORQUE-819)
Give integs a bit more heap because DRb leaks threads like a sieve
Get yardocs working again after yard starting picking up JRuby's bugger Ripper implementation
Clean up the Ruby API docs by marking lots of things as private
Fix Rails4 integs under JRuby's Ruby 2.0 mode
Only run 'torquebox rails' against Rails4 in integs for 1.9 mode or higher (TORQUE-1115)