On Tue, Mar 22, 2022 at 12:47 PM Thomas Heigl <tho...@umschalt.com> wrote:

> Hi,
>
> Yesterday, I discovered that our attempted fix for
> https://issues.apache.org/jira/browse/WICKET-6944 didn't work. Application
> destroy listeners are still registered for every new Websocket connection
> and never cleared.
>
> I can see two options to fix this:
>
> 1. Keep the current listeners and try to find a solution based on static
> fields and careful registering and unregistering of application listeners.
>

https://github.com/apache/wicket/pull/505
A possible solution for this approach.



> 2. Add an AtomicBoolean Application#destroyed field that is set during
> Application#destroy and can be queried via Application#isAlive or
> Application#isDestroyed. This would allow us to replace the current
> listener based approach with something much simpler.
>

I don't mind this approach too!



>
> WDYT?
>
> Best,
>
> Thomas
>

Reply via email to