Configure threadpools for infinispan on wildfly 8.2.0
thomash Nov 4, 2015 10:09 AMI'm having difficulties configuring dedicated threadpools for infinispan on wildfly 8.2.0.
The documentation states I should use the existing threads subsystem (https://docs.jboss.org/author/display/WFLY8/Threads+subsystem+configuration)
This subsystem is however deprecated: it is no longer included in the standalone.xml or standalone-ha.xml. (it was still there with wildfly 8.0.0)
So I tried this suggestion: https://developer.jboss.org/message/922751
This broke the xml-validity: the infinispan-subsystem ("urn:jboss:domain:infinispan:2.0") doesn't have a '<thread-factory>' element
This is what I tried:
<subsystem xmlns="urn:jboss:domain:infinispan:2.0"> <thread-factory name="infinispan-thread-factory" /> <bounded-queue-thread-pool name="infinispan-transport"> <core-threads count="1"/> <queue-length count="100000"/> <max-threads count="25"/> <thread-factory name="infinispan-thread-factory"/> </bounded-queue-thread-pool> <bounded-queue-thread-pool name="infinispan-listener"> <core-threads count="1"/> <queue-length count="100000"/> <max-threads count="1"/> <thread-factory name="infinispan-factory"/> </bounded-queue-thread-pool> <scheduled-thread-pool name="infinispan-eviction"> <max-threads count="1"/> <thread-factory name="infinispan-factory"/> </scheduled-thread-pool> <scheduled-thread-pool name="infinispan-repl-queue"> <max-threads count="1"/> <thread-factory name="infinispan-factory"/> </scheduled-thread-pool> <cache-container .../> </subsystem>
This results in :
Message: JBAS014789: Unexpected element '{urn:jboss:domain:infinispan:2.0}thread-factory' encountered
When I try to include the threads subsystem anyway (as described here Threads subsystem configuration - WildFly 8 - Project Documentation Editor and How to configure threads in Infinispan - WildFly 8), the server doesn't startup either. Looks like some sort of deadlock.
According to [WFLY-497] Infinispan thread pool injection - JBoss Issue Tracker threadpool injection for infinispan is only fixed for wildfly 10.
I 'suspect' infinispan currently uses (on wildfly 8.2.0) threadpools from the ee-subsystem (urn:jboss:domain:ee:2.0, managed-executor-services), but I would like to have more control.
So what is the correct way to use a 'isolated' theadpool for infinispan?
Message was edited by: Thomas Houtekier strikethrough wrong statement. I must have done something wrong there