I see that none of NuGet packages for the actual persistence plugins has been updated to 1.0.7 on NuGEt.
so i have a question. i have an actor that gets a message from a remote client. in this message is information about a class this actor should retrieve from the container and a method and a bunch of params that the actor should call as well as the return type. so i have this actor that retrieves the object form the container, checks if there's a method on that class that fits the description of the message and then tries to call it with
Invoke(). so far so good. it is all working so far. i put this Invoke() call inside a try catch block because i basically want to tell the sender if something happened to while calling the method and basically return the thrown exception as a message back to sender. but when the invoked method itself throws a TargetInvocationException because of reasons it seems the actor just dies. and i get some disassociation messages in the log and stuff like that. it's like the try catch block inside the receive method is just not working. any hints?
@object there is a PR akkadotnet/Akka.Persistence.SqlServer#24 that updates the plugin, so you need to wait until this was merged and released
What does this mean when building Akka.net
---------------------------------------------------------------------
1) Building C:\CF\SourceCode\akka.net\src\Akka.sln failed with exitcode 1.
2) MSB4126: C:\CF\SourceCode\akka.net\src\Akka.sln.metaproj(0,0): The specified solution configuration "Release|MCD" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration.
---------------------------------------------------------------------
How do I rectify this problem? I am building from the command line using build build
@schepersk you need to exclude Lighthouse from your shard regions in your configuration
it will never work
under any circumstances
because it doesn't run Akka.Cluster.Sharding or Akka.Persistence or Akka.Cluster.Tools
use the roles setting
I am trying to run the cluster sharding example. Since I cannot compile the akka project I pulled the ClusterSharding.Node out into a clean solution. Installed all the references via Nuget. I am getting an error in the following line:
public override string PersistenceId { get; } = Context.Parent.Path.Name + "/" + Context.Self.Path.Name;The error is...
Akka.Persistence.UntypedPersistentActor.Context' is a 'property' but is used like a 'type'
What's missing?
Is the Ask valid in this sence or should i try to remove it in general?
var creditor = Context.ActorOf(PaymentCreditor.GetProps());
service.Ask(AccountCommands.GetIdentity(state.AccountId))
.PipeTo(creditor, success: m => PaymentProcessCommands.Credit(Id, m, state.Description, state.Amount));
this will set creditor as message sender
If i am sending the accountIdentity to the creditor before the credit command to set up the state, i would need to remove the account field of the credit command
this is sample hocon.
akka {
actor {
guardian-supervisor-strategy = "UserSupervisorExample.UserSupervisorStrategy"
}
}namespace UserSupervisorExample
{
public class UserSupervisorStrategy : SupervisorStrategyConfigurator
{
public UserSupervisorStrategy()
{
}
public override SupervisorStrategy Create()
{
return new OneForOneStrategy((excep) =>
{
int x = 3;
x = 6;
return Directive.Restart;
});
}
}}
however, Exception occurs in ActorSystem
akka {
actor {
guardian-supervisor-strategy = "HelloWorldUserSupervisor.UserSupervisorStrategy, HelloWorldUserSupervisor"
}
}
actor {
guardian-supervisor-strategy = "HelloWorldUserSupervisor.UserSupervisorStrategy, HelloWorldUserSupervisor"
}
}
i forget dll name. ^^;;
anyone got anything on my problem? i have a remote actor that i send a message to via a client. and as soon as that remote actor does anything that generates an exception that gets caught and handled in the remote actor the connection gets disassociated and the thing basically dies. what am i doing wrong here?
i will build a test solution and try if i get the same error there and if i do i'll up it on github
@Horusiath For the snapsot generation algo. there is beside event-count an other possibility. When each event has a timestamp and it is assumed that the application is pushing constantly events to the event-stream, then it is highly plausible that events in a short time frame are loaded faster then events over an longer timeframe. If the the events are over a long period >24h not snapshotted it can be done, even with only 2 events.
but as i said i'll try to make a test program that "hopefully" has the same problem
