Question

I have this new mvc project where all beans are default scoped(no prototype or session).
with single application context.

i want to know
by making all beans to be default scoped are we trying to achieve the whole application to be run in single thread?

if so will that make each httprequest(from multiple or same sessions) to be queued until the previous one completes?How to avoid such scenario any advice or link would be helpful.

I am relatively new to spring and java development.

Answer 1

Because Spring beans are typically stateless, you can safely call them from multiple threads. That’s how your application works: there is only one instance of every controller, service, DAO, etc. But your servlet container (through Spring) calls these beans from multiple threads – and it’s completely thread safe.

In fact in plain servlets the situation is the same – there is only instance of each servlet and it can be accessed by infinite number of threads. As long as this servlet is stateless or properly synchronized.

Do not confuse Spring with stateless session beans in ejb that are pooled and each client gets its own instance from the pool.¹

^{1 – In fact that’s a bit dumb – since the beans are stateless by the definition, there is no point in pooling them and preventing concurrent access…}