+ Props creation with nulls does not fail any longer
+ null values are now serialised properly and can be used in remote
deployments too
+ added tests for Reflect.findConstructor
> does not change wire protocol, so that's open for discussion (if we
> want it to be more like SerialisedMessage or not)
Resolves#13946
Per discussion with Roland and Kathleen, suggest we point users interested in the Akka in Action book to the Typesafe.com 'Akka in Action' E-Book page, so that they can obtain free sample chapters.
(cherry picked from commit b17142f368fb07b34c3bed2727eb62a77790866f)
Conflicts:
akka-docs/rst/additional/books.rst
* I couldn't find anything wrong
* Increasing the test timeout, it takes 1.5 s for the reconnects,
so the previous total of 3 s might not have been enough
(for that run)
* Replace sleep with awaitAssert
* Use separate probes for awaitAssert checks to avoid spill-over
to the testActor
* Some additional cleanup
* Deliver buffered messages when HostShard is received
Test failures showed that initial messages could be re-ordered otherwise
* deprecates awaitTermination, shutdown and isTerminated
* introduces a terminate-method that returns a Future[Unit]
* introduces a whenTerminated-method that returns a Future[Unit]
* simplifies the implementation by removing blocking constructs
* adds tests for terminate() and whenTerminated
* The reason it didn't work is that messages are delivered before the cell is swapped
as can be seen in RepointableActorRef.replaceWith (L195)
* Use ask until the RepointableActorRef is started, then use attachChild
Added spec test to cover fix for bug 15671
Replaced deprecated NamedProcessor with NamedPersistentActor. Cleaned up unused message handling. Typos and misspellings.
- Move all entry related logic out of the ShardRegion and into a
new dedicated child `Shard` actor.
- Shard actor persists entry started and passivated messages.
- Non passivated entries get restarted on termination.
- Shard Coordinator restarts shards on other regions upon region failure or handoff
- Ensures shard rebalance restarts shards.
- Shard buffers messages after an EntryStarted is received until state persisted
- Shard buffers messages (still) after a Passivate is received until state persisted
- Shard will retry persisting state until success
- Shard will restart entries automatically (after a backoff) if not passivated and remembering entries
- Added Entry path change to the migration docs
