Sorry,
Misread it :(
I actually using both.
Ajax request refreshing HTTP session and binary ping refreshing websocket
connection and being ignored
WBR, Maxim
(from mobile, sorry for the typos)
On Sep 19, 2017 02:49, "Martin Grigorov" wrote:
> Hi,
>
> @Maxim: the problem Manfred faces is not tha
Hi,
@Maxim: the problem Manfred faces is not that the Http Session expires but
that the WebSocket connection is closed by the web container due to
inactivity.
@Manfred: I'd use server-side timer that uses the
IWebSocketConnectionRegistry to send the heartbeat message to all connected
clients. The
Hello Manfred,
AFAIK websocket ping messages will not update HTTP session.
You can set up AbstractAjaxTimerBehavior or send pure JS HTTP request
to refresh the session
On Sat, Sep 16, 2017 at 7:34 PM, Manfred Bergmann
wrote:
>
> Hi,
>
> On Sat, Sep 16, 2017 at 1:32 PM, Manfred Bergmann
> w
Hi,
On Sat, Sep 16, 2017 at 1:32 PM, Manfred Bergmann
wrote:
> Found a different solution.
>
> Followed the advice here:
> https://issues.apache.org/jira/browse/WICKET-5453
>
> Where you can set the default idle timeout on the
> WebSocketServerContainerInitializer.
>
This is a good start!
Hi,
On Sat, Sep 16, 2017 at 1:32 PM, Manfred Bergmann
wrote:
> Found a different solution.
>
> Followed the advice here:
> https://issues.apache.org/jira/browse/WICKET-5453
>
> Where you can set the default idle timeout on the
> WebSocketServerContainerInitializer.
>
This is a good start!
But i
Found a different solution.
Followed the advice here:
https://issues.apache.org/jira/browse/WICKET-5453
Where you can set the default idle timeout on the
WebSocketServerContainerInitializer.
Manfred
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
--
you can add timeout behavior which will send ajax requests
these requests will refresh session
So far this is the only workaround i can propose
On Fri, Sep 15, 2017 at 11:53 PM, Manfred Bergmann
wrote:
> Hi.
>
> I'm not exactly certain how that helps me, except that the not yet released
> versio
Hi.
I'm not exactly certain how that helps me, except that the not yet released
version 7.8.1 fixes something regarding WebSockets. But I don't know if it's
that.
The thing is, that I have a one page application. Meaning the page itself
doesn't ever refresh. Only panels are reloaded here and ther
According to tomcat user list web socket activity does not touch session
You can set timeout ping behavior to touch the session
Here is the thread with my question according this
http://markmail.org/thread/g2ao4a4ytc3322b5
On Fri, Sep 15, 2017 at 10:05 PM, Bergmann Manfred
wrote:
> Hi.
>
> I’m h
Hi.
I’m having a problem with WebSocket timeouts.
One panel (currently) of a page uses a WebSocket to push data and re-render
something.
Leaving the browser untouched the WebSocket will timeout after 5 minutes:
—-
[ERROR] 2017-09-15 16:57:46.566 [Scheduler-1197176722]
org.apa.wic.pro.ws.jav.Wick
10 matches
Mail list logo