[akka-user][deprecated] Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

Is this resolved problem? On Sunday, May 28, 2017 at 3:03:06 PM UTC+9, Vishnu Vardhan wrote: > > Hi Johan, > > Was there a defect logged for this issue. I seem to be suffering from > exactly the same symptoms. I am now checking the docker / docker on > different hosts. > > A related issue is

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

Hi Johan, Was there a defect logged for this issue. I seem to be suffering from exactly the same symptoms. I am now checking the docker / docker on different hosts. A related issue is the shutdown behavior if one of my producers is on bare metal, and the consumers is on a docker container. I

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

Another piece to the puzzle: docker <-> docker does work routed through the host as long as the containers run on different hosts. It's only when doing docker <-> docker routed through host on the same host that it doesn't work. Seems like an issue in the artery or aeron protocol. Den onsdag

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

One additional piece of info that could be useful: It works if I let the docker containers call each other by container IP instead of host IP+fowarding. Den onsdag 9 november 2016 kl. 19:29:44 UTC+1 skrev Akka Team: > > Ah, sorry, didn't notice it in the command line. > > Can you verify with

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

With akka.loglevel = DEBUG i only get two more lines on the consumer side: First [DEBUG] [11/09/2016 20:29:02.937] [aeron-client-conductor] [akka.remote. artery.ArteryTransport(akka://consumer-system)] onAvailableImage from 172.17.0.1:52515 session 2110811048 And then a few seconds later

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

Ok hm sorry.. this is a lot of new things to take in for me :). How do I change debug level for akka? Is there a typesafe/akka conf parameter? I may try the FlightRecorder later if I have time. I think we're probably going to stick with netty.tcp for now though while artery has some time to

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

New info. I have now tested regular udp docker <-> docker - with the exact same application repurposed for raw java udp sockets. Using the same command line arguments. *It works fine with regular udp docker<->docker*. It's just artery that doesn't want to work for me I suppose :(. Could it be

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

looks related -- Cheers, √ On Nov 9, 2016 20:13, wrote: > Well, host <-> docker container artery works (both permutations). It's > just docker <-> docker on the same host that doesn't. > So udp forwarding seems to work. I will try to figure out a

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

Well, host <-> docker container artery works (both permutations). It's just docker <-> docker on the same host that doesn't. So udp forwarding seems to work. I will try to figure out a non-artery way of testing udp. Might end up writing a small scala echo server + client with udp (im terrible

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

Ah, sorry, didn't notice it in the command line. Can you verify with some other tool that you can communicate using udp between the nodes? (using netcat for example) Set logs to debug to see if there is anything helpful in there. Additionally artery contains a "flight recorder" which you can

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

Yes - i Did. Please see my original post for details. You will see that I use the udp parameter for my docker port forwarding. Also please note that I've tested artery successfully in docker as long as one of the applications is running outside docker. However the problem occurs only when both

Re: [akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

Hi Johan (good name!), Artery/Aeron uses UDP, while the old remoting is TCP-based, did you configure your docker nodes with udp port mappings? -- Johan Akka Team On Wed, Nov 9, 2016 at 6:11 PM, wrote: > I'm pretty new to Akka and am currently trying out

[akka-user] Akka-remote docker<->docker works fine with netty.tcp, but fails with artery - ideas?

I'm pretty new to Akka and am currently trying out Akka's new Artery backend for akka-remoting (http://doc.akka.io/docs/akka/2.4/scala/remoting-artery.html) while also testing the regular netty.tcp transport (http://doc.akka.io/docs/akka/2.4/scala/remoting.html). It looks fairly straight