akkadotnet/akka.net

Port of Akka actors for .NET

Ashit Shakrani

@ashshak

yup, I saw the source file. And even the handler for OnTransition() is firing. But it never enters the stateFunc of the 2nd state.

Aaron Stannard

@Aaronontheweb

akka.loglevel = DEBUG

this will print out the _log.Debug("transition {0} -> {1}", oldState, upcomingState); messages to the console

so you'll know for certain if the transition occurs

I think you are transitioning to the second state

but you need to send another event

right now nothing is handled in that state

events don't cascade

they're handled and cause a transition

Ashit Shakrani

@ashshak

ok, I see. I have just fired another message and it now hits handler. I thought I could just move from one to another. Thanks for your help.

Aaron Stannard

@Aaronontheweb

no worries @ashshak - it was a good gut check for me too

the thing I was worried about was using nullable types to define states

since we do so many STATE1 == STATE2 comparisons

but you handled that by using singletons

we really need to document FSMs anyway - @skotzko just put together a big sample the other day showing how to unit test them

Ashit Shakrani

@ashshak

Where can I find that. http://getakka.net/docs/FSM seems incomplete to me as it there are no GoTo s. Your markedup blog post for FSM was helpful.

Aaron Stannard

@Aaronontheweb

we'll be publishing it soon - the getakka.net docs for the FSM are scarce

@rogeralsing @Horusiath btw, this is supposed to be getting merged today Azure/DotNetty#40

has all of the stuff needed to replace Helios AFAIK

Roger Johansson

@rogeralsing

nice!

Aaron Stannard

@Aaronontheweb

only thing missing is the multi-threaded event loop

which helps throughput across multiple connections

makes no difference over a 1:1 connection

Arjen Smits

@Danthar

Commit message Motivation: Let me guess. commit messages are mandatory ? ^^

Aaron Stannard

@Aaronontheweb

lol what's that from?

Arjen Smits

@Danthar

o wait. its followed by a newline :D

Azure/DotNetty@0722ade

Aaron Stannard

@Aaronontheweb

haha

Max has a very precise communication style

Arjen Smits

@Danthar

System.Diagnostics.Contract stuff is great. Been using it more and more in my own code as well

l3igmike

@l3igmike

is it possible to kill an actor, recreate it somewhere else and include its former mailbox messages?

Aaron Stannard

@Aaronontheweb

@l3igmike Akka.Persistence can do this

backs up its state, but not its messages, to a durable store

Yin Zhang

@melcloud

Morning guys. Is there a way to filter out death watch and heartbeat log message under debug? I want to see all sent/receive messages between two remote nodes, but those heartbeat message are rally annoying! :smile:

Aaron Stannard

@Aaronontheweb

if you're debugging Akka.Remote

or Cluster

one thing I recommend doing is just setting the heartbeat interval way the hell long

so you can stay at a breakpoint for a few minutes without a bunch of failure detectors going off

I have a snippet for that...

akka {          
           log-config-on-start = on
                        actor {
                            provider = "Akka.Cluster.ClusterActorRefProvider, Akka.Cluster"
                        }

                        remote {
                            log-remote-lifecycle-events = DEBUG

                            helios.tcp {
                                transport-class = "Akka.Remote.Transport.Helios.HeliosTcpTransport, Akka.Remote"
                                applied-adapters = []
                                transport-protocol = tcp
                                #will be populated with a dynamic host-name at runtime if left uncommented
                                #public-hostname = "POPULATE STATIC IP HERE"
                                hostname = "127.0.0.1"
                                port = 800
                            }
             transport-failure-detector {
               implementation-class = "Akka.Remote.DeadlineFailureDetector,Akka.Remote"
               heartbeat-interval = 400 s
               acceptable-heartbeat-pause = 300000 s
               monitored-by-nr-of-members = 5
               expected-response-after = 5000 s
             }
                        }            

                        loggers = ["Akka.Logger.Serilog.SerilogLogger, Akka.Logger.Serilog"]

                        cluster {
                            #will inject this node as a self-seed node at run-time
                            seed-nodes = []
                            roles = [lighthouse]
             failure-detector {
               implementation-class = "Akka.Remote.DeadlineFailureDetector,Akka.Remote"
               heartbeat-interval = 400 s
               acceptable-heartbeat-pause = 300000 s
               monitored-by-nr-of-members = 5
               expected-response-after = 5000 s
             }
                        }
                    }

pardon the weird tabbing

Yin Zhang

@melcloud

@Aaronontheweb nice... you kill two birds with one stone... :+1:

Aaron Stannard

@Aaronontheweb

but that lets me debug a cluster for effectively forever

that setting would be terrible to run in production

obviously

Yin Zhang

@melcloud

yeah, for sure. I just need it for development testing

Aaron Stannard

@Aaronontheweb

we have an issue where we're considering automatically doing that if the debugger is attached

but that probably wouldn't fix it if the service you're debugged is connected to a bunch of other ones that aren't

better just to modify the config

let me know if that works

Where communities thrive

People

Repo info

Activity