Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 13:10
    zbynek001 opened #4000
  • 11:20
    IgorFedchenko commented #3973
  • 11:20
    IgorFedchenko commented #3973
  • 11:18
    IgorFedchenko commented #3973
  • 10:47
    IgorFedchenko synchronize #3973
  • 10:13
    valdisz commented #3921
  • Oct 21 15:57
    Aaronontheweb closed #3877
  • Oct 21 15:57
    Aaronontheweb commented #3877
  • Oct 21 15:56

    Aaronontheweb on dev

    Persistence TestKit documentati… (compare)

  • Oct 21 15:56
    Aaronontheweb closed #3889
  • Oct 21 07:27
    dependabot-preview[bot] labeled #3999
  • Oct 21 07:27

    dependabot-preview[bot] on nuget

    Bump FluentAssertions from 4.14… (compare)

  • Oct 21 07:27
    dependabot-preview[bot] opened #3999
  • Oct 20 17:25
    valdisz synchronize #3889
  • Oct 20 17:17
    valdisz synchronize #3889
  • Oct 20 15:44
    valdisz synchronize #3889
  • Oct 20 09:22
    ismaelhamed commented #3863
  • Oct 19 23:39
    valdisz synchronize #3889
  • Oct 19 23:08
    edvinasz commented #2947
  • Oct 19 13:36
    Aaronontheweb commented #3973
Ebere Abanonu
@eaba
@mmisztal1980 I get you perfectly
Like I said, though it might be painful, unplug your logging stack
What I have pasted above logs everything including exceptions
Maciek Misztal
@mmisztal1980
I have a similar setup right now :)
Maciek Misztal
@mmisztal1980
interestingly, if I send PoisonPill.Instance to the actor before doing the .Tell a deadletter message is logged :D
Bartosz Sypytkowski
@Horusiath
@eaba it looks like, you're trying to use some object that JSON.NET is not able to serialize - my guess would be that you're trying to use Akka.Cluster.Sharding (which has warning to not use json.net as a default ;) )
you can try to change it to something else, like Hyperion, or to use akka.cluster.sharding in ddata mode
Ebere Abanonu
@eaba
@Horusiath am not using akka.cluster.sharding no akka.cluster atm... @ismaelhamed suggestion:
serialization-settings.json {
                        preserve-object-references = false
                        encode-type-names = false
                    }
Is taking me further......what do you say about it?
Arjen Smits
@Danthar
Im sure it helps. But like @Horusiath is saying. If your using Cluster Sharding. Using json.net is highly discouraged
When using cluster sharding. or actually, any akka modules with persistence. You will want to have explicit control over your message schema's
considering that akka.persistence is using event-sourcing
Ebere Abanonu
@eaba
When using cluster sharding. or actually, any akka modules with persistence. You will want to have explicit control over your message schema's
Am not using cluster sharding
Arjen Smits
@Danthar
ok
Ebere Abanonu
@eaba
So am left with persistence
does preserve-object-references = false
solve my problem
should i be worried about something going that way?
Arjen Smits
@Danthar
perhaps. i dont know what your message schema looks like. But you can test that pretty quickly yourself
going what way ?
Ebere Abanonu
@eaba
preserve-object-references = false way
Tested and working
Arjen Smits
@Danthar
ah. Im not aware of any long term issues with disabling object-references
Ebere Abanonu
@eaba
My message is just an Immutable Dictionary wrapped in a custom class
Ok
Arjen Smits
@Danthar
ah. yeah json.net can have issues with that
immutable collection types and json.net have a history of bugs
Ebere Abanonu
@eaba
Ok I will note that
Arjen Smits
@Danthar
so be sure to test all your message types if you continue to use immutable collection types with json.net
Ebere Abanonu
@eaba
Ok...
Thanks @Danthar
QwerSense
@QwerSense
Hey, is there a websocket chat example with akka.net and dotnet core?
AndreSteenbergen
@AndreSteenbergen
@Horusiath I configured all nodes like this, my cluster isn't really dynamically sized, so I am going for keep-oldest. Is that a good idea?
    cluster {
            #will inject this node as a self-seed node at run-time
            seed-nodes = ["akka.tcp://claxe@10.0.0.30:4040", "akka.tcp://claxe@10.0.0.31:4040"]
            roles = ["tracker","crawlanalyser","initializer","productanalyser"]

            failure-detector {
                    threshold = 15.0
                    min-std-deviation = 250 ms
            }

            split-brain-resolver {
                    active-strategy = keep-oldest

                    keep-oldest {
                            # Enable downing of the oldest node when it is partitioned from all other nodes
                            down-if-alone = on

                            # if the 'role' is defined the decision is based only on members with that 'role',
                            # i.e. using the oldest member (singleton) within the nodes with that role
                            role = "lighthouse"
                    }
            }
    }
