https://bz.apache.org/bugzilla/show_bug.cgi?id=60623
--- Comment #13 from romain.manni-bucau <rmannibu...@gmail.com> --- side note: to speak about well known frameworks affected by that, log4j2 can lead to the mentionned issue when added to the container since it sets a threadlocal in initialzer or context listener and reset it in a servlet (intended to be load on startup 1). Goal being to be initialized for the whole startup duration but if another filter fails then it is not resetted. While tomcat uses a pool this is not a big deal but when it will start to use the caller thread it can fail where it was previously ok. See log4j-web for the detail. -- 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
