[jbosstools-issues] [JBoss JIRA] (JBIDE-15054) embed cartridges: cannot embed rockmongo + mongo + phpmyadmin + mysql at the same time

Fri Jun 28 11:05:21 EDT 2013

    [ https://issues.jboss.org/browse/JBIDE-15054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786238#comment-12786238 ] 

Andre Dietisheim edited comment on JBIDE-15054 at 6/28/13 11:04 AM:
--------------------------------------------------------------------

Unfortunately it turns out that WizardUtils is applying a default timeout of 2 mins if you dont give it a timeout, something I didnt spot so far (thought it was implemented not to timeout in that case).
So I'm reverting this patch and increase the timeout to very high values and file an issue for 4.2.x to remove the guards for these jobs, provide some wizardUtils that wont cancel the job if a given timeout is exceeded: JBIDE-15058.

      was (Author: adietish):
    Unfortunately it turns out that WizardUtils is applying a default timeout of 2 mins if you dont give it a timeout, something I didnt spot so far (thought it was implemented not to timeout in that case).
So I'm reverting this patch and increase the timeout to very high values and file an issue for 4.2.x to remove the guards for these jobs, provide some wizardUtils that wont cancel the job if a given timeout is exceeded.

> embed cartridges: cannot embed rockmongo + mongo + phpmyadmin + mysql at the same time
> --------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15054
>                 URL: https://issues.jboss.org/browse/JBIDE-15054
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.1.0.CR1
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>             Fix For: 4.1.0.CR1, 4.2.0.Alpha1
>
>         Attachments: embed-mongo-mysql-myadmin-rockmongo.png
>
>

--
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