I think this played largely during your vacation ;)
Next problem - I upgraded all my projects across the board to 1.1.1. When the actor system starts up, I now get this exception:
Logger [Akka.Event.DefaultLogger] specified in config cannot be loaded:
System.MissingMethodException: Method not found: 'System.Type Akka.Dispatch.Mailboxes.GetMailboxType(Akka.Actor.Props, Akka.Configuration.Config)'.
at Akka.Remote.RemoteActorRefProvider.ActorOf(ActorSystemImpl system, Props props, IInternalActorRef supervisor, ActorPath path, Boolean systemService, Deploy deploy, Boolean lookupDeploy, Boolean async)
at Akka.Actor.ActorCell.MakeChild(Props props, String name, Boolean async, Boolean systemService)
at Akka.Actor.ActorCell.AttachChild(Props props, Boolean isSystemService, String name)
at Akka.Actor.Internal.ActorSystemImpl.SystemActorOf(Props props, String name)
at Akka.Event.LoggingBus.AddLogger(ActorSystemImpl system, Type loggerType, LogLevel logLevel, String loggingBusName, TimeSpan timeout)
at Akka.Event.LoggingBus.StartDefaultLoggers(ActorSystemImpl system)
System.MissingMethodException: Method not found: 'System.Type Akka.Dispatch.Mailboxes.GetMailboxType(Akka.Actor.Props, Akka.Configuration.Config)'.
at Akka.Remote.RemoteActorRefProvider.ActorOf(ActorSystemImpl system, Props props, IInternalActorRef supervisor, ActorPath path, Boolean systemService, Deploy deploy, Boolean lookupDeploy, Boolean async)
at Akka.Actor.ActorCell.MakeChild(Props props, String name, Boolean async, Boolean systemService)
at Akka.Actor.ActorCell.AttachChild(Props props, Boolean isSystemService, String name)
at Akka.Actor.Internal.ActorSystemImpl.SystemActorOf(Props props, String name)
at Akka.Event.LoggingBus.AddLogger(ActorSystemImpl system, Type loggerType, LogLevel logLevel, String loggingBusName, TimeSpan timeout)
at Akka.Event.LoggingBus.StartDefaultLoggers(ActorSystemImpl system)
My HOCON config is very simple:
akka {
actor {
provider = "Akka.Remote.RemoteActorRefProvider, Akka.Remote"
}
remote {
helios.tcp {
port = 8092
hostname = localhost
}
}}
GetMsg and ProcessMsg are two separate actors, which ProcessMsg is created by GetMsg
I initialize like this
container.Register<QueryDataStoreActorBase, QuerySqlDataStore>();
var system = ActorSystem.Create("ActorSystem");
system.AddDependencyResolver(new SimpleInjectorDependencyResolver(container, system));
container.RegisterSingleton(system);
Just calling
var resolver = new SimpleInjectorDependencyResolver(container, system); is enough
it registers itself with the system
the
system.AddDepedencyResolver is a public api exposed for the DI plugins to use. It should not be used directly. Although it is possible, if you know what you are doing.
Oh? thats odd.
A will receive 2 response from 2 B instances, that's what I was thinking of testing but I can't find a way to "mock" router using testkit
The tests work. So plugin integration for 1.0.8 looks good
If you upgrade, you should rebuild the plugin against the latest akka.net packages
It looks ok.
I gtg, got a meeting
also check the tests project of the plugin, for details on how to register dependencies
could be the readme is wrong
gl!
Hey guys, I have a cluster running with 6 nodes including 2 seeds (A and B), all started at the same time. According to the logs, the leader is trying to move seed node B to [Up] every 3 or 4 seconds. Node B appears as "Joining" to my monitoring node but never goes to the Up status. No dead letters, no exceptions. I've restarted the whole cluster twice but the situation persists. Any ideas ?
interesting, it's always the last node I start that the leader is trying to move to Up but remains 'Joining' to the other nodes
