-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
None
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)
- blocks
-
JBIDE-15905 allow users to set openshift-java-client specific timeout in JBoss Tools via Eclipse Preferences
- Closed
-
JBIDE-16046 CLONE - allow users to set openshift-java-client specific timeout in JBoss Tools via Eclipse Preferences
- Closed
-
JBIDE-15831 Server side errors while creating most of the scalable app. on Openshift Enterprise
- Closed
-
JBIDE-15835 Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
- Closed
-
JBIDE-16047 CLONE - Timeout when add/remove postgresql cartridge to application (Openshift Enterprise)
- Closed
- relates to
-
JBIDE-16100 OpenShift time out preference should show default 240 seconds and not 0
- Closed