-
Bug
-
Resolution: Done
-
Blocker
-
8.0.0.GA-CR1
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
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"
]
}
- clones
-
-
- Resolved
-
- is incorporated by
-
JBEAP-25614 (8.0.z) Upgrade hal console from 3.6.12.Final to 3.6.15.Final
-
- Closed
-
