Details
-
Bug
-
Resolution: Done
-
Critical
-
8.0.0.Beta-CR1
-
False
-
None
-
False
Description
In the heavyread scenario (4 nodes cluster using web replicated cache) we noticed the following exception in the server logs (see wlf_20225405-085430-wildfly-service-1-server.log ):
2022-12-05 09:12:22,021 FATAL [org.jgroups.protocols.TCP] (Connection.Receiver [10.0.154.188:38511 - 10.0.153.226:7600]-14,ejb,wildfly1) wildfly1: thread pool is full (max=100, active=200); thread dump (dumped once, until thread_dump is reset): "Reference Handler" #2 prio=0 tid=0x2 nid=NA runnable java.lang.Thread.State: RUNNABLE at java.base@11.0.16/java.lang.ref.Reference.waitForReferencePendingList(Native Method) at java.base@11.0.16/java.lang.ref.Reference.processPendingReferences(Reference.java:241) at java.base@11.0.16/java.lang.ref.Reference$ReferenceHandler.run(Reference.java:213)
Cluster nodes are configured as follows:
embed-server --server-config=standalone-ha.xml if (outcome != success) of /subsystem=jgroups:read-attribute(name=default-stack) /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) else /subsystem=jgroups:write-attribute(name=default-stack,value=tcp) /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) end-if /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add() /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH) /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add() /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl)
Attachments
Issue Links
- is caused by
-
WFLY-18038 JGroups transport thread pool configuration is ignored
- Closed