https://bz.apache.org/bugzilla/show_bug.cgi?id=60623
--- Comment #8 from romain.manni-bucau <rmannibu...@gmail.com> --- Fact is tomcat kind of guarantee you execute code in a specific thread pool (far from any user pool or http pool to be concrete). So there is now a lot of code relying on deployment "initialization" setting there and not cleaning it (for good or bad reasons depending the listener implementation/hook). This is not an issue - assuming classes are coming from the "container" - since you are limited to this pool so it will be initialized each time and runtime will either not use that or get null and handle it (that's the 2 cases I'm aware of). Add to that #pool=1 is used to avoid concurrent deployments and uresing this value to change the deployment mode will break instances. Also just on a semantic point of view pool size = 1 sounds like a pool size is 1 and not 0 which correspond to "execute in context" no? -- 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
