Re: [jetty-users] Unresolved callbacks

[Simone Bordet <sbordet@xxxxxxxxxxx>]

Hi,

On Tue, Apr 9, 2024 at 11: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.

We are working on a similar solution, see here:
https://github.com/jetty/jetty.project/pull/11786

Do you mind taking a look and see if it would cover your case, and if
not, propose the features you need?

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