EJB's and Threading

java jakarta-ee ejb message-driven-bean
TheWolf picture TheWolf · Jan 3, 2011 · Viewed 16.2k times · Source

From what I understand it is illegal to spawn threads from within an EJB as it may potentially interfere with the EJB's lifecycle. However, is it illegal to use predefined Java classes from the JDK which internally spawn and handle threads such as Executor within an EJB, specifically an MDB?

Answer

jtahlborn picture jtahlborn · Jan 3, 2011

You "cannot" (should not) use threads, thread pools, executors... all of the above. the point of using an app server is to only write business logic and let the app server do the heavy lifting. if you really, really need to do your own threading, use an EJB 3.1 "singleton" service to manage the threading. however, as mentioned by others, it's best to leave this to the app server. one way to do parallel processing in an app server is to use MDBs (which it sounds like you already are using), although depending on the type of parallel processing, these may be too heavyweight.

Related questions

Should I use @EJB or @Inject

I have found this question: What is the difference between @Inject and @EJB but I did not get any wiser. I have not done Java EE before nor do I have experience with dependency injection so I do not understand …

Read More
Stateless and Stateful Enterprise Java Beans

I am going through the Java EE 6 tutorial and I am trying to understand the difference between stateless and stateful session beans. If stateless session beans do not retain their state in between method calls, why is my program acting …

Read More
What does the @EJBs annotation do?

I know roughly what this construction does: it creates a SomeType EJB and injects the object into another EJB. @EJB(name="name1") SomeType someVariable Now I have a class which starts like this: (I give all class-level annotations, even though …

Read More