This content has been marked as final.
Show 4 replies
-
1. Re: Issue with invoking same instance SLSB when accessing from remote client
jaikiran Apr 22, 2015 6:02 AM (in response to valsaraj007)Stateless EJBs are not meant to store state across business method invocations. You were just lucky that the same EJB instance (from the pool) ended up being used previously. But as you notice now, there's no such guarantee. In fact, pooling isn't even mandated by the spec and that's why WildFly 8 doesn't use pools for stateless EJBs.
-
2. Re: Issue with invoking same instance SLSB when accessing from remote client
valsaraj007 Apr 23, 2015 12:10 AM (in response to jaikiran)Thanks much Jaikiran!
I wonder whether WildFly 8.2 is creating SLSB instance on request if it is not using bean pool?
-
3. Re: Issue with invoking same instance SLSB when accessing from remote client
jaikiran Apr 23, 2015 2:01 AM (in response to valsaraj007)valsaraj viswanathan wrote:
I wonder whether WildFly 8.2 is creating SLSB instance on request if it is not using bean pool?
By default, yes, it's creating an instance of the SLSB per request and isn't using a pool.
-
4. Re: Issue with invoking same instance SLSB when accessing from remote client
valsaraj007 Apr 23, 2015 2:44 AM (in response to jaikiran)Will this cause any performance issue? Do we need to configure pool?
Thanks!