Ok, It was a maven problem of some kind. Did a mvn clean install and suddenly it started working. I have no clue…
We can close this one K > On 12 Dec 2019, at 20:31, Simone Bordet <[email protected]> wrote: > > Hi > > On Thu, Dec 12, 2019 at 6:51 PM Joakim Erdfelt <[email protected]> wrote: >>> >>> 17:41:18.640 [eduler-1b868ef0] DEBUG org.eclipse.jetty.io.FillInterest:134 >>> - onFail FillInterest@13a1a18f{null} >>> java.util.concurrent.TimeoutException: Idle timeout expired: 30005/30000 ms >>> 17:41:18.640 [eduler-1b868ef0] DEBUG org.eclipse.jetty.io.WriteFlusher:490 >>> - ignored: WriteFlusher@15e95526{IDLE}->null >>> java.util.concurrent.TimeoutException: Idle timeout expired: 30005/30000 ms >> >> >> That looks like the normal persistent HTTP/1.1 connection being idle timed >> out after the request is handled. > > Except the request is not handled, there is no trace of read from the > network or HTTP parsing. > It's really weird. > > -- > Simone Bordet > ---- > http://cometd.org > http://webtide.com > Developer advice, training, services and support > from the Jetty & CometD experts. > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/jetty-users _______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
