Stateless Session Beans vs. Singleton Session Beans

Question

The Java EE 6 Tutorial says:

To improve performance, you might choose a stateless session bean if it has any of these traits:

• The bean’s state has no data for a specific client.
• In a single method invocation, the bean performs a generic task for all clients. For example, you might use a stateless session bean to send an email that confirms an online order.
• The bean implements a web service.

Singleton session beans are appropriate in the following circumstances:

• State needs to be shared across the application.
• A single enterprise bean needs to be accessed by multiple threads concurrently.
• The application needs an enterprise bean to perform tasks upon application startup and shutdown.
• The bean implements a web service.

But what to use if:

• no state has to be shared across the application
• a single enterprise bean could be accessed by multiple threads concurrently
• no tasks on startup or shotdown need to be performed

Say for example I have a login service with the following interface:

public interface LoginService {
  boolean authenticate(String user, String password);
}

Should it be annotated with @Singleton or @Stateless? What are the benefits of the one and the other? What if LoginService needs to get injected an EntityManager (which would be used concurrently)?

Addition: I'm thinking about the Java EE counterpart of Spring service beans, which are stateless singletons. If I understand that correctly the Java EE counterpart are @Stateless session beans and @Singleton Beans are used to configure the application at startup or cleanup at shutdown or to hold application wide objects. Is this correct?

Scrubber

Answer 1

I would go for Stateless - the server can generate many instances of the bean and process incoming requests in parallel.

Singleton sounds like a potential bottleneck - the default @Lock value is @Lock(WRITE) but may be changed to @Lock(READ) for the bean or individual methods.

Nourish

Could you explain, why you consider singleton like a bottleneck if we can use @Lock(LockType.READ) for all class? For example @Lock(LockType.READ)public class MySingleton {..}. – Arian

I wonder if this is actually a drawback to Stateless, mjn. With Stateless, do we need a pool size of N to serve N concurrent requests? Presumably a Singleton with a @Lock(READ) can serve N concurrent requests without adjusting pool size. – Accalia

Answer 2

according to the ejb 3.1 spec, page 110, chapter 4.8.5 "Singleton Concurrency":

It is legal to store Java EE objects that do not support concurrent access (e.g. Entity Managers, Stateful Session Bean references) within Singleton bean instance state. However, it is the responsibility of the Bean Developer to ensure such objects are not accessed by more than one thread at a time.

and furthermore, according to the hibernate entitymanager documentation

An EntityManager is an inexpensive, non-threadsafe object that should be used once, for a single business process, a single unit of work, and then discarded.

For me, this means, that you should never inject an EntityManager into a singleton EJB. I would use a singleton EJB as a replacement for a stateless EJB only if EVERYTHING I need to implement in this class supports concurrency without the need to do additional locking / synchronization. As you or other programmers might lose this issue sooner or later from your focus, I personally prefer to not use singleton EJBs except for startup-related issues or features that can be implemented as self-contained units - independently of other beans. In that sense, it doesn't seem to be advisable to inject for example Stateless EJBs into Singletons. Doing so raises the question about the point in time, when the container actually performs the injection of the SLSB into the Singleton? According to the EJB 3.1 Spec, chapter 4.8, the dependency injection gets done before the singleton bean instance can be accessed by clients. So the singleton would obviously stick to the same instance of the SLSB, which seems to become a singleton implicitly, but there doesn't seem to be any guarantee for that. At least I couldn't find anything in the specs, so the behavior might be unpredictable or in the best case container-specific, which is not what most people will want.

Thus, I would only inject Singletons into Singletons or Singletons into SLSBs but not vice versa. For the case of an injection of a Singleton into a Singleton, the Spec offers you the opportunity to define the dependencies between the singletons so that the container can initialize them in the correct order (see the ejb 3.1 spec, chapter 4.8.1 concerning the @DependsOn annotation).

Zito

Answer 3

@Stateless will allow you to have multiple copies ready for processing within a JVM (as much as memory and pool size allows) where-as @Singleton there's only one copy in a JVM, even if the single one can support multiple concurrent threads running against it.

In terms of performance @Singleton would be better, provided that the resources it uses allow long running access. However, in a distributed environment sometimes bad things occur, e.g. database or network links may fail.

With a @Stateless bean, the access is more short lived. In addition, should there be a failure it will just respawn and try to establish a new connection to the resource. If something happens like that on a singleton, then it's up the the singleton to handle it without requiring an application restart because the @PostConstruct is only called once per JVM.

I would prefer a bit of fault tolerance vs performance for most situations especially on systems I have no control over.

Pupil

Answer 4

I think Singleton in concurrency usage will not perform worse than SLSB Pool, it might be even better. The only problem is if you want to share something between threads, you need lock it, and that could be a big problem of performance. So in that case, a SLSB Pool perform much better, because it's not 100% singleton, there are more instances, one got locked, the other one comes up. Anyway if the lock is on some resource sharing by all SLSBs, the pool won't help neither.

In short, I think singleton is better than SLSB Pool, you should use it if you can. It's also the default scope for Spring Beans.

I'm not a JavaEE expert, that's just my feeling, please correct me if I'm wrong.

Igal

Answer 5

I think you should use Singleton session bean. Because a login service should be a global service and it does not need to store any state for a concrete user or invocation.

Hesperidium

Answer 6

If you're sure you're not sharing state between threads, then a Singleton will be fine in which case you should also annotate the class with @ConcurrencyManagement( ConcurrencyManagementType.BEAN ) which will allow multiple threads running at the same time.

Pouncey

Answer 7

you should go for Singleton if you have any resource that is going to remain constant across the application. Like loading some data from some file or reference data which would not change across the application lifecycle. otherwise, go for SLSB. The drawback of SLSB is that multiple objects would be created hence more memory would be occupied.

Ariana

Answer 8

Imho I would answer like that:

"no state has to be shared across the application" leads me to stateless bean because of the sentence "To improve performance, you might choose a stateless session bean...".

Considering "a single enterprise bean could be accessed by multiple threads concurrently" you would have to use singleton. If I got it right it is not even possible to access a stateless bean's concurrently when properly used.

"no tasks on startup or shotdown need to be performed" would not matter to me. If tasks have to be done to properly setup a bean then they have to be invoked by a @PostActivate method.

I would logically conclude your question what to use to @Singleton since you asked for concurrent access. Of course you will have to manually control snychronisation of accesses on any further resources (which are not EJBs).

Cloudberry