Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1113349
Description of problem:
Idle timeouts can be distracting. Thus, uf a user enters a very large number in the config settings for idle_timeout, there is no bounds testing and the UI crashes.

Version-Release number of selected component (if applicable):

Satellite-6.0.3-RHEL-6-20140625.0

How reproducible:

Steps to Reproduce:
1. In config settings, change the idle_timeout value to something large like "9999999"
2. Begin navigating elsewhere in UI.
3. View results

Actual results:
We're sorry, but something went wrong.

We've been notified about this issue and we'll take a look at it shortly.

In production.log

ArgumentError (year too big to marshal: 192146 UTC):
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in `block (3 levels) in start_threads'

Expected results:
Sane bounds testing of this field (and all others!).

Additional info: