[jboss-jira] [JBoss JIRA] (WFLY-1458) Allow specifying timeout for org.jboss.as.arquillian.container.ManagementClient.isServerInRunningState()

[Ladislav Thon (JIRA)]

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

Ladislav Thon commented on WFLY-1458:
-------------------------------------

I believe I have reproduces the same issue. In fact, the connection won't hang indefinitely -- it will only hang for cca 50 minutes (in default settings). That's because the loop in {{ManagedDeployableContainer.startInternal}} assumes that {{ManagementClient.isServerInRunningState()}} is cheap, which it doesn't have to be. It can fall into a trap and the IO will have to time out. By default, that timeout is 5 seconds, which means that the container startup timeout is prolonged cca 50x (which gives the 50 minutes -- the default container startup timeout is 1 minute).

I have a proposed fix in this pull request: https://github.com/wildfly/wildfly/pull/5334
                
> Allow specifying timeout for org.jboss.as.arquillian.container.ManagementClient.isServerInRunningState()
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1458
>                 URL: https://issues.jboss.org/browse/WFLY-1458
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Richard Achmatowicz
>            Assignee: Aslak Knutsen
>         Attachments: thread.dump.txt
>
>
> When deploying a container, Arquillian will use a management client to connect to the deployed container to see if it is in a running state. If the management address and management port are incorrect, the connection to the container hangs indefinitely.
> Please allow configuration of a timeout so that if the connection paramaters are not correct, at least the container deployment will fail with a meaningful error.

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