Hi Mark! it seems that this few tiny bits breaks the replication :)
With new behavior, you mean the behavior with Tomcat 7.0.22+? Why do we need an ServletFilter AND a Valve? Configuration via context/host etc. or web.xml is ofc ok! Regards, Thomas 2012/4/25 Mark Struberg <strub...@yahoo.de> > Hi, yes, I changed a bit, but really only a few tiny bits. > > Last week I also talked with Peter Roßbach who is on the Apache Tomcat > PMC. We went through the Servlet-3.0 spec and it seems that the new > behaviour is in sync with the spec! > > Which means we need to explore alternative ways to integrate the > FailoverService. I'd we provide a ServletFilter and a TomcatValve to > trigger it and completely remove the triggering of the > SessionContext->Session copying from the ServletListener at all. > > That would allow to integrate it either on server level or at least via > web.xml. > > wdyt? > > LieGrue, > strub > > > > ----- Original Message ----- > > From: Thomas Andraschko <zoi...@googlemail.com> > > To: dev@openwebbeans.apache.org > > Cc: > > Sent: Wednesday, April 25, 2012 10:59 AM > > Subject: Replication fails with OWB 1.1.4 > > > > Hi, > > > > weeks ago, i created an issue that OWB failover does not work anymore. > The > > issue was a compatiblity mismatch between MSM (memcached-session-manager) > > and Tomcat 7.0.21 or higher. > > Currently we stay with Tomcat 7.0.21 and our replication works fine. > > Today i upgraded to OWB 1.1.4 and our failover does not work again. > > > > Was anything changed in the failover logic between 1.1.3 and 1.1.4? > > > > Thanks, > > Thomas > > >
