-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
During passivation we perform a long-lived synchronization on the internal cacheMap, which restricts both requests to get new sessions as well as invocations upon other sessions until passivation is completed.
The synchronization cannot simply be removed, better possibility may be to apply a copyOnWrite or copyOnPassivate-type implementation
- is related to
-
EJBTHREE-1551 SimpleStatefulCache does not synchronize StatefulBeanContext instances during get() Activation
- Open
- relates to
-
EJBTHREE-2273 Deadlock in StatefulSessionFilePersistenceManager when too many ejb clients for ejb3 cache maxSize
- Open