6

Are Session Beans (stateless session beans, stateful session beans) Synchronized?

Sergio
  • 3,317
  • 5
  • 32
  • 51
B. S. Rawat
  • 1,874
  • 3
  • 22
  • 34
  • 1
    somebody asked me this question, what should be the correct answer? I didn't see any synchronized methods inside of EJB, I would say EJB is not synchronized. Like people used to ask "is Hashtable synchronized?" – B. S. Rawat May 21 '09 at 14:16
  • Technically your question is not clear. Do you mean: Need Session beans to be made thread safe? or Are session beans thread-safe? – V G Jul 29 '15 at 13:55

5 Answers5

6

Only one thread at a time will be accessing your beans. It is up to the application server to manage this. So you should not be using synchronized from within your beans. This is why a non-threadsafe like EntityManager can be an instance value and not have synchronization issues.

Rob Di Marco
  • 43,054
  • 9
  • 66
  • 56
  • Yeah thats fine, but somebody asked this question in a interview and I replied in the same way but he wasn't satisfied with my answer. – B. S. Rawat May 21 '09 at 04:03
  • 3
    It's always possible they didn't have a clue. – Charlie Martin May 21 '09 at 05:08
  • 1
    Exactly. Further, the new @AccessTimeout annotation allows you to configure, in a portable way, exactly how long you want a calling thread to wait for an instance to become available. Also note that the new @Singleton bean can be configured to allow multithreaded access but is not so by default. That decision was made in efforts to keep consistency behind the default rules for all Session beans (@Stateless, @Stateful, @Singleton) – David Blevins Nov 09 '10 at 22:03
  • 2
    Executing the same code more than once may cause problems. Stateless EJB method is executed paralely, as many http requests are made. There is no synchronization inside session. – Peter Šály Nov 23 '16 at 15:50
4

Stateless beans: Every thread/request will get different instance of EJB from pool. SLB should not hold any user session data, any state. The same code may be executed in parallel. One instance is accessed by one thread at a time.

Statefull beans are synchronized for user session. Every user will get own session scoped instance. Second thread/request will wait until the first thread finishes. Statefull EJB can hold user specific data. One user cannot execute same code in parallel. Different users may execute same code in parallel.

If accessing a resource that does not allow parallel access use Singleton EJB. As name implies there is only one instance. By default EJB Singleton can be accessed only by one thread (Container Managed Concurrency and @Lock(WRITE)).

Peter Šály
  • 2,848
  • 2
  • 12
  • 26
0

Stateless/Stateful session beans are thread safe. Because each request will get a dedicated instance of the bean and so it doesn't need to be synchronized.

Singleton session beans are shared and needs to be synchronized either by the container (Container Managed Concurrency - CMC) or by the user (Bean Managed Concurrency - BMC).

Sri
  • 4,613
  • 2
  • 39
  • 42
-3

Very True thing about EJB beans is that once you have created EJB 3.0 beans then the methods of the EJB is by default Synchronized.

e.g.

@Statelss Class EJBclass {

void someMethod(){ }

}

now if you will make this someMethod Synchronize it will show Error like it is can not be Synchronize at this level as it is synchronized.

EJB 3.0 Beans are smart and performance is good.

JavaSun
  • 58
  • 7
-3

Enterprise java beans are not synchronized . As session beans are maintained by ejb container so you have to implement synchronization logic in application level.

  • Are you sure about this? I think the JEE standard is very clear and only Entity Beans allow configuration of current access to their methods. Please correct me if I'm wrong. – icordoba May 07 '14 at 15:58