I have developed a work around on this issue and I want your opinion about it. It consist on the following.

1.- Deploy a service called custom-work-manager-service.xml defining a custom WorkManager with a custom thread pool with the following content

<server>

 <mbean code="org.jboss.util.threadpool.BasicThreadPool"
 name="custom.jca:service=CustomWorkManagerThreadPool">
 <!-- The name that appears in thread names -->
 <attribute name="Name">CustomWorkManager</attribute>
 <!-- The maximum amount of work in the queue -->
 <attribute name="MaximumQueueSize">10</attribute>
 <!-- The maximum number of active threads -->
 <attribute name="MinimumPoolSize">1</attribute>
 <!-- The maximum number of active threads -->
 <attribute name="MaximumPoolSize">10</attribute>
 <!-- How long to keep threads alive after their last work (default one minute) -->
 <attribute name="KeepAliveTime">60000</attribute>
 <!-- The behaviour when the queue is full -> the calling thread blocks until the queue has room -->
 <attribute name="BlockingMode">wait</attribute>
 </mbean>

 <mbean code="org.jboss.resource.work.JBossWorkManager"
 name="custom.jca:service=CustomWorkManager">
 <depends optional-attribute-name="ThreadPoolName">custom.jca:service=CustomWorkManagerThreadPool</depends>
 <depends optional-attribute-name="XATerminatorName">jboss:service=TransactionManager</depends>
 </mbean>

</server>

WorkManager customWorkManager = null;
 try {
 MBeanServer server = MBeanServerLocator.locateJBoss();
 customWorkManager = (WorkManager) server.getAttribute(new ObjectName(
 "custom.jca:service=CustomWorkManager"), "Instance");
 } catch (MalformedObjectNameException e) {
 // TODO
 } catch (Exception e) {
 // TODO
 }

Yeah, I've already tested my resource adapter with this configuration and it works successfully. I want only to know if this approach could have any undesirable impact in the application server.

For example, does this thread pool definition take threads from any underlying system thread pool, so that it could reduce available threads for other tasks on the server, otherwise, it creates a totally independent (but managed) thread pool?