raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

Don't stop dynamic router when all routees terminated, see #2734

Browse source
This commit is contained in:
Patrik Nordwall 2013-04-08 13:19:44 +02:00
parent 3ee42dbe11
commit accdd63e7d
5 changed files with 39 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

8
akka-docs/rst/java/routing.rst
View file

@ -149,7 +149,8 @@ direct children of their grand-parent instead.
If the child of a router terminates, the router will not automatically spawn
a new child. In the event that all children of a router have terminated the
router will terminate itself.
router will terminate itself, unless it is a dynamic router, e.g. using
a resizer.
Router usage
^^^^^^^^^^^^
@ -378,7 +379,7 @@ documentation for details.
.. includecode:: code/docs/jrouting/RouterViaProgramDocTestBase.java#poisonPill
For a router, which normally passes on messages to routees, it is important to realised that
For a router, which normally passes on messages to routees, it is important to realise that
``PoisonPill`` messages are processed by the router only. ``PoisonPill`` messages sent to a router
will *not* be sent on to routees.
@ -399,7 +400,8 @@ routees aren't children of the router, i.e. even routees programmatically provid
With the code shown above, each routee will receive a ``PoisonPill`` message. Each routee will
continue to process its messages as normal, eventually processing the ``PoisonPill``. This will
cause the routee to stop. After all routees have stopped the router will itself be :ref:`stopped
automatically <note-router-terminated-children-java>`.
automatically <note-router-terminated-children-java>` unless it is a dynamic router, e.g. using
a resizer.
.. note::

6
akka-docs/rst/scala/routing.rst
View file

@ -151,7 +151,8 @@ direct children of their grand-parent instead.
If the child of a router terminates, the router will not automatically spawn
a new child. In the event that all children of a router have terminated the
router will terminate itself.
router will terminate itself unless it is a dynamic router, e.g. using
a resizer.
Router usage
^^^^^^^^^^^^
@ -396,7 +397,8 @@ routees aren't children of the router, i.e. even routees programmatically provid
With the code shown above, each routee will receive a ``PoisonPill`` message. Each routee will
continue to process its messages as normal, eventually processing the ``PoisonPill``. This will
cause the routee to stop. After all routees have stopped the router will itself be :ref:`stopped
automatically <note-router-terminated-children-scala>`.
automatically <note-router-terminated-children-scala>` unless it is a dynamic router, e.g. using
a resizer.
.. note::