client timeouts when talking to OpenShift are unfortunaltey still a topic and cause errors (
JBIDE-15835, JBIDE-15831) when OpenShift is installed on systems with poor performance. We should thus provide a client-lib specific default timeout that a user may override by setting it in the system properties.
The timeout-setting order would thus then be:
1) specific operation timeout (ex. JBT is currently using a specific creation timeout)
2) client-lib default timeout (which may be set by a system property)
3) HttpUrlConnection default timeout (jdk timeout: -Dsun.net.client.defaultConnectTimeout=600000)