Hi According to a response on a ticket I opened with New Relic, they are not invoking or exaggerating the occurrence of ActorKilledException. With the latest java agents, NR is by default not reporting ActorKilledException anymore. A workaround, not a solution.
Since this seems to happen in so many applications with up to a 100% error rate on NR, the issue probably merits further analysis by Akka/Play devs? On Thursday, October 31, 2013 8:07:11 AM UTC+1, Donovan Muller wrote: > > Hi Thiago, > > Our ticket is still open with NR. > Hopefully they will resolve soon... > > Cheers > > > On 30 October 2013 22:56, Thiago Lima <[email protected]<javascript:> > > wrote: > >> Any update about this issue? Same problem here... >> >> -- >> You received this message because you are subscribed to the Google Groups >> "play-framework" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
