Re: [jetty-users] Unresolved callbacks

[Joakim Erdfelt <joakim@xxxxxxxxxxx>]

Please open an issue and include the details on which callbacks you are reporting.

Can you grab a stracktrace of when the callback was created and include that stacktrace when you detect your "not succeeded" action?

Note: you should check for succeeded and failed, if it didn't succeed, it should have at least called failed once.

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Tue, Apr 9, 2024 at 4:11 AM Matthias Pfau via jetty-users <jetty-users@xxxxxxxxxxx> wrote:

Hi there,
during the migration to jetty 12, we implemented a callback registry to make sure that we find places where callbacks are not succeeded.

It works like this: Every callback passed from jetty to our handlers is wrapped and registered. The callbacks get unregistered once the succeed function is called on the wrapped callback. Besides that, the wrapper is a delegate. Two hours after a callback was registered, we evict it from the registry and log the request URL.

Besides long running websocket connections, we expect that no callbacks are left in the registry after this time. We noticed that callbacks for a set of requests for static resources (e.g. index.html) that seem to belong to the same client are not succeeded. 

We were wondering if this is expected behaviour when a timeout happens.

Best,
Matthias
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users