https://bz.apache.org/bugzilla/show_bug.cgi?id=67927
--- Comment #11 from Michael Osipov <micha...@apache.org> --- (In reply to Mark Thomas from comment #10) > We need to allow in-progress usage of the old SSLContext to continue while > new requests get the new SSLContext. We don't want new requests to have to > wait for a long running request using the old SSLContext to complete. > > I agree we need some locking to make sure the 'current' SSLContext is > updated in a thread-safe manner but I wouldn't classify that as pausing all > requests. That looks to be in place on the Java side. Makes totally sense. Keeping at most two handles. > It is rather hacky but I often find, if I can reproduce the issue, a few > printf statements in the Native code can be very helpful. Had the same idea. Where you able to reproduce it already? -- 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