Dan
@ctrlaltdan

Question regarding the lighthouse/voting mechanism...

Whilst developing locally I frequently debug/exit processes which inevitably causes unreachable nodes. I had been using the pbm tool to clear these manually as I assumed the absence of enough running nodes was preventing the voting mechanism from cleaning up correctly.

My attempt at fixing this was to deploy 5 lighthouse nodes. Unfortunately this still seems to have the same issue as only having one lighthouse node.

Does anyone have any recommendations for working locally?

[Unspecified/localhost:9110] pbm> cluster show
akka.tcp://imburse@docker.for.win.localhost:55679 | [client-configuration-v1] | up | unreachable
akka.tcp://imburse@docker.for.win.localhost:55686 | [client-api-v1] | up | unreachable
akka.tcp://imburse@lighthouse-1:4053 | [lighthouse] | up |
akka.tcp://imburse@lighthouse-2:4054 | [lighthouse] | up |
akka.tcp://imburse@lighthouse-3:4055 | [lighthouse] | up |
akka.tcp://imburse@lighthouse-4:4056 | [lighthouse] | up |
akka.tcp://imburse@lighthouse-5:4057 | [lighthouse] | up |
Arjen Smits
@Danthar
For ppl interested in Alpakka and akka.streams connectors
Aaron Stannard
@Aaronontheweb
@QwerSense not a chat application, but does use SignalR and Akka.NET on .NET Core: https://github.com/petabridge/akkadotnet-code-samples/tree/master/Cluster.WebCrawler
GianPiero Bresolin
@ninjabadgerpirate
Hi, what's the best practice when working with HOCON files, app.config files and remote actors? If I have a main actor (A) that creates the initial ActorSystem and actors that loads it's config from a local HOCON file using FromConfig.Instance, and another AKKA project (B) which acts as a remote worker instance, should I be copying the HOCON files and config files from the A project to the B project as well?
Currently when I try to create new instances of child actor on the B worker instance in the PreStart method, I get failures because it cannot find the HOCON config for that worker on the remote.
I was wondering if someone could give me some guidance on what the recommended approach would be
Thanks very much
atresnjo
@atresnjo
I'm receiving an Unhandled message, even though I am 100% sure I subscribe to it. Any ideas why this might happen?
grafik.png
atresnjo
@atresnjo
nevermind me, while refactoring ended up with duplicates
Nick Polyderopoulos
@NickPolyder
Hello guys, I'm experiencing a problem with unit testing my supervisor strategy.

It seems that while i am using

Sys.ActorOf(SupervisorActor.Create(loggerMock.Object,
                dbActorFactory,
                ignore), ActorNames.SupervisorActor)

and trying to read that the excpection happened with

EventFilter.Exception<NullReferenceException>().ExpectOne(() =>
            {
                loggerMock.Verify(log => log.Error(It.IsAny<Exception>()), Times.Once);

                sut.Tell("test");

                ExpectMsg<LogExceptionMessage>((msg) =>
                    {
                        msg.Exception.Should().NotBeNull().And.BeOfType<InvalidOperationException>();
                        loggerMock.Verify(log => log.Error(It.IsAny<Exception>()));
                    });

            });

EventFilter runs the ExpectOne with any kind of Exception even if i didnt throw that kind of exception. and the supervisor has not yet send the real message

Aaron Stannard
@Aaronontheweb
I'll try to check back on these unanswered questions here later today - kind of dealing with some hot potatoes otherwise :p
also, I'm working on a re-imagining of the AtLeastOnceDeliveryActor base class: https://github.com/Aaronontheweb/Akka.AtLeastOnceDeliveryJournaling