I am running through a tutorial on PluralSight (that is a little outdated) and am using the Terminate() method followed by the WhenTerminated task. What I get is a "DeathWatchNofitification message was not delivered" error. Any thoughts?
@fouimette usually it's nothing to worry about. When actor system terminates, it kills all actors in async fashion. Actors build in hierarchies parent-child often send messages to each other when terminating. In case of system termination that means that one terminating actor could send a message to another, which is being terminated too.
Hi guys, what's the status of the Akka Cluster?
@corneliutusnea pretty solid already, I think @Aaronontheweb is going to move it out of beta in a week.
Should I wait for final integration / testing with my product ?
if it's only a week, I would wait anyway
Thanks @to11mtm ... is there a site for Akka.Visualizer with a bit more info?
@qwoz I think you are talking about my visualizer. I really had no time to publish it :/ my fault
@Horusiath Thanks for the response. I would expect that a simple demo to create an actor in an actor system and then terminating the system would not produce such an unexpected result.
hi How can I get recover the message in supervisor?
Bart de Boer
@hidavidpeng either in the 'character' actor you do smth with it in PreRestart (or PostStop), or have the supervisor 'remember' it when sending it to the inner actor, and keep it until 'OK' or 'NOK (deadwatchnotification)'
Can I check if a (cluster) router currently has any routees?
In more words: I would like to know if there is currently any node connected which has actors capable of the job I want to do.
await router.Ask<Routees>(new GetRoutees())
@corneliutusnea THANK YOU for putting it on git finally. =D
are there any screenshots of the visualizer?
man, amazing what one small change can do in the right place in terms of performance
removed one allocation inside the dispatcher system and saw a bump immediately
going to add a unit test that does the equivalent of what our NBench specs do for measuring actor message throughput
to make it easier to hook up a profiler like dotTrace, mostly
since NBench doesn't offer that level of granularity
actually, hmmm... I'm going to need to rethink that
@Aaronontheweb is there anyway to have both a Priority Mailbox and a Stash?
do I just have to implement IDequeBasedMailbox on my custom priority mailbox?
or is the whole concept a conflict of interests
you should be to able to do both
to be honest I'm not sure due to the changes coming in 1.1