You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2023. It is now read-only.
I'm building a realtime app and therefore make extremely use of the graphql subscriptions.
When a user makes a subscription i internally return a "publisher" as it should be. I internally keep a reference to this publisher in order to regularly post internal events to the client. Works pretty good.
My problem comes when the websocket connection to the server gets broken. In the former version 5.3.1, i could, for such cases, always see stacktraces of the EOFException in the logs. This EOFException seems to be handled pretty much better in the current version 5.10.0 of the framework.
My question: Is it possible that i implement a handler for this particular exception? With this handler i will be able to clean the references to the publisher i keep, so as to avoid loading memory.