[akka-user] Re: Swakka - a new extension to akka-http for Swagger/OpenApi

Thanks for reporting this, Philippe. For anybody who experienced this problem, fixed in https://bitbucket.org/jtownson/swakka/commits/0f5cb77196ea83135f9ca7913f1f111f6b39f369. Please pull from master. Actually I am planning a move to github soon, because of their really good usage stats. On

[akka-user] Re: Swakka - a new extension to akka-http for Swagger/OpenApi

I had issues with credentials w.r. sonatype and removed all references thereof in build.sbt and plugins.sbt and this temporarily resolved my issues. I am not interested in publishing artifacts to an external site but perhaps you are. On Tuesday, January 30, 2018 at 10:08:06 AM UTC-5,

[akka-user] Re: Swakka - a new extension to akka-http for Swagger/OpenApi

Would you consider migrating the project to github since you find it more stable now? I am unable to make use of it from bitbucket due to some sonatype_credentials file issue, which looks mysterious to me and would like to give this a dev try today. Thanks, Phil On Wednesday, January 24,

Re: [akka-user] Mutual Authentication using Akka HTTP

Did you see the Mutual Auth section in the Akka HTTP docs? https://doc.akka.io/docs/akka-http/10.0.11/scala/http/server-side/server-https-support.html#mutual-authentication The synthetic Tls-Session-Info header should give you access to the client certs etc. -- Johan Akka Team On Mon, Jan 29,

Re: [akka-user] Akka Default Dispatcher creating 9000+ Worker Threads!!

Please read the docs about this effect here: https://doc.akka.io/docs/akka/current/dispatchers.html#blocking-needs-careful-management It’s the Fork Join Pools (JDK) reaction to doing “bad things”™ (blocking) to it. The solution is as Johan explained. -- Cheers, Konrad 'ktoso '

Re: [akka-user] Akka Default Dispatcher creating 9000+ Worker Threads!!

If you use Await.result, Await.ready or surround logic with scala.concurrent#blocking and use a FJP dispatcher, that will fork unbounded amounts of threads for those blocks, so that could perhaps explain why you are seing so many thread. Looking at stack dumps should show you what those threads

Re: [akka-user] Akka typed - first impressions

Hi Patrik, Thanks for pointing me at the actor-to-actor pull request - it seems like it would be very useful in "pipe to self" use-cases. It makes me wonder, though, if it wouldn't be possible to do something similar while "piping" to other actors. In my experience (which admittedly, may not

Re: [akka-user] Managing long time processing using Akka Actors

Thanks for the help! My comments are in lined. On Tuesday, January 30, 2018 at 10:23:25 AM UTC+2, Manuel Bernhardt wrote: > > Hi, > so the problem is that you don't need all the actors for all nodes at all > times, but rather on demand, correct? > Yes. Actors are quite good for on demand, as

Re: [akka-user] Managing long time processing using Akka Actors

Hi, so the problem is that you don't need all the actors for all nodes at all times, but rather on demand, correct? You mention that you check the count of routees for each router. Are those pool routers? If yes, do you really need many routees for each check or could you reduce the amount