Hi Spencer, This sounds like it could work with a supervision strategy that does not restart the actor but rather lets it resume on a failure.
If that is not possible you would have to move the information that the FSM actor has been previously started somewhere outside of it. Could be to another actor, in which case you would have to query that actor about it when the FSM actor starts, with an not-quite-initialized state and then going to different actual initial states when the reply arrives. If you would want it to behave the same across JVM crashes as well you would have to persist the information, this could for example be done using Akka persistence (take a look at PersistentFSM) but it could also be done in a multitude other ways depending on your needs (file on disk, save to database etc). -- Johan -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
