csadilek:"The problem is that our session object turned out to be not serializable in 2.3.0 or earlier. So, that was a super critical fix in 2.3.1 by itself (e.g to make Errai work in a cluster with session replication). Unfortunately, the fix introduced a problem when cleaning up sessions which also needs to be addressed (2.3.2)."
There is known fix in upstream https://github.com/errai/errai/commit/4c9bbbbe84b2a49be6cdc4746b332c47a2e61efe by Jonathan. The question is, include into CR1 only this fix or to wait for 2.3.2.Final Errai release, which should be available this week. Given the fact we are closed to WFK-2.3 CR1, I would not go the way of including 2.3.2.Final but only backporting this fix, as other commits alogn the way 2.3.1 --> 2.3.2 might bring into a new regresions, which is not desirable.
updated into 2.3.2.Final with http://git.app.eng.bos.redhat.com/?p=errai/errai.git;a=shortlog;h=refs/heads/wfk23-prod-2.3.2.Final
Verified in WFK 2.3.0.CR1
Christian Sadilek <csadilek> updated the status of jira ERRAI-574 to Closed