must-revalidate,
no-store");
-Original Message-
From: Martijn Dashorst [mailto:martijn.dasho...@gmail.com]
Sent: Tuesday, June 21, 2011 11:27 AM
To: users@wicket.apache.org
Subject: Re: FW: Debugging page expired exception errors
For the TL;DR: check your cookies... Fun story follow
For the TL;DR: check your cookies... Fun story follows...
We just solved a strange bug in our own application where users were
logged out after a certain, but random amount of time, and where other
users reported being thrown out every 5 minutes.
We couldn't discover what happened, and after logg
if this was a load issue we would hear a ton of complaints on the list.
-igor
On Tue, Jun 21, 2011 at 5:37 AM, Brown, Berlin [GCG-PFS]
wrote:
> I posted this the other day, I think I have some more information.
>
> Is there a way to change the session secondlevel cache store and
> possibly the d
What do you think about older versions? 1.4 era.
I will try the load tests.
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Tuesday, June 21, 2011 8:40 AM
To: users@wicket.apache.org
Subject: Re: FW: Debugging page expired exception errors
we have a
we have a unit test that starts 20 threads which read and write
randomly and there is no problem.
DiskDataStoreTest (Wicket 1.5)
On Tue, Jun 21, 2011 at 3:37 PM, Brown, Berlin [GCG-PFS]
wrote:
> I posted this the other day, I think I have some more information.
>
> Is there a way to change the se
I posted this the other day, I think I have some more information.
Is there a way to change the session secondlevel cache store and
possibly the default disk store such that there aren't collissions
between file writes/reads.
I think in a high volume environment (lots of hits), I am getting thi