reduced timeouts as a results of impact of waiting for CG during service outage on 2/6
request backup appears to have caused tomcat memory usage to spike, triggering high CPU due to GC,
and finally failure to respond at all

If we fail to log new registrations, customers just get free registrations which is better than an outage.
If we timout other requests, users may see an error in account management UI, which isn't actually
worse than waiting a very long time for that UI to render
Merge pull request #2 from RusticiSoftware/bsc_timeout

reduced timeouts as a results of impact of waiting for CG during service...