JBoss AS 7.1.3 - Thread pool configuration for @Asynchronous EJB invocations

[jmsjr]

JBoss AS 7.1.3

I can't seem to find anywhere in the documentation the following:

1) What is the default configuration for the thread pool used for @Asynchronous method invocations ?

2) How can I change the thread pool used for @Asynchronous method invocations ?

3) Is the thread pool used for @Asynchronous method invocations also used for other purposes ? Is it thread pool shared for other purposes ( e.g. all EJB method invocations, asynchronous or not ) ?

4) Can I have a separate thread pool specifically just for @Asynchronous method invocations ?

Any pointers / references greatly appreciated.

[jmsjr]

The closest thing that I found was this:

[JBAS-9356] Move the ejb3-async-deployer-jboss-beans.xml out of the jar so that it can be configured by users  - JBoss I…

... but that was for JBoss AS 6.1.0, not JBoss AS 7.1.3. There is no jboss-ejb3-async-deployer.jar in JBoss AS 7.1.3

[sfcoy]

If you look in your standalone.xml file, you will find:

<async thread-pool-name="default"/>

defined in the ejb subsystem section. A little below that, you will also find:

            <thread-pools>
                <thread-pool name="default">
                    <max-threads count="10"/>
                    <keepalive-time time="100" unit="milliseconds"/>
                </thread-pool>
            </thread-pools>

Hopefully, that will give you enough clues.

[jmsjr]

Stephen Coy wrote:

If you look in your standalone.xml file, you will find:

1. <async thread-pool-name="default"/> 

defined in the ejb subsystem section. A little below that, you will also find:

1.             <thread-pools> 
2.                 <thread-pool name="default"> 
3.                     <max-threads count="10"/> 
4.                     <keepalive-time time="100" unit="milliseconds"/> 
5.                 </thread-pool> 
6.             </thread-pools> 

Hopefully, that will give you enough clues.

Great! Thanks. I can actually configure a different pool just for @Asynchronous method invocations

[sfcoy]

It's worthwhile developing a JBoss CLI script to do this (and any other) configuration as it will make server updates a breeze.