[quote=mvatkina]
This is what GlassFish docs say:
.. Priority Based Scheduling of Remote Bean Invocations
You can create multiple thread pools, each having its own work queues. An
optional element in the glassfish-ejb-jar.xml file, use-thread-pool-id,
specifies the thread pool that processes the requests for the bean. The bean
must have a remote interface, or use-thread-pool-id is ignored. You can
create different thread pools and specify the appropriate thread pool ID for
a bean that requires a quick response time. If there is no such thread pool
configured or if the element is absent, the default thread pool is used.
HTH,
-marina
[/quote]
Pretty sure this only applies to remote EJB invocations. I'm trying to
execute async methods on local instances. I've done some more testing and it
seems like the async thread pool size is fixed at 16, which is, at least for
me, not acceptable. Again, thanks for the help.
--
[Message sent by forum member 'karl.vizmatik']
View Post: http://forums.java.net/node/804293