memory issue.
> > >
> >
> > Yeah, that's how it should be.
> >
> >
> > > Kalle, I still use AWS and thus far it's been very reasonable. I just
> > worry
> > > instances being held active and running my bill up because of sticky
>
to be the only two items effected by this, so I don't think
> > I'll have a memory issue.
> >
>
> Yeah, that's how it should be.
>
>
> > Kalle, I still use AWS and thus far it's been very reasonable. I just
> worry
> > instances being held act
t; >
>
> Yeah, that's how it should be.
>
>
> > Kalle, I still use AWS and thus far it's been very reasonable. I just
> worry
> > instances being held active and running my bill up because of sticky
> > sessions. I'll admit, I'm no expert in thi
#x27;t think
> I'll have a memory issue.
>
Yeah, that's how it should be.
> Kalle, I still use AWS and thus far it's been very reasonable. I just worry
> instances being held active and running my bill up because of sticky
> sessions. I'll admit, I'm no expert
s far it's been very reasonable. I just worry
instances being held active and running my bill up because of sticky
sessions. I'll admit, I'm no expert in this, so perhaps my understanding
isn't correct.
Is there any recommendation for the timeout? I currently have it set at 0.
On
to
> fix them, but at the cost of a sticky session. My application sits behind a
> load balancer, so my question is why do I need to use a sticky session and
> how do I avoid the use of them? I'm concerned with the fact this is going
> to cause a scaling dilemma.
>
I'd almos
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.
https://github.com/apache/tapestry-5/blob/master/tapestry-core/src/main/java/or
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 able to
fix them, but at the cost of a sticky session. My application sits behind a
loa
