[
https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz updated WFLY-4853:
--------------------------------------
Description:
The Wildfly testsuite is missing a test case for testing EJBClient interactions over two
clusters, which does exist in the EAP test cycle.
The test setup:
- two clusters
{noformat}
-- (ejb-forwarder = {node0, node1}
-- ejb={node3, node4})
{noformat}
where each node of cluster ejb-forwarder has a remote outbound connection to node3
- a forwarding SFSB deployment on cluster ejb-forwarder, which forwards invocations to
cluster ejb
- a non-forwarding deployment on cluster ejb
- a client which makes invocations on the clustered deployment on ejb-forwarder every 10
ms
The test execution:
Once the servers and deployments have been deployed, each server is shutdown and then
restarted in turn, at which time the test ends.
The expected behavior is that:
- all client invocations will complete
- test client invocations on ejb-forwarder will fail over from node0 to node1 (or vice
versa, depending on which node of cluster ejb-forwarder is down)
- server-client invocations on ejb will failover from node3 to node 4 (or vice versa
depending on which node of cluster ejb is down)
The transaction set up is currently:
- invocations from the client to ejb-forwarder are not in transaction scope
- invocations from ejb-forwarder to ejb are in transaction scope with attribute REQUIRED
This allows exercising invocations from a managed transaction context.
was:
The Wildfly testsuite is missing a test case for testing EJBClient interactions over two
clusters, which does exist in the EAP test cycle.
The test setup:
- two clusters (ejb-forwarder = {node0, node1}, ejb={node3, node4}) where each node of
clusterA has a remote outbound connection to node3
- a forwarding SFSB deployment on cluster ejb-forwarder, which forwards invocations to
cluster ejb
- a non-forwarding deployment on cluster ejb
- a client which makes invocations on the clustered deployment on ejb-forwarder every 10
ms
The test execution:
Once the servers and deployments have been deployed, each server is shutdown and then
restarted in turn, at which time the test ends.
The expected behavior is that:
- all client invocations will complete
- test client invocations on ejb-forwarder will fail over from node0 to node1 (or vice
versa, depending on which node of cluster ejb-forwarder is down)
- server-client invocations on ejb will failover from node3 to node 4 (or vice versa
depending on which node of cluster ejb is down)
The transaction set up is currently:
- invocations from the client to ejb-forwarder are not in transaction scope
- invocations from ejb-forwarder to ejb are in transaction scope with attribute REQUIRED
This allows exercising invocations from a managed transaction context.
Provide two cluster test case for EJBClient
-------------------------------------------
Key: WFLY-4853
URL:
https://issues.jboss.org/browse/WFLY-4853
Project: WildFly
Issue Type: Feature Request
Components: Test Suite
Affects Versions: 10.0.0.Alpha4
Reporter: Richard Achmatowicz
The Wildfly testsuite is missing a test case for testing EJBClient interactions over two
clusters, which does exist in the EAP test cycle.
The test setup:
- two clusters
{noformat}
-- (ejb-forwarder = {node0, node1}
-- ejb={node3, node4})
{noformat}
where each node of cluster ejb-forwarder has a remote outbound connection to node3
- a forwarding SFSB deployment on cluster ejb-forwarder, which forwards invocations to
cluster ejb
- a non-forwarding deployment on cluster ejb
- a client which makes invocations on the clustered deployment on ejb-forwarder every 10
ms
The test execution:
Once the servers and deployments have been deployed, each server is shutdown and then
restarted in turn, at which time the test ends.
The expected behavior is that:
- all client invocations will complete
- test client invocations on ejb-forwarder will fail over from node0 to node1 (or vice
versa, depending on which node of cluster ejb-forwarder is down)
- server-client invocations on ejb will failover from node3 to node 4 (or vice versa
depending on which node of cluster ejb is down)
The transaction set up is currently:
- invocations from the client to ejb-forwarder are not in transaction scope
- invocations from ejb-forwarder to ejb are in transaction scope with attribute REQUIRED
This allows exercising invocations from a managed transaction context.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)