This is only an error if the connection was *not* idle. It is *not* a bug
that idle connections are closed, that was the desired behavior. The
original bug was that it closed the connection even if it was not idle.
Please check if the connection was not idle or not. We will likely change
the
Hi
I get the response in 20 millis
but I've updated to M2 and still the same error:
[ERROR] [12/01/2015 13:40:21.516] [default-akka.actor.default-dispatcher-9]
[akka.actor.ActorSystemImpl(default)] Internal server error, sending 500
response
java.util.concurrent.TimeoutException: No elements
Hi
I understand the error is linked to this configuration
http.server {
parsing.max-method-length = 3000
idle-timeout = 2 s
remote-address-header = on
max-connections = 50
}
where I set idle-timeout = 2s what does it means. I've set this limit make
like a gobal timeout to the
It can very well be. If the response is longer then 2 sec, this bug might
trigger.
On Sun, Nov 15, 2015 at 4:28 PM, Konrad Malawski <
konrad.malaw...@typesafe.com> wrote:
> Hi all,
> thanks for trying out the early Milestone and reporting the problem!
> We believe there is a bug in how the idle
Hi all,
thanks for trying out the early Milestone and reporting the problem!
We believe there is a bug in how the idle timeout was added, not sure if that
specific problem is a manifestation of it,
but we'll add more tests and fixes for idle timeouts in M2 (coming out soon),
please keep an eye
Thanks
Is there any impact on serving ?
On Sunday, November 15, 2015 at 8:53:05 AM UTC+2, Ryan Brozo wrote:
>
> I am also getting the exact same error in 2.0-M1.
>
> I tried some logging using the logRequestResult directive to see which
> requests are getting the InternalServerError. But it
I am also getting the exact same error in 2.0-M1.
I tried some logging using the logRequestResult directive to see which
requests are getting the InternalServerError. But it seems none of the
requests I'm making are getting a 500 status code.
--
>> Read the docs:
