[jbossts-issues] [JBoss JIRA] (JBTM-2633) Arquillian server startup timeout should be configurable in tests

Tom Jenkinson (JIRA) issues at jboss.org
Fri Mar 4 12:39:00 EST 2016

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

Tom Jenkinson updated JBTM-2633:
           Status: Resolved  (was: Pull Request Sent)
    Fix Version/s: 5.next
       Resolution: Done

> Arquillian server startup timeout should be configurable in tests
> -----------------------------------------------------------------
>                 Key: JBTM-2633
>                 URL: https://issues.jboss.org/browse/JBTM-2633
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: Testing
>    Affects Versions: 5.2.14.Final
>            Reporter: Ondřej Chaloupka
>            Assignee: Ondřej Chaloupka
>             Fix For: 5.next
> Arquillian configuration for tests which lays in _arquillian.xml_ currently does not permit changing timeou for server startup. Default timeout for server startup is 60 seconds. If server is not up and running till that time Arquillian stops the serve process and {{LifecycleException}} is thrown informing that server was not started.
> If tests (like txbridge or xts) are run with container which uses _jdbc object store_ and connection to database is slow. It could happen that 60 seconds is not enough for serve being started and tests start to fail. The easy solution is to wait a bit more for server would be started.
> Then add configuration property {{startupTimeoutInSeconds}} to {{arquillian.xml}} files which are configured to start jboss/wildfly server and let user to configure the option.

This message was sent by Atlassian JIRA

More information about the jbossts-issues mailing list