Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of dmikusa@gopivotal.com
 designates 209.85.216.42 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: PersistentManager + JdbcStore
From: Daniel Mikusa <dmikusa@gopivotal.com>
In-Reply-To: <D6CD444703CE4618993E21307F05FD01@msrvcn04>
Date: Fri, 8 Nov 2013 14:34:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <00AC90DF-13AE-4369-BDE0-AE3227DA3035@gopivotal.com>
References: <D6CD444703CE4618993E21307F05FD01@msrvcn04>
To: "Tomcat Users List" <users@tomcat.apache.org>

On Nov 8, 2013, at 2:14 PM, spring@gmx.eu wrote:

> Hi,
>=20
> is it possible to use the PersistentManager + JdbcStore to enable a =
100%
> failover/cluster solution for sessions?

You could, but I'm not sure that's it's intended purpose.  As I =
understand it, the PersistentManager is for pushing session data that =
hasn't been used in a while out of memory, thus allow a Tomcat server to =
handle more sessions with less memory.

> As far as I can see not, because the session data is written async =
into the
> database and only in a min. interval of 1 s.
> Is this right?

This is my understanding as well.  Sessions are persisted to the =
database periodically instead of on-demand.  If you need sessions =
replicated as changes occur then you'll want to look at a different =
solution, like the built-in cluster support.

Dan

>=20
> Thank you
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org