The one thing I keep struggling with is the opaqueness of failures in Akka, i.e. that all the conditions at failure time are not available to either the actor or the supervisor.
What I just came across was a failure during creation. The supervisor saw it and logged it and I found where it died and what the reason was, in this case unexpected/illegal input data during creation. The problem is that this is in an actor that gets spawned for many workloads, and from the stacktrace I could not determine which spawn caused it. I wanted to add more logging around this, but it doesn't seem like the supervisor has any clue who died. Am I overlooking something? I mean, the creation is asynchronous, so I can't even use any creation logging as an indicator which one of the created actors is the one that died. Best I can think is to create and immediately watch it and use the Terminated message (not sure if that would even catch creation failures. Or how should I structure things differently so that I can deal with initialization failures? thanks, arne -- >>>>>>>>>> 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.
