If I understand the discussion correctly it is being suggested that we attempt using the JvmRouteBinderValve for the same functionality provided in the originally submitted patch. I believe the problem we ran into was the JvmRouteBinderValve assumes that we are using the SimpleTcpCluster implementation, when we're actually using the JDBC persistence manager for replication. It's entirely possible I am missing something, but it doesn't appear the JvmRouteBinderValve solves this particular problem.
Chris -------- Original Message -------- Subject: Re: svn commit: r486005 - in /tomcat/container/tc5.5.x: catalina/src/share/org/apache/catalina/connector/Request.java catalina/src/share/org/apache/catalina/session/PersistentManagerBase.java webapps/docs/changelog.xml From: "Mark Thomas" <[EMAIL PROTECTED]> Date: Wed, December 13, 2006 5:55 am To: Tomcat Developers List <dev@tomcat.apache.org> Filip Hanik - Dev Lists wrote: > Rainer Jung wrote: >> My impression now is, that we should backout the commit and the user >> should instead first try to use the existing Valve as described by Peter. > I agree, > Filip That sounds like the right way forward to me. I'll revert my commit later today. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
