It runs on the normal mechanism for completable futures in Java locally by calling submitToKey on a hazelcast map or sumbitToOwer will be put in an executor configure in hazelcast. It's these executors that are often getting deadlocked. So we have a strategy of using an executor per call type and that is becoming a bit heavyweight.
-- >>>>>>>>>> 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.
