I’m encountering a very strange behavior with no event being persisted (or even read) and no particular warning of any kind from Lagom or Akka. More specifically, the commands are handled correctly (using the initial entity state) and returns a correct reply, but the messages table in Cassandra remains fully empty (and thus no read-side processing occurs) Thus, if we send twice the same command (after the entity get passivated), they are processed exactly in the same way, without any side effect. Not also that existing events in Cassandra are not considered neither: entities are always started in the initial state without considering any existing history. And note also that this happen both in dev and prod.
I struggled quite a lot to understand the cause, and this still remains quite obscur. But I realized that by switching back to 1.5.4, the problem disappear and everything works as expected. I have checked twice and just by changing this Lagom minor version number, I can make the problem appear or disappear.
I suspect that the issue is more complex and I still need to reproduce the behavior in a simple setting to understand it more and possibly open an issue.
But in the meantime, I was hoping that someone could have some idea on the possible origin of such a strange behavior (no effective read-write from cassandra but no complain from Lagom-Akka)
Thanks for any help!