[jboss-jira] [JBoss JIRA] (WFLY-13123) Server stopping at RemoteEJBClientStatefulBeanFailoverTestCase needs to be guarded with timeout otherwise the server stop may stuck further test processing

Ondrej Chaloupka (Jira) issues at jboss.org
Tue Feb 18 11:00:29 EST 2020


     [ https://issues.redhat.com/browse/WFLY-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Chaloupka updated WFLY-13123:
------------------------------------
    Summary: Server stopping at RemoteEJBClientStatefulBeanFailoverTestCase needs to be guarded with timeout otherwise the server stop may stuck further test processing  (was: Server stopping at RemoteEJBClientStatefulFailoverTestBase needs to be guarded with timeout otherwise the server stop may stuck further test processing)


> Server stopping at RemoteEJBClientStatefulBeanFailoverTestCase needs to be guarded with timeout otherwise the server stop may stuck further test processing
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-13123
>                 URL: https://issues.redhat.com/browse/WFLY-13123
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 19.0.0.Beta2
>            Reporter: Ondrej Chaloupka
>            Assignee: Ondrej Chaloupka
>            Priority: Major
>
> The clustering test {{RemoteEJBClientStatefulFailoverTestBase}} works with stopping WildFly server to check how clustering and balancing of ejb client works.
> The call of the management operation {{stop}} is not guarded with timeout option currently.
> That could make a trouble (and at Narayana CI) of long standing stopping server which is waiting to be stopped.
> The {{stop}} operation should be guarded with timeout option to not being infinite.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list