[jboss-jira] [JBoss JIRA] (WFLY-12194) Add a testcase that checks remote client transaction afinity in case of failed server

[Ondrej Chaloupka (Jira)]

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

Ondrej Chaloupka commented on WFLY-12194:
-----------------------------------------

for stateful bean there is such testcase in as testsuite here: https://github.com/wildfly/wildfly/blob/17.0.0.Final/testsuite/integration/clustering/src/test/java/org/jboss/as/test/clustering/cluster/ejb/remote/TransactionalRemoteStatefulEJBFailoverTestCase.java
The SFSB affinity works fine, the test should be enhanced for SLSB affinity as well.

> Add a testcase that checks remote client transaction afinity in case of failed server
> -------------------------------------------------------------------------------------
>
>                 Key: WFLY-12194
>                 URL: https://issues.jboss.org/browse/WFLY-12194
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Test Suite
>    Affects Versions: 17.0.0.Final
>            Reporter: Ondrej Chaloupka
>            Assignee: Ondrej Chaloupka
>            Priority: Major
>
> The remote client transaction affinity is not well covered in testsuite.
> Particularly, it would be good to test what happens when a transaction starts on a standalone client. The call goes to a stateless bean. There are two servers started in server that the client can choose. The client starts transaction, calls the bean and then the server fails. Will be the next call to bean fails correctly? (as it could be expected as the affinity points to the non-existent server, despite the fact there is another server deploying the same stateless bean)



--
This message was sent by Atlassian Jira
(v7.12.1#712002)