...Gracias
> Date: Sat, 9 Nov 2013 16:07:42 -0300
> Subject: Re: PersistentManager + JdbcStore
> From: jbig1...@gmail.com
> To: users@tomcat.apache.org
>
> Thanks for this post, but the problem that I have is uncertain. My
> application is Java Web and creates a session f
Thanks for this post, but the problem that I have is uncertain. My
application is Java Web and creates a session for the user in Tomcat
(version apache-tomcat-7.0.29) and an unusual one user captures the user
session without finding an explanation.
Could you help me or tell me who to contact to fi
> Given some method of automatic discovery, other than
> multicast, it sounds like you could still use Tomcat's
> clustering support. So perhaps you could write your own
> membership service?
Yes, I think with Jgroups + S3 ping this could be solved.
But since both ClusterManagers are based o
On Nov 9, 2013, at 8:42 AM, spr...@gmx.eu wrote:
I think I will fix the DynamoDB-Sessionmanager.
>>>
>>> Also an option.
>>
>> Already in process it seems ;)
>>
>> https://github.com/aws/aws-dynamodb-session-tomcat/issues/3
>>
>> I hope they will use the code from tomcat for managing th
> > > I think I will fix the DynamoDB-Sessionmanager.
> >
> > Also an option.
>
> Already in process it seems ;)
>
> https://github.com/aws/aws-dynamodb-session-tomcat/issues/3
>
> I hope they will use the code from tomcat for managing the classloader
> issues.
Well, just realized that this
On 09/11/2013 6:41 AM, wrote:
>
> > If you need
> > sessions replicated as changes occur then you'll want to look
> > at a different solution, like the built-in cluster support.
>
> Unfortunately it does not work on AWS, no multicast.
>
Cant you use static membership instead mcast?
> I think I wi
> Multicast is not a requirement, that just defines how Tomcat
> nodes will locate each other. Since multicast is not
> available for you, you could statically list your Tomcat
> nodes in your configuration.
>
>
> https://tomcat.apache.org/tomcat-7.0-doc/config/cluster-interc
> eptor.html#
On Nov 8, 2013, at 2:41 PM, wrote:
>> If you need
>> sessions replicated as changes occur then you'll want to look
>> at a different solution, like the built-in cluster support.
>
> Unfortunately it does not work on AWS, no multicast.
Multicast is not a requirement, that just defines how Tomc
> If you need
> sessions replicated as changes occur then you'll want to look
> at a different solution, like the built-in cluster support.
Unfortunately it does not work on AWS, no multicast.
I think I will fix the DynamoDB-Sessionmanager.
Thank you
-
On Nov 8, 2013, at 2:14 PM, spr...@gmx.eu wrote:
> Hi,
>
> 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 Persi
Hi,
is it possible to use the PersistentManager + JdbcStore to enable a 100%
failover/cluster solution for sessions?
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?
Thank you
Greetings, all
I might be completely off track (hope not!), but I am trying to achieve
session replication by using JDBCStore and PersistentManager with a shared
database.
I noticed that the sessions are not persisted in database until I stop the
application (or stop Tomcat) and this is a problem
12 matches
Mail list logo
