[jboss-jira] [JBoss JIRA] (WFLY-9415) Add test cases to cover EJB client clustered session creation

[Richard Achmatowicz (JIRA)]

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

Richard Achmatowicz edited comment on WFLY-9415 at 10/3/17 12:32 PM:
---------------------------------------------------------------------

There are two test cases:
ClientStatefulSessionCreationTestCase
NamingStatefulSessionCreationTestCase

Each test covers the three test scenarios: 
* ClientStatefulSessionTestCase covers them by changing the default EJBClientContext for each test, as well as the server environment (via undeploy, deploy)
* NamingStatefulSessionTestCase covers them by changing the default EJBDirectory (JNDI environment) for each test, as well as the server environment (via undeploy, deploy). 



was (Author: rachmato):
There are two test cases:
ClientStatefulSessionCreationTestCase
NamingStatefulSessionCreationTestCase

Each test covers the three test scenarios. 
ClientStatefulSessionTestCase covers them by changing the default EJBClientContext for each test, as well as the server environment (via undeploy, deploy). NamingStatefulSessionTestCase covers them by changing the default EJBDirectory (JNDI environment) for each test, as well as the server environment (via undeploy, deploy). 


> Add test cases to cover EJB client clustered session creation
> -------------------------------------------------------------
>
>                 Key: WFLY-9415
>                 URL: https://issues.jboss.org/browse/WFLY-9415
>             Project: WildFly
>          Issue Type: Task
>          Components: Clustering, Test Suite
>    Affects Versions: 11.0.0.CR1
>            Reporter: Richard Achmatowicz
>            Assignee: Richard Achmatowicz
>             Fix For: 11.0.0.Final
>
>
> EJB client session creation involves creating a proxy for a SFSB deployed on a remote server, which has the side effect of creating a session instance on the chosen target node. 
> Whether or not the operation is successful depends on three factors: 
> * the connections defined in the EJB client configuration
> * the server environment in which the client is executing 
> * any strong affinity set by the client  
> These tests consider session creation in a clustered environment. The default server environment is a cluster called "ejb" with two nodes, "node-0" and "node-1".
> The following test scenarios are covered:
> 1. "normal" scenario
> *  client configuration: points to node-0
> *  server environment: module deployed on cluster "ejb" = {node-0, node-1}
> 2. "failover" scenario
> *  client configuration: points to node-0
> *  server environment: module deployed on cluster "ejb" = {node-1}
> 3. "bad connection" scenario
> *  client configuration: points to node-2 (non-existent)
> *  server environment: module deployed on cluster "ejb" = {node-0, node-1}
> As mentioned earlier, these tests operate in a single two-node cluster environment. A third singleton, non-clustered node added to the available environment would permit more complex scenarios (where we could test cluster affinity specification more directly). 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)