TCK – verify entity passivation

[marcellanz]

An issue reported in v0.1.0 of the Go Support brought up a testcase the TCK could verify for state models.

The proxy sets the timeout for entity passivation to 30s for now. The property cloudstate.proxy.passivation-timeout can be set to a different value for the TCK running the proxy.

Tasks

• verify entity passivation for eventsourcing with the TCK
• verify entity passivation for CRDTs. I will include this for CRDTs with the new CRDT TCK this issue to be solved.

Go issue#27 demonstrates how it can be verified.

[marcellanz]

On passivation this message is logged by the proxy:

2020-06-14 23:42:13.486 INFO akka.actor.LocalActorRef - Message [akka.actor.Status$Failure] to Actor[akka://cloudstate-proxy/system/sharding/ShoppingCart/50/mrcl#-1089585546] was not delivered. [1] dead letters encountered. If this is not an expected behavior then Actor[akka://cloudstate-proxy/system/sharding/ShoppingCart/50/mrcl#-1089585546] may have terminated unexpectedly. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.

What does it mean by the proxies perspective?

[pvlugter]

Yes, I've also noticed the deadletter on passivation and have been meaning to look at it.

[viktorklang]

Good, thanks @pvlugter!

Thanks for opening this issue, @marcellanz

[sleipnir]

It would be nice to relate it to this other issue that deals with the same theme #298

[pvlugter]

I've moved the dead letter log to issue #389

[pvlugter]

Entity passivation in the language supports is now verified through the new TCK tests which call the subprotocols directly. We can also test the passivation timeouts from the language supports when based on #486. I'll close this issue as resolved.