Some common misconceptions related to Actors library:
- Actors handle incoming messages in a parallel, in multiple threads / against a thread pool (in fact, handling messages in multiple threads is contrary to the actors concept and may lead to racing conditions - all messages are sequentially handled in one thread (thread-based actors use one thread both for mailbox processing and execution; event-based actors may share one VM thread for execution, using multi-threaded executor to schedule mailbox processing))
- Uncaught exceptions don't change actor's behavior/state (in fact, all uncaught exceptions terminate the actor)
