select
> router with ActorSelection. However you can select individual
> children with ActorSelection which has names c1, c2, ...:
>
> ActorSelection router_selection =
>
> test_system.actorSelection("akka.tcp://PingActorSystem@192.168.2.17:2553/LocalRouter
>
.2.17:2553/LocalRouter
> <http://PingActorSystem@192.168.2.17:2553/LocalRouter>/c1");
>
> But that is not very useful.
>
>
> On Fri, Jul 11, 2014 at 2:00 PM, Pierre Falda
> wrote:
>
>> Hi everyone,
>>
>> I set up a little testing environment to de
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
k
>
> On 9 July 2014 at 10:44:17, Pierre Falda (p.f...@disbrain.com
> ) wrote:
> Hello everyone,
> I had a simple two layer akka (test)deployment with akka 2.2.1 and was
> working well.
> It was quite simple: a machine is responsible for router creation and
> forwarding
:2553/user/ResolveService/c2]
[DEBUG] [07/09/2014 10:13:41.238]
[BrainRoutingSystem-akka.actor.default-dispatcher-24]
[akka.tcp://BrainRoutingSystem@Vortex:2553/system/remote-watcher] Unwatched
last watchee of node: [akka.tcp://DisBrainBackend@Vortex:2552]
Do you have any idea on how to resolve/identify th
