https://bz.apache.org/bugzilla/show_bug.cgi?id=60623
--- Comment #12 from romain.manni-bucau <rmannibu...@gmail.com> --- Ok, if you have a listener observing before_init or before_start on Context (or even org.apache.catalina.core.StandardHost#addChild) you can initialize some context there, if you only deploy in this pool then you are safe to set and not unset the value there. I saw that several times in company integrations and I think it would be great to not break them. Also keep in mind 1 is the default. Regarding 0, you are right. For the story it means "auto number" from the available processors which is something I missed. Side note - unrelated to this ticket but still related to in context deployment: for the embedded case using tomcat.getHost().addChild(context) already deploys in current thread (that's what does Apache Meecrowave for instance). This also means org.apache.catalina.core.ContainerBase#initInternal could be lazy to avoid to create these useless threads. Thinking more about it I think a clean solution would to just pass an executor name like for connectors and just lookup the executor from the server.xml definitions. If you don't want that pool deployment tomcat can provide an InCallerThreadExecutor implementing Executor interface. wdyt? -- 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
