Am 23.10.2014 um 19:45 schrieb spr...@gmx.eu:
You may want to have a look at parallel deployment (
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html).
At the moment /Catalina/localhost/ is used as value in column app. It
is the
root app.
Would a war ROOT##2.war use another value?
No
> Well, I think it solves your problem. Old session-ids will
> get routed to
> the old version of your webapp and thus will be deserialized
> without a
> problem. New sessions will be created in the new version.
Yes, but the session persistence will go into the same table rows -> chrash
while
Am 23.10.2014 um 19:45 schrieb spr...@gmx.eu:
You may want to have a look at parallel deployment (
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html).
At the moment /Catalina/localhost/ is used as value in column app. It
is the
root app.
Would a war ROOT##2.war use another value?
No
> >> You may want to have a look at parallel deployment (
> >> http://tomcat.apache.org/tomcat-7.0-doc/config/context.html).
> >
> >
> >At the moment /Catalina/localhost/ is used as value in column app. It
> >is the
> >root app.
> >
> >Would a war ROOT##2.war use another value?
> No.
OK, then t
Am 23. Oktober 2014 13:34:22 MESZ, schrieb spr...@gmx.eu:
>> You may want to have a look at parallel deployment (
>> http://tomcat.apache.org/tomcat-7.0-doc/config/context.html).
>
>
>At the moment /Catalina/localhost/ is used as value in column app. It
>is the
>root app.
>
>Would a war ROOT##2.
> Are you using distributed sessions? If so, you'll have to override the
> internal serialization mechanism and do it all manually in a way that
> is going to be cross-version-compatible.
>
> It's not impossible, but it does take some planning and forethought.
OK; thought so.
Thank you.
---
> You may want to have a look at parallel deployment (
> http://tomcat.apache.org/tomcat-7.0-doc/config/context.html).
At the moment /Catalina/localhost/ is used as value in column app. It is the
root app.
Would a war ROOT##2.war use another value?
Am 22. Oktober 2014 21:20:12 MESZ, schrieb spr...@gmx.eu:
>Hi,
>
>when I deploy a new app version with incompatible serialization version
>of
>same classes I get:
>
>java.io.InvalidClassException:
>org.hibernate.collection.internal.AbstractPersistentCollection; local
...
>
>Is there something in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
To whom it may concern,
On 10/22/14 3:20 PM, spr...@gmx.eu wrote:
> when I deploy a new app version with incompatible serialization
> version of same classes I get:
>
> java.io.InvalidClassException:
> org.hibernate.collection.internal.AbstractPer
Hi,
when I deploy a new app version with incompatible serialization version of
same classes I get:
java.io.InvalidClassException:
org.hibernate.collection.internal.AbstractPersistentCollection; local class
incompatible: stream classdesc serialVersionUID = -8914173462748164853,
local class serialV
On 19/06/2014 06:14, Johanes Soetanto wrote:
> Is there some advice on how to debug our issues? or is there some obvious
> configuration issue that we have? Thanks for all the advice beforehand.
Check the system clocks on your production machines.
Add a session listener to log the stakctrace whe
Hi all,
We are having problem debugging our implementation of JDBCStore session
persistence. We followed guide from this post
http://www.intelligrape.com/blog/2010/07/21/tomcat-6-session-persistence-through-jdbcstore/
and it works in our local machine and our test servers. When we move it on
our
...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
anagers are based on ManagerBase too and they have to
option for synchronous replication, it should be possible with a central
session store (e.g. JdbcStore) too? But I cannot find the magic to replace
the async background processing with sync. processing... Any idea?
An alternative could be to use
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
languages since we are not fluent in those. Is that OK?
What should we do about the documentation for JDBCStore? Should we say that it
is deprecated and to use DataSourceStore instead? Or leave it and update the
documentation to talk about both?
If you are interested you can look at the prelimina
rsions. I just do
not see how all issues can be solved just by patching JDBCStore.
For such components the "support" is mostly a supervision. The bug
reports and patches are usually provided by those who are actually
using the component.
> #3 Sorry, I should have mentioned that we te
racker and submit a patch.
From: Konstantin Kolinko
To: Tomcat Users List
Sent: Tuesday, November 6, 2012 11:24 AM
Subject: Re: Thread starvation with JDBCStore
2012/11/5 ken dombeck :
> Occasionally when a user signs into our web site it is taking a very long
> time to create a session (10
Expires() to swap out sessions from memory and
> remove expired sessions from the database. The issue only appears when we
> have 10’s of thousands of sessions in memory/database.
>
> The problem is that even though StoreBase.processExpires() correctly releases
> the locks from
Badh, Tajvinder [mailto:tajvinder.b...@emc.com]
> Sent: 27 April 2011 11:19
> To: Reinwald Warapen; Tomcat Users List
> Subject: RE: JDBCStore Persistent Manager
>
> Hi,
>
> Thank you for the suggestions. I will take try it out and let you know how it
> goe
would need to be entered into this section
of the configuration?
Regards,
Taj
-Original Message-
From: Badh, Tajvinder [mailto:tajvinder.b...@emc.com]
Sent: 27 April 2011 11:19
To: Reinwald Warapen; Tomcat Users List
Subject: RE: JDBCStore Persistent Manager
Hi,
Thank you for the
Hi,
Thank you for the suggestions. I will take try it out and let you know how it
goes.
Regards,
Taj
-Original Message-
From: Reinwald Warapen [mailto:reinwal...@directi.com]
Sent: 27 April 2011 10:18
To: Tomcat Users List
Cc: Badh, Tajvinder
Subject: Re: JDBCStore Persistent Manager
e possible solution was to use the
Tomcat JDBCStore Persistent Mananger so that session information is held
centrally in a database.
This did not seem to work as intended as the minimum time to write session
details to the database was 10 seconds. This clearly did not solve the
problem as the users intera
the Amazon ELB. We are having difficulties in session
stickyness over HTTPS such that that requests are not being directed to the
same Tomcat instance, therefore creating a new session when the request is
directed to a different instance. One possible solution was to use the
Tomcat JDBCStore Persisten
is directed to a
different instance. One possible solution was to use the Tomcat JDBCStore
Persistent Mananger so that session information is held centrally in a database.
This did not seem to work as intended as the minimum time to write session
details to the database was 10 seconds. This
r users cannot be expected to
> tolerate interruptions (due to a failing server) then you'll /have/ to
> go with some kind of replication.
>
>> To be completely safe and sleep well, I would like to replicate the
>> sessions now, and in the mentioned document I read that it i
I read that it is
> possible using the PersistenceManager with JDBCStore.
Just note that this is probably the slowest of the 3 options presented
in the Replication HOWTO, since each session attribute will have to be
retrieved from the database every time. Option #3 (in-memory
replication) will probably be
-sessions, so
mostly the clients on the web stay on the same server. Mostly...
To be completely safe and sleep well, I would like to replicate the
sessions now,
and in the mentioned document I read that it is possible using the
PersistenceManager with JDBCStore.
My question now:
Is it enough to set up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerry,
On 4/15/2009 11:58 PM, jerrySheen wrote:
> So u mean to say, that if I were to prolong the JSESSIONID cookie's expiry
> time, the server would take care of repopulating the session state(stored in
> the db) even after a browser restart?
>
> We
this message in context:
http://www.nabble.com/retrieve-session-data-stored-in-db-using-JDBCStore.-tp23020556p23071047.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-uns
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerry,
On 4/13/2009 11:15 PM, jerrySheen wrote:
> As we are dealing with sessions that are no [longer accessible], this action
> would have no effect on any live sessions thus no inconsistencies.
>
>> if YES, please furnish some sample code or at lea
can someone please reply to the above post.:-((
--
View this message in context:
http://www.nabble.com/retrieve-session-data-stored-in-db-using-JDBCStore.-tp23020556p23052044.html
Sent from the Tomcat - User mailing list archive at Nabble.com
data to the new session.
thus i would be able to regain the last session state in which the browser
was closed. once the transaction is complete i would remove the old session
from the db.
Is this possible, if yes how?
--
View this message in context:
http://www.nabble.com/retrieve-session-data-st
jerrySheen wrote:
> Hi,
> I have been successful in saving the sessions to my mysql db, using the
> given code in my server configuration file.
>
>
> connectionURL="jdbc:mysql://X/xx?user=z&password=zz"
> driverName="com.mysql.jdbc.Driver"
> sessio
snapshot).
--
View this message in context:
http://www.nabble.com/retrieve-session-data-stored-in-db-using-JDBCStore.-tp23020556p23020556.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
, I'd appreciate it.
> Hi Eddie,
>
> I'm not sure if this would be possible with the default JDBCStore
> shipped with tomcat
> since the org.apache.catalina.session.JDBCStore is not considering
> usage of datasources
> which would certainly be a good plus, but maybe
Hi Eddie,
I'm not sure if this would be possible with the default JDBCStore
shipped with tomcat
since the org.apache.catalina.session.JDBCStore is not considering
usage of datasources
which would certainly be a good plus, but maybe there is a reason why
it is not in there.
if some one else
cifies db complete
> db info (user/pass/db/port/sid)-- I would like to know if I can
> specify a datasource specified in the server.xml instead, and how to
> specify it (if you could provide an example, that'd be great).
Unfortunately, JDBCStore does not support the use of DataSources. I
Hi,
I currently use deployment descriptor xml files to describe both the war file
to deployed and the session persistence info (configs+db info). Currently we
use a connectionURL that specifies db complete db info
(user/pass/db/port/sid)-- I would like to know if I can specify a datasourc
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
48 matches
Mail list logo
