[JBoss JIRA] (WFLY-4854) Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar)
by Martin Simka (JIRA)
Martin Simka created WFLY-4854:
----------------------------------
Summary: Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar)
Key: WFLY-4854
URL: https://issues.jboss.org/browse/WFLY-4854
Project: WildFly
Issue Type: Bug
Components: Application Client
Reporter: Martin Simka
Assignee: Stuart Douglas
Exclude org.jboss.logmanager:jboss-logmanager from wildfly-client-all (jboss-client.jar)
its presence causes TCK failures with error:
{noformat}
IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
{noformat}
as LogManager is loaded twice, from jboss-client.jar and from module. It was brought in together with ActiveMQ Artemis messaging.
{noformat}
[INFO] --- maven-dependency-plugin:2.9:tree (default-cli) @ wildfly-client-all ---
[INFO] org.wildfly:wildfly-client-all:jar:10.0.0.Alpha5-SNAPSHOT
[INFO] +- org.wildfly:wildfly-ejb-client-bom:pom:10.0.0.Alpha5-SNAPSHOT:compile
[INFO] | +- org.jboss:jboss-ejb-client:jar:2.1.1.Final:compile
[INFO] | +- org.jboss:jboss-remote-naming:jar:2.0.4.Final:compile
[INFO] | +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile
[INFO] | +- org.jboss.marshalling:jboss-marshalling:jar:1.4.10.Final:compile
[INFO] | +- org.jboss.marshalling:jboss-marshalling-river:jar:1.4.10.Final:compile
[INFO] | +- org.jboss.remoting:jboss-remoting:jar:4.0.9.Final:compile
[INFO] | +- org.jboss.sasl:jboss-sasl:jar:1.0.5.Final:compile
[INFO] | +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final:compile
[INFO] | +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final:compile
[INFO] | +- org.jboss.xnio:xnio-api:jar:3.3.1.Final:compile
[INFO] | \- org.jboss.xnio:xnio-nio:jar:3.3.1.Final:compile
[INFO] +- org.wildfly:wildfly-jms-client-bom:pom:10.0.0.Alpha5-SNAPSHOT:compile
[INFO] | +- org.apache.activemq:artemis-commons:jar:1.0.0:compile
[INFO] | | +- org.jboss.logmanager:jboss-logmanager:jar:2.0.0.Final:compile
[INFO] | | \- commons-beanutils:commons-beanutils:jar:1.9.2:compile
[INFO] | | \- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] | +- org.apache.activemq:artemis-core-client:jar:1.0.0:compile
[INFO] | | +- org.jgroups:jgroups:jar:3.6.4.Final:compile
[INFO] | | +- org.apache.activemq:artemis-selector:jar:1.0.0:compile
[INFO] | | \- org.apache.activemq:artemis-journal:jar:1.0.0:compile
[INFO] | | \- org.apache.activemq:artemis-native:jar:1.0.0:compile
[INFO] | +- org.apache.activemq:artemis-jms-client:jar:1.0.0:compile
[INFO] | | +- org.apache.geronimo.specs:geronimo-jms_2.0_spec:jar:1.0-alpha-1:compile
[INFO] | | \- javax.inject:javax.inject:jar:1:compile
[INFO] | +- org.hornetq:hornetq-commons:jar:2.4.7.Final:compile
[INFO] | +- org.hornetq:hornetq-core-client:jar:2.4.7.Final:compile
[INFO] | | \- org.hornetq:hornetq-journal:jar:2.4.7.Final:compile
[INFO] | | \- org.hornetq:hornetq-native:jar:2.4.7.Final:compile
[INFO] | +- org.hornetq:hornetq-jms-client:jar:2.4.7.Final:compile
[INFO] | +- io.netty:netty-all:jar:4.0.26.Final:compile
[INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile
[INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:compile
[INFO] | \- org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1:compile
[INFO] +- org.jboss.remotingjmx:remoting-jmx:jar:2.0.1.Final:compile
[INFO] \- org.wildfly.checkstyle:wildfly-checkstyle-config:jar:1.0.3.Final:compile
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4853) Provide two cluster test case for EJBClient
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz reassigned WFLY-4853:
-----------------------------------------
Assignee: Richard Achmatowicz
> 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
> Assignee: Richard Achmatowicz
>
> The Wildfly test suite 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 shut down and then restarted in turn, at which time the test ends.
> The expected behaviour:
> - at least 90% of client invocations will complete without exception
> - 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 fail-over from node3 to node 4 (or vice versa depending on which node of cluster ejb is down)
> The invocation transaction attribute set up:
> - 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, which uncovered a number of issues...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4853) Provide two cluster test case for EJBClient
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on WFLY-4853 at 7/1/15 10:58 AM:
--------------------------------------------------------------------
The test case has identified a number of issues:
- problems with ejb cache renaming (https://issues.jboss.org/browse/WFLY-3290)
- problems with batching in Wildfly clustering (https://issues.jboss.org/browse/WFLY-4678)
- problems with EJBClient and clean shutdown (https://issues.jboss.org/browse/WFLY-4697)
- problems with EJBCLient retry mechanism being used with invocations from a managed context (see https://issues.jboss.org/browse/EJBCLIENT-137 )
I'm currently working on resolving the last issue.
was (Author: rachmato):
The test case has identified a number of issues:
- problems with ejb cache renaming (https://issues.jboss.org/browse/WFLY-3290)
- problems with batching in Wildfly clustering (https://issues.jboss.org/browse/WFLY-4678)
- problems with EJBClient and clean shutdown (https://issues.jboss.org/browse/WFLY-4697)
- problems with EJBCLient retry mechanism being used with invocations from a managed context (see https://issues.jboss.org/browse/WFLY-4697)
I'm currently working on resolving the last issue.
> 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 test suite 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 shut down and then restarted in turn, at which time the test ends.
> The expected behaviour:
> - at least 90% of client invocations will complete without exception
> - 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 fail-over from node3 to node 4 (or vice versa depending on which node of cluster ejb is down)
> The invocation transaction attribute set up:
> - 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, which uncovered a number of issues...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4853) Provide two cluster test case for EJBClient
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated WFLY-4853:
--------------------------------------
Description:
The Wildfly test suite 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 shut down and then restarted in turn, at which time the test ends.
The expected behaviour:
- at least 90% of client invocations will complete without exception
- 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 fail-over from node3 to node 4 (or vice versa depending on which node of cluster ejb is down)
The invocation transaction attribute set up:
- 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, which uncovered a number of issues...
was:
The Wildfly test suite 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 shut down and then restarted in turn, at which time the test ends.
The expected behaviour is that:
- at least 90% of client invocations will complete without exception
- 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 fail-over 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 test suite 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 shut down and then restarted in turn, at which time the test ends.
> The expected behaviour:
> - at least 90% of client invocations will complete without exception
> - 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 fail-over from node3 to node 4 (or vice versa depending on which node of cluster ejb is down)
> The invocation transaction attribute set up:
> - 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, which uncovered a number of issues...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4853) Provide two cluster test case for EJBClient
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated WFLY-4853:
--------------------------------------
Description:
The Wildfly test suite 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 shut down and then restarted in turn, at which time the test ends.
The expected behaviour:
- at least 90% of client invocations will complete without exception
- 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 fail-over from node3 to node 4 (or vice versa depending on which node of cluster ejb is down)
The invocation transaction attribute set up:
- 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, which uncovered a number of issues...
was:
The Wildfly test suite 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 shut down and then restarted in turn, at which time the test ends.
The expected behaviour:
- at least 90% of client invocations will complete without exception
- 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 fail-over from node3 to node 4 (or vice versa depending on which node of cluster ejb is down)
The invocation transaction attribute set up:
- 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, which uncovered a number of issues...
> 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 test suite 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 shut down and then restarted in turn, at which time the test ends.
> The expected behaviour:
> - at least 90% of client invocations will complete without exception
> - 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 fail-over from node3 to node 4 (or vice versa depending on which node of cluster ejb is down)
> The invocation transaction attribute set up:
> - 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, which uncovered a number of issues...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (WFLY-4853) Provide two cluster test case for EJBClient
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-4853:
-------------------------------------------
By the way, a similar test case was created for EAP 6: https://github.com/rachmatowicz/jboss-eap/tree/twoclustertest
I seem to remember there was a problem getting it merged as the upstream test case was not present.
Need to revisit that.
> 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 test suite 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 shut down and then restarted in turn, at which time the test ends.
> The expected behaviour is that:
> - at least 90% of client invocations will complete without exception
> - 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 fail-over 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)
8 years, 9 months
[JBoss JIRA] (WFLY-4853) Provide two cluster test case for EJBClient
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated WFLY-4853:
--------------------------------------
Description:
The Wildfly test suite 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 shut down and then restarted in turn, at which time the test ends.
The expected behaviour is that:
- at least 90% of client invocations will complete without exception
- 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 fail-over 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 test suite 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 shut down and then restarted in turn, at which time the test ends.
The expected behaviour 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 fail-over 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 test suite 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 shut down and then restarted in turn, at which time the test ends.
> The expected behaviour is that:
> - at least 90% of client invocations will complete without exception
> - 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 fail-over 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)
8 years, 9 months
[JBoss JIRA] (WFLY-4853) Provide two cluster test case for EJBClient
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-4853?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-4853:
-------------------------------------------
The test case has identified a number of issues:
- problems with ejb cache renaming (https://issues.jboss.org/browse/WFLY-3290)
- problems with batching in Wildfly clustering (https://issues.jboss.org/browse/WFLY-4678)
- problems with EJBClient and clean shutdown (https://issues.jboss.org/browse/WFLY-4697)
- problems with EJBCLient retry mechanism being used with invocations from a managed context (see https://issues.jboss.org/browse/WFLY-4697)
I'm currently working on resolving the last issue.
> 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 test suite 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 shut down and then restarted in turn, at which time the test ends.
> The expected behaviour 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 fail-over 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)
8 years, 9 months