Please consider upgrading to WF10 - where the new distributed web session implementation (first introduced in WF8) is much more stable.
Otherwise, you should make sure to use PESSIMISTIC locking and REPEATABLE_READ isolation, to ensure that a subsequent request for a given session waits for the previous request to commit its session attributes - otherwise, dirty reads can occur.
Hi Paul, thank you for replay. I will try this configuration next week in the convenable environnement (becuase those errors is no present in the developpement's environnement).
However, i am not sure that i can migrate to WF10 now, because i must be sure that they aren't new bugs in the newest version and i must wait until it becomes most stable.
I'm not sure why you assume that 8.2 is more stable than 10. 8.2 hasn't been touched in 7 months - that's not because it has no bugs, but because we aren't maintaining it any longer. Any bugs we're fixing now are only going into master (the branch for the 10.x series). Conversely, there are no bugs fixed in 8.2 that aren't also fixed in 10.
Upgrade to WF 10 will take much time to test that all fonctionnalities are still work (--> that will take weeks to test that).
I say that because i was upgrade to WF9 and i found more problems (very slow, problems with jgroups, ...) so we decide to still use WF8.
Hi Paul, after dowing the changement (use PESSIMISTIC locking and REPEATABLE_READ isolation), the frequency of nullpointerexception has reduced (i still have sometimes nullpointerexceptions).
But i have other kind of errors :
ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [30 seconds] on key [org.wildfly.clustering.server.group.AddressableNode@af787ff3]
have you an issue to resolve this errors please?
Sure it needs some testing, but WF10 is definitely the most stable among WF8/9/10 so I would think upgrading will be worth while. Let us know if you have some concrete problem with the newer jgroups version in WF10.
Hm I vaguely remember this has been fixed around WF9 Beta. I am not sure there would be an easy workaround.