it looks like our multinode test runner swallows stack traces from exceptions
also another question: from where those messages, that test runner shows, are taken from? They are not standard logging bus messages.
does anybody have a simple Akka.Cluster example with Lighthouse running as a seed node A and a message is sent from non-seed node B to non-seed node C?
all the examples I can find are either super simple (subscribing to cluster events) or crazy complex (e.g. the WebCrawler one which is doing remote deployment)
I am getting an error like this: "Message TestRequest from akka://testcluster/user/source_actor to akka://testcluster/user/target_actor was not delivered. 1 dead letters encountered" - I can see Lighthouse has got node B and C on its membership list but just can't seem to send messages across the cluster
I am using ActorTaskScheduler to execute some AsyncMethods inside an actor.
Sometimes a thread is blocking at TryExecuteTask(task); Line-64
It is blocked by a RX Subject hosted with TaskPoolScheduler.ScheduleLongRunning();
Its like, it was queued by RX for LongRunning and ended up in the Akka Scheduler.
Its waiting now for new RX Events and this Subject is a Infinite Event Feed.
And so the Actor is not serving message anymore.
Sometimes a thread is blocking at TryExecuteTask(task); Line-64
It is blocked by a RX Subject hosted with TaskPoolScheduler.ScheduleLongRunning();
Its like, it was queued by RX for LongRunning and ended up in the Akka Scheduler.
Its waiting now for new RX Events and this Subject is a Infinite Event Feed.
And so the Actor is not serving message anymore.
the LongRunning thread from the RX Subject is created on the first OnNext()
How schould a scheduler behaive on LongRunning? Is this a miss by the AsyncTaskScheduler ?
"In practice, our actual implementation in .NET 4 does exactly what you say, using a non-ThreadPool thread to run the Task, but that's an implementation detail, and could change in the future."
"The default TaskScheduler implements LongRunning as I outlined above, but a custom scheduler could do whatever it wanted with the LongRunning hint."
@rogeralsing do you think, we could incorporate delegate serialization in Wire? (I'm not saying doing this for lambdas, but only for delegates)
is it safe to use FutureActorRef directly? Is it considered public or internal api?
@nvivo its private
@rogeralsing I need a form of "ask" using the event stream. I want to publish a request and wait for the first message to come back. I'm using regular actors now, but I'd like to avoid creating an actor for each request
is there any way to do this currently?
I'm currently trying to copy the code from Ask and implement it directly in my code, trying to see if this works
that should be possible, there is no magic in there except for the usual
sender stuff, but other than that it should be straightforward
yeah, I'm adding the sender to the message, so I can reply without an implicit sender
ok, I'll keep going and see if it works
thanks
@Horusiath is there a specific use case you need it for?
does Akka.Cluster require manual tracking of ClusterEvent.MemberUp messages to correctly figure out when it's possible to communicate with the cluster?
I'm struggling with messages not being delivered to the cluster but even with all debugging options I can find enabled I'm none the wiser
@rogeralsing I haven't got Internet for half of a day, so I've created a seed for akka-typed on C# ;) Many features are already there
but since it works on delegates, it requires to make them serializable
@ryanjshaw basically yes, you should subscribe to cluster events on PreStart.
@Horusiath even though I do that, my messages are not getting delivered to cluster members (I can confirm I'm receiving MemberUp messages for these members). am I incorrect in thinking if node A is lighthouse, node B has a "/user/source_actor" and node C has "/user/target_actor", then from node B doing Context.ActorSelection("/user/target_actor").Tell(new TestMessage()) should be delivered to node C?
@rogeralsing anything I can help you with to get a hocon release ready? Would like to remove my local version ;-)
@Silv3rcircl3 the main issue with the extracted hocon lib is that we want to keep compatability with existing code, but it should be possible if we just remove the hocon code in akka.net and add a ref to the new lib
the configuration section loaded probably needs to exist in the Akka.net lib still though, as existing code points to the akka.net lib fully qualified assembly name
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<section name="akka"
type="Akka.Configuration.Hocon.AkkaConfigurationSection, Akka" /> <-- this bit points to akka.net lib
but if that class stays in akka.net, and the rest is in the hocon lib, then everything should be fine I think
that would be an interesting blog post ;) hint hint
I see, in my case I want to use hocon without akka, so I would be satisfied if hocon would be released also if akka doesn't use the new lib ;-) but if nobody else is doing it, I could try to replace it inside akka
I'll make it a new year resolution
hello, have anybody got problem to run akka.remote.tests in visual studio?
I've got an error "System.IO.FileLoadException: Could not load file or assembly 'xunit.execution.desktop, Version=2.1.0.3179, Culture=neutral, PublicKeyToken=8d05b1bb7a6fdb6c' "
the same error if to do it by xunit.console.runner
@ryanjshaw don't think about nodes in context of virtual machines. If you want to apply some specific behavior to node, group them by using cluster roles. If I'm right, on MemberUp you receive
Member info about new cluster node - this member contains list of roles, that member fulfills. Just check it if is desired one. If so, you may assume that it has particular set of actors working on it and send messages to them.
@Aaronontheweb where do we get akka.net logo for NuGet from? nvm, found it
@maxim-s try to get nuget reference to xUnit test runner
Morning guys. I hope someone can show me how to correctly use the
BackOffSupervisor. I set up two actors like following, and expect the FakeActor to be restarted after 10 seconds, but it seems to keep processing it without a backoff.public class TestActor : ReceiveActor
{
private IActorRef _child;
public TestActor()
{
Receive<string>(msg =>
{
_child.Forward(msg);
});
}
protected override void PreStart()
{
var ch = Props.Create(() => new FakeActor(), OneForOneStrategy.StoppingStrategy);
_child = Context.ActorOf(Props.Create(() => new BackoffSupervisor(ch, null, TimeSpan.FromSeconds(10), TimeSpan.FromMinutes(1), 0.25)));
}
}
public class FakeActor : ReceiveActor
{
public FakeActor()
{
Receive<string>(msg =>
{
FatalError();
});
}
protected override void PostStop()
{
Console.WriteLine("Actor is stopped");
}
protected override void PreRestart(Exception reason, object message)
{
if (message != null)
{
Self.Forward(message);
}
base.PreRestart(reason, message);
}
private void FatalError()
{
throw new InvalidOperationException();
}
}