[jbosstools-issues] [JBoss JIRA] (JBIDE-16400) Timeout shutdown poller does not wait for timeout

[Martin Malina (JIRA)]

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

Martin Malina updated JBIDE-16400:
----------------------------------

         Fix Version/s: 4.2.0.Alpha2
           Description: When you select "Timeout" as the Shutdown poller in server editor, one would expect the server to show stopped only after the timeout has elapsed (like it happens with the Timeout startup poller). Instead, the server is shown instantly once you stop the server.
    Steps to Reproduce: 
1. Add EAP 6.2 as a server
2. Open the server editor by double-clicking the server in the server view
3. Select both startup and shutdown pollers to "timeout" and save the editor
4. Start the server (by clicking the start button in the server view)
Server will be in the "Starting" state until the timeout is reached - good
5. Stop the server (by clicking the stop button in the server view)
Server will switch to "Stopped" immediately - FAIL - it should wait for the timeout
     Affects Version/s: 4.1.1.Final
           Environment: 
JBDS 7.1.0.GA
EAP 6.2.0
           Component/s: server

    
> Timeout shutdown poller does not wait for timeout
> -------------------------------------------------
>
>                 Key: JBIDE-16400
>                 URL: https://issues.jboss.org/browse/JBIDE-16400
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.1.1.Final
>         Environment: JBDS 7.1.0.GA
> EAP 6.2.0
>            Reporter: Martin Malina
>             Fix For: 4.2.0.Alpha2
>
>
> When you select "Timeout" as the Shutdown poller in server editor, one would expect the server to show stopped only after the timeout has elapsed (like it happens with the Timeout startup poller). Instead, the server is shown instantly once you stop the server.

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