[jbosstools-issues] [JBoss JIRA] (JBIDE-14895) Deployed module stays in [Stopped, Synchronized] state after being deployed

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-14895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-14895.
---------------------------------

    Resolution: Done


Fixed in cr1.

Details:  The job in charge of updating the status now has a loop in it to wait for all modules to complete. After a set timeout duration, the job will of course give up and set the module to stopped. IT's still possible that for large modules with a long deployment time will be marked as 'stopped' for this process, and I expect future jiras to open because of this. 

However for CR1, a 20 second duration to wait for modules to be picked up by server and properly deployed is as long as the job will wait. 
                
> Deployed module stays in [Stopped, Synchronized] state after being deployed
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-14895
>                 URL: https://issues.jboss.org/browse/JBIDE-14895
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.1.0.Beta2
>         Environment: JBDS 7.0.0.Beta2, JBoss AS 7.1.1, EAP 6.1
>            Reporter: Radim Hopp
>            Assignee: Rob Stryker
>             Fix For: 4.1.0.CR1
>
>
> When deploying project (tried few projects from JBoss Central) to running server (I have tried JBoss AS 7.1.1 and EAP 6.1), the project stays in {noformat}[Stopped, Synchronized]{noformat} state, even though the project was successfuly deployed and is running.

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