On Dec 10, 2013, at 9:00 AM, "Spielmann, Simon" <simon.spielm...@capgemini.com> wrote:
> The main difference is, that session data is written to the database at the > end of every request. > The existing jdbc session manager does only support "lazy" writes into the > database, so if the app server crashes session data is not guaranteed written > to the database. > We did some load testing, but compared it only to a "in application session > persistence", which does in fact the same but did not reside in tomcat. > We tested it with oracle rac, other database should be possible. > Main feature is the support for sticky seasons and higher availability, > because sessions are in the database after every request (see above). > We have documented installation procedure (in German at the moment). > Translation to English would be possible. > Code is not public available at the moment. I could probably publish it when > general interest is there. If it's not too much trouble, could you share the code and docs? I'm interested enough to at least take a further look and give it a test run, assuming it's using the Apache license. Dan > > Simon > > -----Original Message----- > From: Daniel Mikusa [mailto:dmik...@gopivotal.com] > Sent: Dienstag, 10. Dezember 2013 14:19 > To: Tomcat Developers List > Subject: Re: New JDBC SessionManager for non sticky-sessions > > On Dec 10, 2013, at 6:34 AM, "Spielmann, Simon" > <simon.spielm...@capgemini.com> wrote: > >> Hello together, >> >> we developed a custom JDBC SessionManager which supports non sticky-sessions. >> Is there interest in including this in the official tomcat distribution? > > Can you tell us more? Some questions coming to mind… > > - What motivated you to develop this? > - How does it work? How does it integrate with Tomcat? > - Have you performance / load tested it? If so, with what results? > - What databases does it support? What tables does it need setup to work? > - What benefits does it offer other than not requiring sticky sessions? or > is that the main feature? > - Can I use it with sticky sessions or would that break it / defeat the > purpose? > - How is it different than using a persistent manager with JDBC based store? > > > https://tomcat.apache.org/tomcat-7.0-doc/config/manager.html#Nested_Components > > - Is the source posted some where? So anyone curious could try it out? > - Are there installation instructions? > > Dan > > >> >> Kind Regards >> Simon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org