-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
8.1.0.Beta
-
None
-
False
-
None
-
False
-
-
-
-
-
-
Known Issue
-
-
Scenario: we have a 4 nodes cluster which is using an Oracle Db to offload session data:
embed-server --server-config=standalone-ha.xml /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) /subsystem=infinispan/cache-container=web/invalidation-cache=offload:add() data-source add --name=testDS --jndi-name=java:jboss/datasources/testDS --driver-name=oracle-connector.jar --connection-url=jdbc:oracle:thin:@10.0.190.167:1521/FREEPDB1 --enabled=true --jta=true --use-java-context=true --transaction-isolation=TRANSACTION_READ_COMMITTED --min-pool-size=10 --max-pool-size=25 --pool-prefill=true --user-name=EAP_QE --password=test /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc:add(data-source=testDS,fetch-state=false,passivation=false,purge=false,shared=true,dialect=ORACLE){allow-resource-service-restart=true} /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.name,value=id) /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.name,value=datum) /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.name,value=version) /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=id-column.type,value=VARCHAR2(255)) /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=timestamp-column.type,value=NUMBER) /subsystem=infinispan/cache-container=web/invalidation-cache=offload/store=jdbc/table=string:write-attribute(name=data-column.type,value=BLOB) /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=offload) /subsystem=transactions:write-attribute(name=node-identifier,value=wildfly1)
Moving from "8.0.5.GA-SP1-CR1" to "8.1.0.Beta-CR2" we notices a few new cache errors, e.g. (see run #53 linked in comment):
Invalid serial: Expected 188, received 0 (previous: JSessionId{sessionId='P1apAKYlczlvZNaU7sZu7DgT4XYobp1tKrhyJG5U', jvmRoutes=[wildfly1]} current: JSessionId{sessionId='RKFZ3x_AhordMqePu3ua3MUWTVSFHVMYmEnRlMMS', jvmRoutes=[wildfly2]})
This one above, happens right after the 4rth node has been shut down: it looks like the session is lost and re-created;
We marked this as a blocked because it looks like a regression; anyway the client fail rate is just slightly affected since we observed just a few of these errors;
Yet another example of the same kind:
1. Session "07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly" is created on node1 (see run #51 linked in comment):
2025-02-03 05:40:31,862 INFO [org.jboss.test.clusterbench.common.session.CommonHttpSessionServlet] (default task-1) New session created: 07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly with 4kB cargoo
2. as node2 is shut down, session "07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly" has a "jvmRoute" change and the session is recreated with a different ID::
2025-02-03 05:45:08,174 INFO o.j.e.c.j.u.LogLoader: CLUSTERING_LIFECYCLE_MARKER: FAIL SHUTDOWN WildFly Service 2 2025-02-03 05:45:07.555 ... 2025-02-03 05:45:12,308 WARN o.j.e.c.j.ClusteringHTTPRequestSampler: Thread Group 1-307: Serial 70: Session ID changed: JSessionId{sessionId='07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly', jvmRoutes=[wildfly4]} -> JSessionId{sessionId='yij7oC-mHM-oh83UM-R19xBOUZkJZL_SZAekyAYU', jvmRoutes=[wildfly3]} 2025-02-03 05:45:12,309 ERROR o.j.e.c.j.ClusteringHTTPRequestSampler: Invalid serial: Expected 70, received 0 (previous: JSessionId{sessionId='07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly', jvmRoutes=[wildfly4]} current: JSessionId{sessionId='yij7oC-mHM-oh83UM-R19xBOUZkJZL_SZAekyAYU', jvmRoutes=[wildfly3]}) samples sequence: 05:40:31.863 serial 0 JSessionId{sessionId='07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly', jvmRoutes=[wildfly1]} ... 05:41:23.914 serial 13 JSessionId{sessionId='07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly', jvmRoutes=[wildfly1]} 05:41:27.924 serial 14 JSessionId{sessionId='07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly', jvmRoutes=[wildfly3]} ... 05:43:20.079 serial 42 JSessionId{sessionId='07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly', jvmRoutes=[wildfly3]} 05:43:24.087 serial 43 JSessionId{sessionId='07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly', jvmRoutes=[wildfly4]} ... 05:45:08.204 serial 69 JSessionId{sessionId='07ZK8EFicjg43hcmR5TwWmshyXFWX3PNPCnvL9Ly', jvmRoutes=[wildfly4]} 05:45:12.309 serial 0 JSessionId{sessionId='yij7oC-mHM-oh83UM-R19xBOUZkJZL_SZAekyAYU', jvmRoutes=[wildfly3]}
- is cloned by
-
WFLY-20427 Cache inconsistencies when using ORACLE Database
-
- Resolved
-
- is incorporated by
-
JBEAP-29546 Upgrade JBoss EAP 8.1 Build to c342ef47b0f883d58756deeb6680939e64c6d37b
-
- Verified
-
- relates to
-
JBEAP-29376 [CLUSTERING] Cache inconsistencies in fail-over tests
-
- New
-