[ https://issues.jboss.org/browse/JBIDE-14342?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-14342 at 4/30/13 5:09 PM: ------------------------------------------------------------------- Reopening since it turned out that the issue is not in the OpenShift broker (https://bugzilla.redhat.com/show_bug.cgi?id=958113 is not a bug, I closed it) but in JBoss Tools: The cause for this issue is in the CreateApplicationJob which is responsible for creating all applications on OpenShift from JBoss Tooks. The job timeouts in many cases (apparently the timing in OpenShift further degrade) and it then tries to refresh and retries if the app isn't listed yet: {code:title=CreateApplicationJob} @Override protected IStatus doRun(IProgressMonitor monitor) { try { try { this.application = domain.createApplication(name, cartridge, scale, gear); } catch (OpenShiftTimeoutException e) { this.application = refreshAndCreateApplication(monitor); } private IApplication refreshAndCreateApplication(IProgressMonitor monitor) throws OpenShiftException { if (monitor.isCanceled()) { return null; } IApplication application = null; do { try { domain.refresh(); application = domain.getApplicationByName(name); if (application == null) { // app is not created yet, try again application = domain.createApplication(name, cartridge, scale, gear); } } catch (OpenShiftTimeoutException ex) { // ignore } } while (application == null && openKeepTryingDialog() && !monitor.isCanceled()); return application; } {code} When timeouting and refreshing it'll get the application that was created but loose the creation log since the log is only reported for the initial request (not for the refresh). The only solution I currently see is to increase the timeouts. was (Author: adietish): reopening since it turned out that the issue is not in the OpenShift broker (https://bugzilla.redhat.com/show_bug.cgi?id=958113 is not a bug, I closed it) but in JBoss Tools: The cause for this issue is in the CreateApplicationJob which is responsible for creating all applications on OpenShift from JBoss Tooks. The job timeouts in many cases (apparently the timing in OpenShift further degrade) and it then tries to refresh and retries if the app isn't listed yet: {code:title=CreateApplicationJob} @Override protected IStatus doRun(IProgressMonitor monitor) { try { try { this.application = domain.createApplication(name, cartridge, scale, gear); } catch (OpenShiftTimeoutException e) { this.application = refreshAndCreateApplication(monitor); } private IApplication refreshAndCreateApplication(IProgressMonitor monitor) throws OpenShiftException { if (monitor.isCanceled()) { return null; } IApplication application = null; do { try { domain.refresh(); application = domain.getApplicationByName(name); if (application == null) { // app is not created yet, try again application = domain.createApplication(name, cartridge, scale, gear); } } catch (OpenShiftTimeoutException ex) { // ignore } } while (application == null && openKeepTryingDialog() && !monitor.isCanceled()); return application; } {code} -- 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