Currently our use of Akka is limited and I would like to increase it. However, I am getting some good questions from colleagues that I don't have the answer to. One of the questions is about avoidance of Live Lock. Essentially we are using Hazelcast distributed execution via executors and callable instances that return futures and there are some problems. Given processes A, B and C. Process A calls process B which calls Process C which calls Process A again to get some sub facet of communication. The problem is if enough events are fired at the executor of process A then the system live locks. A cannot return because it needs the result of B which needs the result of C which needs results of invocation of other instances of Process A. As long as the thread pool for A is not full, everything works but as soon as enough threads get backed up, Live lock occurs. We have gotten into having per-method call executors and that is a LOT of thread pools laying around mostly doing nothing.
Now would Akka be susceptible to the same notion of live lock? If not then how does it avoid it in the above circumstance. When my colleagues ask me "What is the benefit of Akka over our executor framework" I need to be able to answer them to make progress. Thanks in advance. -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
