Hi Patrik! The new handling make sense to me. We handled the problem a slightly different so far, we used a scheduleOnce and retried to store the message in case a PersistendFailure occurred. The reason we didn't stop the actor is that our PersistendActor is as well a ClusterSingleton and we would like to avoid stopping it without a good reason.
I need now to check out how the new handling effects our Singleton in Error cases. Wolfgang -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
