tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <>
Subject Re: Stateless EJB and attributes
Date Wed, 16 Jul 2014 10:12:25 GMT
I don't recall exactly our default but it is configurable/pluggable

Romain Manni-Bucau
Twitter: @rmannibucau

2014-07-16 12:09 GMT+02:00 agumbrecht <>:
> Hi Alex,
> My understanding is that a request gets a checked out bean instance for the
> duration of the method call. No other call will get this bean instance until
> it is returned to the pool, after the method call completes.
> If you have a bean class field like private final AtomicInteger then you can
> increment it in every method call on that bean. You will see that each bean
> will keep it's own call count. Putting it back into the pool will not reset
> the variable.
> The chance that another call will get the same bean is never guaranteed.
> It's maybe interesting to see in a loop how often you actually get the same
> instance.
> So a stateless bean can actually have state, but it 'may' get discarded - At
> least when the instance is discarded. You may also get a completely new
> instance on the next call if the pool is starved etc.
> Anyway, putting anything into a class variable in a stateless is probably
> not a good idea as the next caller may have access to it. If you do, clean
> it up before returning from the call.
> Romain, without looking, do we pop from the head and put back to the tail?
> Andy.
> -----
>     --
>     Andy Gumbrecht
>     TomEE treibt Tomitribe ! |
> --
> View this message in context:
> Sent from the TomEE Users mailing list archive at

View raw message