Dont you think it means the async thread pool has a size of 3? (i ask but...) Le 7 janv. 2014 21:34, "Howard W. Smith, Jr." <[email protected]> a écrit :
> Stuart, > > On Tue, Jan 7, 2014 at 3:03 PM, Stuart Easterling < > [email protected]> wrote: > > > Romain, if you add the annotation @Asynchronous to your foo() business > > method in TestBean it reproduces the behavior I have been having. > > > > I'm definitely not one of the committers (or expert users), but your > questions/threads, today, remind me of some related topics discussed on > this tomee user list. > > Recent (possibly related) topics are: > > @Asynchronous And TransactionRequiredException > > and > > initial size of pool of stateless beans > > You can search google + tomee user list for those topic titles, above, and > read them. In one of those topics, I think I stated that I would never add > @Asynchronous to @Stateless bean. As a java EE newbie that learned java EE > via Java EE 6 tutorial and NetBeans, I never seen the two married together > in tutorial or in any working examples, but I've seen others on this list > marry the two together. > > In my understanding/experience of @Asynchronous... use the same (@Stateless > test) bean, but execute the @Asynchronous 'method'...later, and hope it > executes. I think I've even heard David Blevins (TomEE lead/committer) > state that @Asynchronous is not always/fully reliable. I think Romain will > disagree with that though. :) > > I use @Asynchronous only with @SessionScoped beans...as > documented/demonstrated/suggested in Java EE 6 tutorial. I think TomEE > allows @Asynchronous + @Stateless, because of the DeltaSpike/OpenEJB > features in TomEE. :) >
