Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change
notification.
The "HowTo/FasterStartUp" page has been changed by markt:
https://wiki.apache.org/tomcat/HowTo/FasterStartUp?action=diff&rev1=26&rev2=27
Comment:
Complete some TODOs
There exists an attribute on `Context` element, `containerSciFilter`. It can
be used to disable container-provided features that are plugged into Tomcat via
SCI API: !WebSocket support (in Tomcat 7 and later), JSP support (in Tomcat 8
and later).
- The class names to filter can be detected by looking into
`META-INF/services/javax.servlet.ServletContainerInitializer` files in Tomcat
JARs. For !WebSocket support the name is
`org.apache.tomcat.websocket.server.WsSci`, for JSP support the name is
`org.apache.jasper.servlet.JasperInitializer`.
+ The class names to filter can be detected by looking into
`META-INF/services/javax.servlet.ServletContainerInitializer` files in Tomcat
JARs. For !WebSocket support the name is
`org.apache.tomcat.websocket.server.WsSci`, for JSP support the name is
`org.apache.jasper.servlet.JasperInitializer`. e.g.:
+ {{{
+
+ }}}
+ The impact of disabling WebSocket support will depend on how many JARs were
being scanned for WebSocket annotations and whether any other SCIs trigger
annotation scans. Generally, it is the first SCI scan that has the biggest
performance impact. The impact of additional scans is minimal.
- ''TODO: Configuration example''
-
- ''TODO: How much faster does it make it? In short: Delays due to annotation
scanning caused by !WebSocket have been already mentioned in another paragraphs
on this page. This is an alternative to removing websocket JARs from Tomcat
installation.''
References: [[https://bz.apache.org/bugzilla/show_bug.cgi?id=55855|Bug
55855]], [[http://tomcat.apache.org/tomcat-8.0-doc/config/context.html|Tomcat 8
Context documentation]]
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
