Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 11:24
    Kenji-Tanaka commented #3887
  • 10:45
    nagytech edited #4086
  • 10:45
    nagytech synchronize #4086
  • 10:43
    nagytech opened #4086
  • 09:00
    Horusiath commented #4077
  • 06:31
    Aaronontheweb commented #4085
  • 06:28
    Aaronontheweb commented #4085
  • 06:24
    Aaronontheweb commented #4085
  • Dec 07 11:49
    IgorFedchenko commented #4085
  • Dec 07 10:31
    IgorFedchenko commented #4085
  • Dec 07 08:36
    IgorFedchenko commented #4085
  • Dec 06 20:57
    IgorFedchenko commented #4085
  • Dec 06 20:32
    IgorFedchenko commented #4085
  • Dec 06 20:01
    IgorFedchenko commented #4085
  • Dec 06 19:55
    IgorFedchenko commented #4085
  • Dec 06 16:22
    Aaronontheweb labeled #3997
  • Dec 06 16:22
    Aaronontheweb closed #3997
  • Dec 06 16:20
    IgorFedchenko commented #3997
  • Dec 06 16:08
    IgorFedchenko commented #4085
  • Dec 06 15:50
    Aaronontheweb assigned #4085
Aaron Stannard
@Aaronontheweb
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
Yin Zhang
@melcloud
By the way, we really need intellisence for akka config!
Aaron Stannard
@Aaronontheweb
yeah, that's a popularly requested one
Yin Zhang
@melcloud
@Aaronontheweb Yeah, that config works well. thanks
Aaron Stannard
@Aaronontheweb
:thumbsup: glad to hear it
Yin Zhang
@melcloud
hi guys, can I use Become in AtLeastOnceDelivery? Is it a bad idea?