On Wed, Feb 8, 2017 at 2:03 PM, Peter Henderson wrote:
> Thanks Martin,
>
> On 8 February 2017 at 10:45, Martin Grigorov wrote:
>
> > Hi,
> >
> > The WebSocket communication doesn't update the session, i.e. doesn't
> renew
> > it. This is by Servlet specification.
> > So if there is no normal HT
Thanks Martin,
On 8 February 2017 at 10:45, Martin Grigorov wrote:
> Hi,
>
> The WebSocket communication doesn't update the session, i.e. doesn't renew
> it. This is by Servlet specification.
> So if there is no normal HTTP request then the http session will expire and
> Wicket will clean up its
Hi,
The WebSocket communication doesn't update the session, i.e. doesn't renew
it. This is by Servlet specification.
So if there is no normal HTTP request then the http session will expire and
Wicket will clean up its resources.
Later when a web socket message comes it might fail with such kind of
Morning all.
Wicket 7.6.0
Tomcat 8.5.11
Java 1.8.0_121
I'm seeing several DiskDataStore Exceptions [1]. Normally towards the end
of the day, long after users have stopped using my app. So probably when
their sessions time out.
The file name looks very suspicious to me.
/opt/starjar/domains/cust
