Wildfly >9 changed Stateless Session Beans Behavior

[joergl]

Dear all,

we recognized that Stateless Session Beans show a different behavior in Wildfly 10 and 11 compared to versions before that (e.g. Wildfly 9).

Here is a short demonstration using a simple counter example: Wildfly 10+ Stateless Beans Changed Behaviour · GitHub

Basically, for me it looks like the stateless session beans are not really stateless any more, because they to keep variable states over several calls within a client session.

However, I am not a real expert on this, so I would like to know what the reason for this behavior change is (intentional, bug, ...)?

Thank you very much for your help

Best Joerg

[lafr]

Wildfly 8 and possibly also 9 did not use SLSB pooling per default. So every invocation lead to a new instance of the SLSB.

Beginnig with Wildfly 10 SLSB pooling is enabled by default. So your bean instances get poold and reused.

Some links:

Should we use pool for SLSB to improve performance?

EJB3 subsystem configuration guide - WildFly 10 - Project Documentation Editor

WildFly - Performance tuning - Ralph's Open Source Blog

WildFly performance tuning

[joergl]

Yes, that looks like it is the explanation! Thank you so much Frank!