10:35 a.m.
Xavier Coulon created JBIDE-11361:
-------------------------------------
Summary: Increase OpenShift wizards timeouts
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:39 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-11361:
------------------------------------------
OpenShift slowed down quite a bit since the end of last year. Where 10 seconds timeout was
sufficient needs now up to 2 minutes and more to get executed. We already have timeouts
but they're currently obviously too short since it happens quite a lot that users face
the message in wizard that we timeouted while waiting for the application to become
ready. The user then has to cancel the wizard and check if the application was created. If
it was, he is still not completely stuck, he can import the existing application and clone
it to his local workspace. But it's still desireable to wait for some more time and
increase the chances that he's not thrown out of the normal workflow because of a
timeout.
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-11361:
-------------------------------------
Description: OpenShift takes a lot more time to create applications lately. Where 10
seconds where enough initially, 2 minutes and more are needed since the end of last year.
For the user this is kinda annoying: when he's creating a new app in the wizard, he
gets the message that we timeouted while waiting for the new application to become ready.
He then has to close the wizard, check if the application was created (in the console or
in an import wizard). He'll then be able to import the existing application and get
the git repo cloned to his local workspace. We can improve this considerably by increasing
the timeout to 2 or even 3 minutes. The user would then eventually have to wait for much
more time but he'll be able to follow the normal workflow in many more cases.
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-11361:
-------------------------------------
One of the end-user workaround to a timeout is to:
1) Cancel the wizard and go about your business
2) Check the openshift.com express console a few minutes later
3) When they see their app provisioned, click on its URL to double check the default app
is loading correctly
4) Restart the OpenShift Application Wizard
5) Select Existing Application (created during the first phase)
6) Select Existing Project
Another solution for step 2 above is to use the OpenShift Express Console inside of
JBDS/Tools to "monitor" the application and see when its default pages have been
provisioned.
Does that sound about right?
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-11361:
------------------------------------------
In the cases I explored the project was not created yet, since the wizard timeouted in a
prior step, when waiting for the application to become ready. That would alter the above
steps in the sense that you'd have to create a new project (as opposed to choose an
existing one).
Alternatively you could also choose the import appilcation wizard which will have the
selected application preselected (which is the same as chosing the existing app
manually).
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-11361 at 3/21/12 6:37 AM:
-------------------------------------------------------------------
In the cases I explored the project was not created yet, since the wizard timeouted in a
prior step, when waiting for the application to become ready. That would alter the above
steps in the sense that you'd have to create a new project (as opposed to choose an
existing one). Even though this works well in most cases, I'm not completely aware how
reliable this approach is. We try to access a specific healt-check url when waiting for
the application to become ready. I was told that this special url was the only one that
would report that all components (the jboss conainter, the git repo etc.) are configured
properly.
Alternatively you could also choose the import appilcation wizard which will have the
selected application preselected (which is the same as chosing the existing app
manually).
was (Author: adietish):
In the cases I explored the project was not created yet, since the wizard timeouted in
a prior step, when waiting for the application to become ready. That would alter the above
steps in the sense that you'd have to create a new project (as opposed to choose an
existing one).
Alternatively you could also choose the import appilcation wizard which will have the
selected application preselected (which is the same as chosing the existing app
manually).
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Xavier Coulon commented on JBIDE-11361:
---------------------------------------
Maybe we should ask that the list of applications we retrieve from the REST API contain an
extra 'status' per application, with values such as 'CREATED' vs
'CREATING' ? This would avoid the need to check health for each and every
user's application, and then let us decide which actions the user can perform (eg:
import only if the application is CREATED)
WDYT ?
/Xavier
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:49 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-11361:
------------------------------------------
that would clearly be the ideal solution, no doubt. But the current RESTy service does not
offer that. Even worse the healt-check url is only available at creation time. You'd
not have it available if you look at applications you created in prior sessions.
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Xavier Coulon commented on JBIDE-11361:
---------------------------------------
Which is why the new REST endpoint could provide us with an URL per application to check
its availability, and/or return the application state when querying for applications.
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:53 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Xavier Coulon updated JBIDE-11361:
----------------------------------
Attachment: JBIDE-11361.patch
Increasing timeout for application availability to 180s and using Future to let the
java-client run in a separate thread and correcly support job cancellation. In case on
cancellation, an error dialog is show to the user, indicating that he cancelled the job.
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:06 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11361:
----------------------------------------
Assignee: Xavier Coulon (was: Max Rydahl Andersen)
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:06 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11361:
---------------------------------------------
patch "looks" ok but could you please do one without reformatting ?
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:02 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Xavier Coulon updated JBIDE-11361:
----------------------------------
Attachment: JBIDE-11361b.patch
Same patch, but removed all unnecessary formatting for better readability ;-)
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch, JBIDE-11361b.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11361:
----------------------------------------
Assignee: Xavier Coulon (was: Max Rydahl Andersen)
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch, JBIDE-11361b.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11361:
---------------------------------------------
looks good - executorservice needs to be shutdown though to avoid thread leak.
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch, JBIDE-11361b.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:02 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Xavier Coulon updated JBIDE-11361:
----------------------------------
Attachment: JBIDE-11361c.patch
New patch that shuts down the Executor pool in a 'finally' block.
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch, JBIDE-11361b.patch, JBIDE-11361c.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11361:
---------------------------------------------
doh - forgot to assign this back.
fix looks good, closes the service now and monitor delegate in there to control progress
bar. yay.
apply.
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch, JBIDE-11361b.patch, JBIDE-11361c.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11361:
----------------------------------------
Assignee: Xavier Coulon (was: Max Rydahl Andersen)
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch, JBIDE-11361b.patch, JBIDE-11361c.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:33 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Xavier Coulon resolved JBIDE-11361.
-----------------------------------
Resolution: Done
Patch applied on trunk and branch
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch, JBIDE-11361b.patch, JBIDE-11361c.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:41 a.m.
[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Stefan Bunciak closed JBIDE-11361.
----------------------------------
Application created, imported, reached in timeout. Verified on JBoss Tools 3.3.0.Beta2
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL: https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Attachments: JBIDE-11361.patch, JBIDE-11361b.patch, JBIDE-11361c.patch
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5124
days inactive
5131
days old
jbosstools-issues@lists.jboss.org
19 comments
5 participants
participants (5)
-
Andre Dietisheim (JIRA) -
Burr Sutter (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Stefan Bunciak (JIRA)
-
Xavier Coulon (JIRA)