Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

Hi Gary, did you find out what's going on by now? If I understand correctly, you get latency spikes as soon as you use the `entity[as[String]]` directive? Could you narrow down if there's anything special to those requests? I guess you monitor your GC times? Johannes On Wednesday, November 1,

Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

Hi Johannes, Yes; we are seeing 2-3 requests/second (only in production) with the latency spikes. We found no correlation between the gc times and these request latencies, nor between the size/type of requests. We had to pause the migration effort for 2 weeks because of the time being taken, but

Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

I wonder if you could start a timer when you enter the trace block and then e.g. after 200ms trigger one or multiple stack dumps (using JMX or just by printing out the result of `Thread.getAllStackTraces`). It's not super likely that something will turn up but it seems like a simple enough thing

[akka-user] Re: HTTP Chunk Size Exceeds the Configured Limit

Chunk size and entity size are 2 different configuration settings. You can easily set bigger chunk size for all connections in your application config see akka.http.parsing.max-chunk-size. If you want to do it programmatically i think right now it is only possible via connection: private fina

[akka-user] TCP idle-timeout encountered on connection

Hello, I'm facing this issue not always but few times (and I want to handle this in my code): *[ERROR] [11/16/2017 15:42:42.908] [myactor-threadpool-dispatcher-7] [TaskInvocation] TCP idle-timeout encountered on connection to [* *api.XYZ.com**:443], no bytes passed in the last 50 seconds (akka

[akka-user] Re: TCP idle-timeout encountered on connection

Full exception is : (akka.stream.scaladsl.TcpIdleTimeoutException: TCP idle-timeout encountered on connection to [*api.XYZ.com *:443], no bytes passed in the last 1 minute) On Thursday, Nov