Hi!
> this is not correct and in fact for entity it is done the proper way, i.e.
> the state sync is in another interceptor.
>
> Acquiring a context and setting it's state are not linked
Agree.
> |It seems to me that the contention is low, since this lock is
> |released ASAP.
>
> Still...
>
> ok, we just finished a solution based on the sync(ctx) where we have only
> one sync and the cache.get is synced on teh cache.
>
> I *strongly* recommend moving the activation out of that sync (out of the
> cache.get) and into a interceptor for stateful beans but that is down the
> road, just keep it in mind for now.
Agree completely. When we do clustered stateful this will be even more
important since activation will happen on all calls. Ah well, since we
already have this going with EntityBeans it should be pretty
straightforward.
> The new solution works, and works well (works for 2 threads, 10 threads,
50
> threads and almost works for 100 threads *all on the same object*). When
I
> say *almost* I mean that now we are back on the "timeout" problems that
send
> the server spinning loco do to a tx that is never cleanly removed
> (somewhere) we will track that one down.
I see. Slowly but surely then.
regards,
Rickard
ps. Just a thought: I really pity the poor souls at commercial companies who
have to do this stuff without such an extensive peer review process. I'm
amazed that even one commercial J2EE server really works...
