Stuart, On Tue, Jan 7, 2014 at 10:03 AM, Stuart Easterling < [email protected]> wrote:
> Hi Romain, I think I may need to do that (my current workaround is to use a > singleton bean and many threads, but I'd like to get my pool working too : > ). > you seem to want to know the difference between the behavior/execution of your code and Romain's code. you mentioned 'singleton bean and many threads', above. did you share your singleton bean code already in this thread? sorry if i missed that. i'm asking/responding, as you asked if anyone seen this behavior before (in their app). the only time, I've seen similar behavior is with my singleton beans... the latest (or only) instantiated singleton bean...is used/referenced.
