Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 08:45
    Zetanova commented #5152
  • 07:37
    Zetanova synchronize #5152
  • 07:15
    Zetanova commented #5273
  • 05:12
    Zetanova synchronize #5273
  • 04:51
    Zetanova synchronize #5273
  • Sep 17 16:56
    Aaronontheweb commented #5273
  • Sep 17 08:49
    Zetanova review_requested #5273
  • Sep 17 03:30
    Zetanova synchronize #5273
  • Sep 17 02:41
    Zetanova commented #5273
  • Sep 17 00:44
    Arkatufus closed #5284
  • Sep 16 21:14
    Arkatufus opened #5284
  • Sep 16 20:05
    Arkatufus synchronize #5282
  • Sep 16 19:47
    Aaronontheweb commented #5273
  • Sep 16 19:28
    Aaronontheweb commented #5273
  • Sep 16 19:18
    Aaronontheweb commented #5273
  • Sep 16 19:16
    Aaronontheweb commented #5273
  • Sep 16 19:15
    Aaronontheweb commented #5273
  • Sep 16 19:11
    Aaronontheweb commented #5273
  • Sep 16 16:52
    Aaronontheweb commented #4989
  • Sep 16 16:17
    dependabot[bot] labeled #5283
Aaron Stannard
@Aaronontheweb
if your actor throws
and gets stopped
CurrentMessage is still the original message that caused the throw
because CurrentMessage = null never gets to run
exception disrupted it
so looks like it should still be preserved
if you just use that property
Paul Trandem
@ptrandem
Using that property would be great, but it's not exposed via IActorContext; i can only see it in the debugger.
I'll take a look at ActorCell as well.
Aaron Stannard
@Aaronontheweb
if you do IActorContext.AsInstanceOf<ActorCell>
that would do it\
it's assignable to that type
like I said, hacky
but it should work
Paul Trandem
@ptrandem
aah! ok. Hacky, yes, but we'll give that a shot. Thanks @Aaronontheweb !
Arsene Tochemey Gandote
@Tochemey
Hello I am having challenges create actors with Netcore where the actors need an injection of a repository at startup.
At any time I got System.ObjectDisposedException in the actor when accessing the repository interface
Bartosz Sypytkowski
@Horusiath
@Tochemey how and when are you creating your actors? Example: If you create an actor in some managed other context (i.e. http request handler) using that context's lifecycle to inject repository, it's quite probable that this repository will be disposed, while actor still lives - as actor context may live longer that context of http request.
Arsene Tochemey Gandote
@Tochemey
Ok
Arsene Tochemey Gandote
@Tochemey
@Horusiath Please is there a way to create actors with DI where the actors has constructors params?
Hyungho Ko
@hhko
My app got this log.
The remote system has quarantined this system. No further associations to the remote system are possible until this system is restarted.
How to solve it?
When it occur?
Aaron Stannard
@Aaronontheweb
occurs when a system message, which normally has reliable delivery attached to it, fails to get delivered
i.e. stopping an actor
death watching an actor
etc
sending a Termination notice back
way to fix it is to restart the quarantined system
that quarantine signal basically means that the state of your ActorSystem is corrupt as far as the remote system is concerned
you can subscribe to a ThisSystemQuarantined event
from the EventStream
that you'll receive that signal when you are quarantined by someone else
Hyungho Ko
@hhko
Yes I can subscribe to a "ThisSystemQuarantined" event.
but I don't know how to restart ActorSystem on run-time?
Aaron Stannard
@Aaronontheweb
you'd want to have something that sits outside the ActorSystem
that you can invoke from an actor
so in the case of a Topshelf service
I could have a static method I could invoke
that would dispose the old ActorSystem and re-create it
Hyungho Ko
@hhko
Could you recommend some code or example for it?
I am wondering while ActorSystem re-creating
the remote another actor can send some messages to that?
is it ok?
Aaron Stannard
@Aaronontheweb
if you get quarantined by one system
that's only a 1:1 relationship
you might not be quarantined by the others
but I don't have any sample code on-hand unfortunately :(
Jack Wild
@jackowild
@Horusiath Please is there a way to create actors with DI where the actors has constructors params?
I would also like to know the answer to this one.
At the moment I create the actor using Context.ActorOf(Context.DI().Props<MyActor>())
Then send in an initialisation message which contains some state I want the actor to have. I'd rather pass this state into the constructor, along with the dependencies I want resolving using Akka.DI. Is this possible? Or are we asking for too much...