Re: [jetty-dev] SharedBlockingCallback

[Guillaume Maillard <guillaume.maillard@xxxxxxxxx>]

Hi,

I just opened the issue.

Sadly, I have no way to reproduce it except waiting a week or two for the magic "lock" to happen on the prodcution server.

Best regards,

Guillaume

2017-09-15 8:20 GMT+02:00 Simone Bordet <sbordet@xxxxxxxxxxx>:

Hi,

On Thu, Sep 14, 2017 at 11:14 PM, Guillaume Maillard
<guillaume.maillard@xxxxxxxxx> wrote:
> Yes you are right, but after that Jetty is not responding anymore to
> resquests... blocked in outputstream write()... which is the real issue...

Please file an issue about this at
https://github.com/eclipse/jetty.project/issues/.

Do you have a reproducible test case ?
If so, please attach it to the issue.

We should close the connection after a 400, and it's strange that we
block in write, so we need to understand the issue before telling
whether it's a timeout issue or something else.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev