[akka-user] Re: [akka-http] Configuring HTTPS with a trusted certificate chain

Hi Johannes, Actually, I figured it out: embarrassingly, I had forgotten to import my private key into the Java keystore. Once I did that everything worked.. sorry to bother you! If only I had a type system that could have warned me about it ahead of time, ha ha.. Best, Julian On Thursday,

[akka-user] Re: Exposing Akka actors through a REST API

Not quite sure what you mean when you say you don't want to "manually encode" the routes in Akka HTTP. What is it about Akka HTTP that is giving you trouble? I personally have built a couple Akka applications with a REST API sitting in front of it. Most of the time I've used http4s but I've

Re: [akka-user] Akka-remoting with Artery using load balancing/round robbing dns

Thanks for clarifying that. We suspected that but weren't sure. We can close this thread ;). Thanks everyone for great input Skickat från min iPhone > 10 nov. 2016 kl. 18:03 skrev Patrik Nordwall : > > And for the record, it's just accidental that it works with tcp.

Re: [akka-user] Akka-remoting with Artery using load balancing/round robbing dns

Consider that confirmed then. ;) On Thu, Nov 10, 2016 at 5:12 PM, wrote: > Ok. Just wanted that confirmed. We already have a workaround for it so I > was mostly just curious to see if it was needed :). > > / Johan > > > > Den torsdag 10 november 2016 kl.

Re: [akka-user] Akka-remoting with Artery using load balancing/round robbing dns

And for the record, it's just accidental that it works with tcp. We don't guarantee that the same connection is reused. tors 10 nov. 2016 kl. 17:14 skrev Endre Varga : > Actor remote messaging is a P2P protocol and as such any kind of > name-remapping is harmful. Trying

Re: [akka-user] Akka-remoting with Artery using load balancing/round robbing dns

Actor remote messaging is a P2P protocol and as such any kind of name-remapping is harmful. Trying to load balance Akka Remote connections I think is a mistake and makes not much sense. You *can* load balance Akka provided services of course, but you need to expose them as a different protocol

Re: [akka-user] Akka-remoting with Artery using load balancing/round robbing dns

Ok. Just wanted that confirmed. We already have a workaround for it so I was mostly just curious to see if it was needed :). / Johan Den torsdag 10 november 2016 kl. 13:03:36 UTC+1 skrev √: > > the host needs to be a stable identifier. > > What problem are you trying to solve with the rr dns?

[akka-user] Re: [akka-http] Configuring HTTPS with a trusted certificate chain

Hi Julian, can you post more information about your code and what happens exactly when you run it? What kind of key material do you have and how do you load it? Are you using akka-http on the client side or on the server side? Johannes On Thursday, November 10, 2016 at 9:50:08 AM UTC+1,

[akka-user] Exposing Akka actors through a REST API

Hello everybody. Is there any project out there capable to easily build REST routes to Akka Actors? I would like to map REST resources to Akka Actors and messages other than manually encode the routes in Akka HTTP... Thank you. -- >> Read the docs: http://akka.io/docs/

Re: [akka-user] Why default-plugin-dispatcher is PinnedDispatcher thread-pool-executor ?

Because there is no reason for a FJP executor. PinnedDispatcher dedicates a thread to an actor, there is no sharing and hence no work stealing. FJP is overkill in that case and makes no sense. -Endre On Thu, Nov 10, 2016 at 12:41 PM, Yaroslav Klymko wrote: > Hi guys, > > Just

Re: [akka-user] Akka-remoting with Artery using load balancing/round robbing dns

the host needs to be a stable identifier. What problem are you trying to solve with the rr dns? On Thu, Nov 10, 2016 at 10:48 AM, wrote: > Case: > > I have two services (A and B) that wish to talk to each other using > akka-remoting over artery. > Each

[akka-user] Why default-plugin-dispatcher is PinnedDispatcher thread-pool-executor ?

Hi guys, Just curious about reasoning to make `default-plugin-dispatcher` as default-plugin-dispatcher { type = PinnedDispatcher executor = "thread-pool-executor" } Why not a fork-join-executor ? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ:

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

[akka-user] Akka-remoting with Artery using load balancing/round robbing dns

Case: I have two services (A and B) that wish to talk to each other using akka-remoting over artery. Each service executes on it's own machine behind a load balancer mapping a dns name, e.g. $A resolving -> multiple IP addresses. For A to talk to B, we can for example execute: // Make request

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

[akka-user] [akka-http] Configuring HTTPS with a trusted certificate chain

Hi akka-user, I'm trying to host a simple server that uses HTTPS. I'm having exactly the same problem as pointed out in this issue , where Chrome responds with ERR_SSL_VERSION_OR_CIPHER_MISMATCH. It worked when I used a self-signed certificate (while