all right :)
> Just to have the choice for other servlet engines. In Tomcat you will
most probably use the Valve. In other environments you can still use the
Filter. But you will probably never use both ;)
Ahh. Do you mean, ServletFilter will be called BEFORE session replication?
2012/4/25 Mark
> it seems that this few tiny bits breaks the replication :)
Well, I take the responsibility - will clean up the mess soon ;)
> With new behavior, you mean the behavior with Tomcat 7.0.22+?
Yes, seems this is because they 'fixed' the tomcat behaviour to match the
clarifications in the servlet
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
> Hi, yes, I change
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
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
