-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amit,
On 3/2/2009 9:58 PM, Amit Chandel wrote:
> I would love to see an example of such a filter.
All you need to do is wrap the HttpSession object with one that does
your database access. Something like the filter below. There are a few
things missi
Hi Chris,
I would love to see an example of such a filter.
Thanks,
Amit
On Mon, Mar 2, 2009 at 5:43 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Amit,
>
> On 3/2/2009 4:21 PM, Amit Chandel wrote:
>> But only issue is that Tomcat doesn't persist sessions t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amit,
On 3/2/2009 4:21 PM, Amit Chandel wrote:
> But only issue is that Tomcat doesn't persist sessions to DB
> synchronously as is the case with in-memory replication where session
> data is first replicated and then the request gets served. So if
>
Hi Chris,
Thanks for bringing up these concerns.
I did a more detailed analysis of our application. Though it keeps 5GB
of session data in RAM which are actually disk backed, the active
session data will only account for a maximum of 200MB per second. So I
am only required to persist this much da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amit,
On 2/28/2009 9:02 PM, Amit Chandel wrote:
> I am trying to deploy a tomcat cluster. I was able to set up a test
> tomcat cluster using in-memory replication with version 6.0.10, but my
> session data is too much (almost 5 GB per tomcat instance,
Hi Group,
I am trying to deploy a tomcat cluster. I was able to set up a test
tomcat cluster using in-memory replication with version 6.0.10, but my
session data is too much (almost 5 GB per tomcat instance, and using 2
nodes in cluster both instances will require 10GB of RAM to hold
session data)
