Summary: | Sticky sessions using PersistentManager enter indeterminate state on node failover | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | Chris Chandler <cchandler> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | P2 | ||
Version: | Nightly Build | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Attachments: |
Recommended patch
Additional strings for StringManager Modifications to JvmRouteBinderValve |
Description
Chris Chandler
2006-09-20 01:33:41 UTC
Created attachment 18890 [details]
Recommended patch
A slightly modified version of your patch has been applied to SVN and will be included in 5.5.21 onwards. Many thanks for the patch. Re-opening to change resolution type. As per the discussion on the dev list - http://marc.theaimsgroup.com/?t=116592092300008&r=1&w=2 - this patch will nto be commmitted. The JvmRouteBinderValve should provide the functionality you require in this case. Created attachment 19470 [details]
Additional strings for StringManager
Added an additional string for logging
Created attachment 19471 [details]
Modifications to JvmRouteBinderValve
Modifications made to JvmRouteBinderValve to make it agnostic of whether or not
in-memory clusting is being used.
Please reopen and investigate this bug. I have made the modifications to the JvmRouteBinderValve as per the discussion on the dev mailing list. My initial testing shows this valve now works as expected for JDBC clustering. Filip, what do you think about the patch as it is right now, for Tomcat 5.5 (not 6.0)? I have applied a modified fix to trunk and proposed it for 6.0.x and 5.5.x This has been applied to 6.0.x and 5.5.x and will be included in 6.0.21 and 5.5.28 onwards. |