-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
Starting with WildFly 27, the cache-container resource has changed. This breaks the cache container view in the console.
The reason is the deprecation of some of the thread-pool singletons:
WildFly 26
/subsystem=infinispan/cache-container=ejb:read-children-types(include-singletons)
{
"outcome" => "success",
"result" => [
"cache",
"distributed-cache",
"invalidation-cache",
"local-cache",
"replicated-cache",
"scattered-cache",
"thread-pool=async-operations",
"thread-pool=blocking",
"thread-pool=expiration",
"thread-pool=listener",
"thread-pool=non-blocking",
"thread-pool=persistence",
"thread-pool=remote-command",
"thread-pool=state-transfer",
"thread-pool=transport",
"transport=jgroups",
"transport=none"
]
}
WildFly >26
/subsystem=infinispan/cache-container=ejb:read-children-types(include-singletons)
{
"outcome" => "success",
"result" => [
"cache",
"distributed-cache",
"invalidation-cache",
"local-cache",
"replicated-cache",
"scattered-cache",
"thread-pool=blocking",
"thread-pool=expiration",
"thread-pool=listener",
"thread-pool=non-blocking",
"transport=jgroups",
"transport=none"
]
}
Tests in Manatoko need to be re-enabled once this is fixed.
- is cloned by
-
JBEAP-25635 Fix cache container view in web console
-
- Closed
-
- is incorporated by
-
WFLY-18521 Upgrade HAL to 3.6.15.Final
-
- Closed
-
- is triggered by
-
HAL-1890 Investigate failures in test-configuration-infinispan manatoko module
-
- Resolved
-