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

document blocking nature of system.actorOf, see #2007

Browse source
This commit is contained in:
Roland 2012-04-23 12:25:33 +02:00
parent 4204b31759
commit 0c4b2a11ae
3 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
akka-docs/general/actor-systems.rst
View file

@ -101,6 +101,12 @@ Actor Best Practices
breaks all the properties which make programming in actors such a nice breaks all the properties which make programming in actors such a nice
experience. experience.
#. Top-level actors are the innermost part of your Error Kernel, so create them
sparingly and prefer truly hierarchical systems. This has benefits wrt.
fault-handling (both considering the granularity of configuration and the
performance) and it also reduces the number of blocking calls made, since
the creation of top-level actors involves synchronous messaging.
What you should not concern yourself with What you should not concern yourself with
----------------------------------------- -----------------------------------------

7
akka-docs/java/untyped-actors.rst
View file

@ -82,6 +82,13 @@ that is used in log messages and for identifying actors. The name must not be em
or start with ``$``. If the given name is already in use by another child to the or start with ``$``. If the given name is already in use by another child to the
same parent actor an `InvalidActorNameException` is thrown. same parent actor an `InvalidActorNameException` is thrown.
.. warning::
Creating top-level actors with ``system.actorOf`` is a blocking operation,
hence it may dead-lock due to starvation if the default dispatcher is
overloaded. To avoid problems, do not call this method from within actors or
futures which run on the default dispatcher.
Actors are automatically started asynchronously when created. Actors are automatically started asynchronously when created.
When you create the ``UntypedActor`` then it will automatically call the ``preStart`` When you create the ``UntypedActor`` then it will automatically call the ``preStart``
callback method on the ``UntypedActor`` class. This is an excellent place to callback method on the ``UntypedActor`` class. This is an excellent place to

7
akka-docs/scala/actors.rst
View file

@ -76,6 +76,13 @@ that is used in log messages and for identifying actors. The name must not be em
or start with ``$``. If the given name is already in use by another child to the or start with ``$``. If the given name is already in use by another child to the
same parent actor an `InvalidActorNameException` is thrown. same parent actor an `InvalidActorNameException` is thrown.
.. warning::
Creating top-level actors with ``system.actorOf`` is a blocking operation,
hence it may dead-lock due to starvation if the default dispatcher is
overloaded. To avoid problems, do not call this method from within actors or
futures which run on the default dispatcher.
Actors are automatically started asynchronously when created. Actors are automatically started asynchronously when created.
When you create the ``Actor`` then it will automatically call the ``preStart`` When you create the ``Actor`` then it will automatically call the ``preStart``
callback method on the ``Actor`` trait. This is an excellent place to callback method on the ``Actor`` trait. This is an excellent place to