George - sounds like those components might be using session persistence
for some of their data (e.g. in the case of Grid it uses @Persist , which
defaults to session persistence, to store the GridPaginationModel - e.g.
On Thu, Dec 4, 2014 at 5:54 AM, George Christman gchrist...@cardaddy.com
wrote:
Hi guys, so I've had a slew of strange behaviors over the past few months
with a few different Tapestry components such as Tapestry Grid, Tapestry
Captcha, and writting/removing cookies. Last night I was finally
I'd have to say 98% of my app is stateless, I only have a few admin pages
that still use tapestry grid. Other than that Captcha and Tapestry Security
redirect seem to be the only two items effected by this, so I don't think
I'll have a memory issue.
Kalle, I still use AWS and thus far it's been
On Thu, Dec 4, 2014 at 12:08 PM, George Christman gchrist...@cardaddy.com
wrote:
I'd have to say 98% of my app is stateless, I only have a few admin pages
that still use tapestry grid. Other than that Captcha and Tapestry Security
redirect seem to be the only two items effected by this, so I
I have a URL persist I wrote to solve this problem. It moves the grids data
from the session into URL parameters.
I'll post the code later today
On Thursday, December 4, 2014, Kalle Korhonen kalle.o.korho...@gmail.com
wrote:
On Thu, Dec 4, 2014 at 12:08 PM, George Christman
Well before I had it disabled with the load balancer which was causing the
issues. It seemed to fix things when I activated it, but it had a default
time of 0. I'll change it to 5mins for now and if I didn't etend it via
async, what would happen?
On Thu, Dec 4, 2014 at 3:41 PM, Kalle Korhonen
On Thu, Dec 4, 2014 at 4:43 PM, George Christman gchrist...@cardaddy.com
wrote:
Well before I had it disabled with the load balancer which was causing the
issues. It seemed to fix things when I activated it, but it had a default
time of 0. I'll change it to 5mins for now and if I didn't etend
