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

[akka-user] Re: 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] Need to publish with DistributedPubSubMediator when MemberUp in Cluster and Mediator is ready to publish to new node in cluster

On Wed, Nov 9, 2016 at 1:59 PM, Ricardo Gasca wrote: > I'm working in the following scenario: > > >- Cluster Akka with several nodes. Each node has: > - several publishers that share a part of whole information in the > system. Like a shard. > - several

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] StreamSupervisor name

I'm trying to write two ScalaTest tests to compare two approaches to driving a Flow that sends out emails. In one approach the flow is sourced using eventsByTag from akka-persistence-query. In the other, I uses SourceQueue.offer after receiving a message via AtLeastOnceDelivery. The test ends with

[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

Re: [akka-user] Re: Akka persistence query examples

Hi everyone. Just waking up this thread (once again) with a related challenge/question I'm used to use PersistentView for my read model before they got deprecated. I have a CQRS architecture where both write and read sides are cluster singleton. In write side I use persistent actors to

[akka-user] Re: Akka-stream - aggregate record counts while writing to a sink, and update an object in the middle of the flow process with the aggregated data.

I guess you need to return a source built with the builder. Other problem is you build a ClosedGraph in ~> flow ~> sink Em terça-feira, 8 de novembro de 2016 22:49:31 UTC-3, Eugene Dzhurinsky escreveu: > > Got some time to experiment: with this definition > > val fetchLikesAndUpdateProfile

[akka-user] Need to publish with DistributedPubSubMediator when MemberUp in Cluster and Mediator is ready to publish to new node in cluster

I'm working in the following scenario: - Cluster Akka with several nodes. Each node has: - several publishers that share a part of whole information in the system. Like a shard. - several subscriber that works with the whole information in the system. - When a

[akka-user] Error: akka.dispatch.Dispatcher in application-akka.actor.default-dispatcher-6 problem in scala.concurrent internal callback

Hi, I'm trying to use akka 2.4.12 with play 2.5.4. I'm injecting ActorSystem using "*GuiceApplicationBuilder().injector()*" with "system = injector.instanceOf[ActorSystem]" or "*@Inject()(**implicit val system: ActorSystem**)*" to get an instance of ActorSystem. I'm using these two mechanisms