Sometimes google does magic :)
nm... I see you send back an
Error with an InvalidCastException
there was some good exposure for akka.net as well
In the docu it states that it is best not to instantiate the runtime in an ASP.NET application because IIS behaviour, which I agree upon, and, it states it would be best to create the runtime and actors in a separate application (or windows service). In this scenario, what would be the advised way to communicate between te ASP.NET applicaiton and the runtime? Is it a good idea to instantiate a runtime in the ASP.NET app which if it runs, gets a reference to the actors in the windows service runtime (using Akka.remote)? Any alternatives?
and pipe data to a cluster over Akka.Remote
you just want to avoid keeping stateful actors inside your web apps is all
wrote about this in some detail here: https://petabridge.com/blog/akkadotnet-aspnet/
@Danthar We should have a quick chat if we bump into each other :-)
hi @Danthar, trying to solve some strange issue with logging. Just need some extra hints what and how to check. For some reason logging is not working on the web node. Config is the same as on windows service. Logging itself is working outside of the akka code. Any hints?
hi. I've a question about akka.net and I can't find the answer anywhere. I'd like to use akka cluster with priority mailbox. Is it possible? The cluster works as expected (without the mailbox), and the priority mailbox works fine locally. But when I try to deploy nonlocal routee actors with my custom priority mailbox, the messages are not processed regarging to their priorities. Can you help me please? Is there any example?
What is the best way to call an async method in the AroundPreStart method?
Can just do async method().configureAwait(false);?
If so is there any side effect since the method is returning void?
@Tochemey whenever I need to do some async work before getting the actor ready, I do something like:
Constructor() {
Self.Tell(new Initialize());
ReceiveAsync<Initialize>(async _ => {
await Whatever();
...
Become(Ready);
});
}
void Ready() {
Receive<ActualMessages>(...);
...
}
but the priority mailbox works only for specific actors
but it sounds like remote deployment with a custom mailbox is not working? am I correct in understanding that?
if so, could you please open up a Github issue for that? should be easy for us to test if that's the case
might be an issue with the fully qualified name of the mailbox not being passed through correctly
also: the binary that defines the custom mailbox is present on both the deployer and the deployee , right?
and the mailbox is registered with the same name on both the deployer and deployee's HOCON too?
