https://bz.apache.org/bugzilla/show_bug.cgi?id=66660
Diego Rivera <diego.riv...@armedia.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #22 from Diego Rivera <diego.riv...@armedia.com> ---
(In reply to Diego Rivera from comment #21)
> <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"
> channelStartOptions="3"
> channelSendOptions="8">
Apparently those options attributes break the K8s stuff ... I removed them and
everything started ticking along quite happily. So at least there's that
avenue.
I also found this:
https://redisson.org/articles/redis-based-tomcat-session-management.html#:~:text=Redisson's%20Tomcat%20Session%20Manager%20allows,might%20serialize%20the%20whole%20session.
Using Redis as the session propagator may be a solid option instead, since I
can have a single Redis instance for all the tomcat components (yes, I have
different apps in the ecosystem which each require their own tomcat ... FML :(
).
But that's beyond the scope of this thread.
Also, I had a patch almost worked out until I realized that it would break
other stuff b/c of how the Member interface was conceived (i.e. with the
thought of a member's IP never changing).
For now, we can return to a RESOLVED status.
Sorry for the extra fuss ...
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
