I'm trying to implement Websockets in Wicket 7 (EAP 6.3 environment) following this mini-tutorial.
Everything is working as expected, except for the websocket is automatically closed after 60 seconds of inactivity. I've read in different places that I have to change the idle timeout for keeping the websocket open, but I can't find where to set the timeout in the Wicket implementation.
Another solution would be to send an empty message for keeping the connection alive, but I don't want this approach.
Did anyone find this problem working with websockets in Wicket 7?
Any suggestions would be appreciated.
Thank you!
I haven't tried it but maybe you can use 'ping' message to keep the connection aliveRemoteEndpoint#sendPing()
At the moment Wicket doesn't expose this API but if you confirm that it does the job then please create a ticket at Apache JIRA and we will add it.