Hi Martynas Mickevičius,
thank you, this fixed the connection problem with the hostname that I
reported in the other thread! :-)
Pierre
> Also I just noticed an error in your configuration. Instead:
>
> remote {
> enabled-transports = ["akka.remote.netty.tcp"]
> hostname = "Vortex"
>
Hi Martynas,
I think I found the problem reviewing some old code: I must specify /user
in the actoselection path:
ActorSelection router_selection = test_system.actorSelection("akka.tcp://
PingActorSystem@192.168.2.17:2553/user/LocalRouter");
Doing in this way works, but is this a bad pratice sin
Also I just noticed an error in your configuration. Instead:
remote {
enabled-transports = ["akka.remote.netty.tcp"]
hostname = "Vortex"
netty.tcp.port = 2553
}
it should be
remote {
enabled-transports = ["akka.remote.netty.tcp"]
netty.tcp {
hostname = "Vortex"
Hi Pierre,
router itself is not an actor. It is an optimized ActorRef which sends
messages directly to the routees. Therefore you can't select router with
ActorSelection. However you can select individual children with
ActorSelection which has names c1, c2, ...:
ActorSelection router_selection =
Hi everyone,
I set up a little testing environment to debug another problem with
remoting, but I'm stuck on an issue (?) with actorselection: telling a
message to a remotely created router works, telling the message to an
actorselectopn of that router, routes the message to deadletters.
Akka ve
