[
https://issues.jboss.org/browse/WFLY-12669?page=com.atlassian.jira.plugin...
]
Tommasso Borgato updated WFLY-12669:
------------------------------------
Description:
The issue is about scattered cache replication across cluster nodes;
WildFly is started in clustered mode using a scattered cache for replicating HTTP session
data across cluster nodes; all 4 nodes in the cluster are initialized with the following
`cli` script:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
/subsystem=infinispan/cache-container=web/scattered-cache=testScattered:add()
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache,
value=testScattered)
{noformat}
The test is run with version `wildfly-18.0.0.Final.zip`; the same tests run with version
`wildfly-17.0.1.Final.zip` do not have any problem; hence this looks like a regression:
- OK [eap-7.x-clustering-http-session-shutdown-scattered with
wildfly-17.0.1.Final.zip](https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.re...
- ERROR [eap-7.x-clustering-http-session-shutdown-scattered with
wildfly-18.0.0.Final.zip](https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.re...
On the server we deploy, as usual, `clusterbench` (see attachment clusterbench-ee8.ear).
As usual, we test that the serial value stored in the scattered cache is incremented at
every call: we observed 97617 inconsistencies meaning e.g. 3 was expected but 2 was
received;
was:
The issue is about scattered cache replication across cluster nodes;
WildFly is started in clustered mode using a scattered cache for replicating HTTP session
data across cluster nodes; all 4 nodes in the cluster are initialized with the following
`cli` script:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
/subsystem=infinispan/cache-container=web/scattered-cache=testScattered:add()
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache,
value=testScattered)
{noformat}
The test is run with version `wildfly-18.0.0.Final.zip`; the same tests run with version
`wildfly-17.0.1.Final.zip` do not have any problem; hence this looks like a regression:
- OK [eap-7.x-clustering-http-session-shutdown-scattered with
wildfly-17.0.1.Final.zip](https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.re...
- ERROR [eap-7.x-clustering-http-session-shutdown-scattered with
wildfly-18.0.0.Final.zip](https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.re...
On the server we deploy, as usual, `clusterbench` (see attachment clusterbench-ee8.ear).
As usual, we test that the serial value stored in the scattered cache is incremented at
every call: we observer 97617 inconsistencies meaning e.g. 3 was expected but 2 was
received;
Clustering: scattered cache errors
----------------------------------
Key: WFLY-12669
URL:
https://issues.jboss.org/browse/WFLY-12669
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 18.0.0.Final
Reporter: Tommasso Borgato
Assignee: Paul Ferraro
Priority: Critical
Attachments: clusterbench-ee8.ear
The issue is about scattered cache replication across cluster nodes;
WildFly is started in clustered mode using a scattered cache for replicating HTTP session
data across cluster nodes; all 4 nodes in the cluster are initialized with the following
`cli` script:
{noformat}
embed-server --server-config=standalone-ha.xml
/subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp)
/subsystem=infinispan/cache-container=web/scattered-cache=testScattered:add()
/subsystem=infinispan/cache-container=web:write-attribute(name=default-cache,
value=testScattered)
{noformat}
The test is run with version `wildfly-18.0.0.Final.zip`; the same tests run with version
`wildfly-17.0.1.Final.zip` do not have any problem; hence this looks like a regression:
- OK [eap-7.x-clustering-http-session-shutdown-scattered with
wildfly-17.0.1.Final.zip](https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.re...
- ERROR [eap-7.x-clustering-http-session-shutdown-scattered with
wildfly-18.0.0.Final.zip](https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.re...
On the server we deploy, as usual, `clusterbench` (see attachment clusterbench-ee8.ear).
As usual, we test that the serial value stored in the scattered cache is incremented at
every call: we observed 97617 inconsistencies meaning e.g. 3 was expected but 2 was
received;
--
This message was sent by Atlassian Jira
(v7.13.8#713008)