Home/ Questions/Q 8395303
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T20:15:56+00:00

Our application is launching a series of threads via the @Asynchronous annotation on EJBs.

  • 0

Our application is launching a series of threads via the @Asynchronous annotation on EJBs. However, JBoss (contrairy to this) is not limiting the number of threads launched. Debugging shows that it is using a default class rather than the one configured in the XML linked in the issue above. The comment on the class says:

Static singleton access to a default java.util.concurrent.ExecutorService
implementation used by clients who do not supply a
org.jboss.ejb3.async.spi.AsyncInvocation to handle asynchronous
EJB 3.1 invocations.

So the question is under what circumstances is JBoss not supplying an org.jboss.ejb3.async.spi.AsyncInvocation class and how can you ensure that this does happen?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    JBoss AS 6.1 should indeed limit the number of threads by default, but due to a bug this simply does not happen. The global setting is sadly ignored without warning.

    If it doesn’t concern too many beans, you can use the org.jboss.ejb3.annotation.Pool annotation:

    @Pool(value = POOL_IMPLEMENTATION_STRICTMAX, maxSize = 10)
public class SomeBean {
    // ...
}

    Be careful though, if I’m not mistaken this will create a pool per bean.

    • 0