[ https://issues.jboss.org/browse/JBIDE-16100?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16100: ------------------------------------------ [~mmurray] the N&N I just checked is wrong. I wrote {quote} To allow you to adjust timeouts when talking to your OpenShift server we now offer you a preferences page. {quote} and max corrected it to the current text: {quote} There is now a preference available to set the timeout used when waiting for OpenShift requests to complete. The default is 240 seconds (4 minutes). You can try raise this value if you are getting time out errors when using OpenShift. {quote} As stated in JBIDE-15880 there are 4 different timeouts that may apply: {quote} 1) operation specific timeout (used in JBT only when creating applications so far) 2) openshift-java-client specific system property 3) jdk-wide HttpUrlConnection timeout 4) safe default of 2 Minutes {quote} The initial value (when user did not set anything) is 0 for the *openshift-java-client specific system property (2)*. Since there's no *jdk-wide HttpUrlConnection timeout (3)* by default, the *safe default of 2 Minutes* would apply. There are thus 2 issues here: 1) The screenshot suggests that we have a default of 240 seconds (4 MInutes) which is wrong. We default to 0 2) There's nothing that tells the user that the safe default of 2 Minutes is applied. I suggest that we change the text in the preferences page and maybe update the N&N to reflect this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira