0

To speed up tomcat startup, I usually configure (dramatic effect):

tomcat.util.scan.StandardJarScanFilter.jarsToSkip=*.jar
tomcat.util.scan.StandardJarScanFilter.jarsToScan=myapp.jar

But skipping everything breaks Vaadin 11. I tried

tomcat.util.scan.StandardJarScanFilter.jarsToScan=myapp.jar,vaadin*.jar

Which jars do I have to scan so that Vaadin 11 can work / startup correctly?

aurelius
  • 3,946
  • 7
  • 40
  • 73
Reto Höhener
  • 5,419
  • 4
  • 39
  • 79
  • 1
    have you tried with `flow-server-*.jar`? – cfrick Nov 17 '18 at 18:38
  • @cfrick Yes thank you! That seems to work. Feel free to convert to an answer. Currently I am using `jarsToSkip=*.jar` and `jarsToScan=myapp.jar,vaadin*.jar,flow*.jar` – Reto Höhener Nov 19 '18 at 20:34
  • That is the answer you have deleted. Why not undelete it? And is `flow-server` alone not enough? – cfrick Nov 19 '18 at 20:40
  • @cfrick I deleted my answer because after some testing I initially thought that it didn't work after all (still not 100% convinced). And in addition it would have allowed me to show my appreciation for your looking into it. – Reto Höhener Nov 21 '18 at 10:49

1 Answers1

1
tomcat.util.scan.StandardJarScanFilter.jarsToSkip=*.jar
tomcat.util.scan.StandardJarScanFilter.jarsToScan=myapp.jar,vaadin*.jar,flow*.jar,polymer*.jar,iron*.jar,shady*.jar

Seems to work so far, although I am a bit uneasy about possible other things that might be needed. e.g. polymer*.jar. So now when I run into weird problems, first thing I do is change it back to scan everything, to rule out that possible cause.

Edit: Already had to adjust the list.

Reto Höhener
  • 5,419
  • 4
  • 39
  • 79