Hi Chris, Its JSF version 2.2.1 What is a bytecode scanner? I will google that, I don't have any idea. And why did I start getting this problem a few days ago? The only thing that changed is Eclipse (I upgraded it to the latest) and the Tomcat that Eclipse uses to run the website everytime I run it when I'm developing.
I could upgrade JSF to some other version, but would that solve the issue? I don't know. And what if the few pages that I created using JSF will not work anymore because of the upgrade? I really totally forgot about how to use JSF, so I would not like having to learn it again now just because of this obstacle! Who is doing the class scanning? Is it JSF? Is it Tomcat? I have no clue right now. The interesting thing is that in my production server i didn't change anything in the software stack, but the WAR that now arrives there causes this problems. It is like if Eclipse is creating a new type of class/JAR files with some new characteristic, in my opinion. Thanks for your help!!! On Thu, Oct 12, 2023 at 4:35 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > Brian, > > On 10/12/23 16:55, Brian Braun wrote: > > Hello, > > > > First of all, I apologize if maybe my issue is not exclusively related to > > Tomcat, but I think it is. > > > > I started my website many years ago, using Struts 1.2.4 and since then I > > have been using it. Some years after that I had the intention to migrate > to > > JSF (version 2.2.X) and combine both frameworks for a while until I > > migrated everything to JSF and Struts was gone. I started learning it, > > created a few pages on my site but then I realized that it was not the > > ideal framework for me, so I stopped creating more pages with JSF and > > continued developing my site with Struts, letting those few JSF pages > that > > work coexist with the rest of the site running using Struts. Since then, > I > > haven't touched JSF. I haven't created even one page with it, never > > upgraded its version but the JSF JAR and pages are still there. Years > > passed and nothing made me think about JSF. > > > > Now I'm using: > > - Mac with the M2 chip > > - Eclipse (ARM version) > > - Tomcat, when developing with Eclipse > > - Tomcat 9.0.58 at my production server (which runs Ubuntu 22.04, x86/64) > > - Azul's Java 11.0.19+7-LTS aarch64, when developing with Eclipse > > - Java 11.0.20.1+1-post-Ubuntu-0ubuntu122.04, at the production server > > > > Well, a few days ago I upgraded Eclipse to Version: 2023-09 (4.29.0) and > at > > the same time upgraded to Azul's Java 11.0.19+7-LTS aarch64 and to Tomcat > > 9.0.71 when developing. And since then, I get these "SEVERE" JSF error > > messages (many of them) when I start Tomcat: > > > > SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool NN at position XX > > > > Why is that? Could someone please give me a clue? I just upgraded Eclipse > > and Tomcat, didn't do anything else relevant and now I get these > messages. > > And when I create the WAR file and deploy it on my production server, I > get > > the same error messages as well over there. It seems like the class files > > that gets generated are now different, since I didn't upgrade anything on > > my production server, so it is the WAR file that gets generated with > > something problematic now. > > > > Thanks in advance! > > > > Here is the complete stuff that Tomcat shows, as a reference: > > > > 12-Oct-2023 14:47:18.676 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server version > name: > > Apache Tomcat/9.0.71 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server built: Jan 9 > > 2023 22:33:01 UTC > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Server version > > number: 9.0.71.0 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log OS Name: Mac OS X > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log OS Version: 14.0 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Architecture: > aarch64 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Java Home: > > /Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log JVM Version: > > 11.0.19+7-LTS > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Azul > > Systems, Inc. > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: > > /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.678 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: > > /Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.719 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > > -Dcatalina.base=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.719 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > > -Dcatalina.home=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71 > > 12-Oct-2023 14:47:18.719 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > > -Dwtp.deploy=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/webapps > > 12-Oct-2023 14:47:18.719 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > > -Djava.util.logging.config.file=/Users/brianbraun/BB/ACME/Programacion-Mac-Silicon/EclipseTomcat9.0.71/conf/logging.properties > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: --add-opens=java.base/java.lang=ALL-UNNAMED > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: --add-opens=java.base/java.io=ALL-UNNAMED > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: --add-opens=java.base/java.util=ALL-UNNAMED > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: --add-opens=java.base/java.util.concurrent=ALL-UNNAMED > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Dfile.encoding=UTF-8 > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Dstdout.encoding=UTF-8 > > 12-Oct-2023 14:47:18.720 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Dstderr.encoding=UTF-8 > > 12-Oct-2023 14:47:18.848 INFO [main] > > org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler > > ["http-nio-80"] > > 12-Oct-2023 14:47:18.889 INFO [main] > > org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler > > ["https-jsse-nio-443"] > > 12-Oct-2023 14:47:19.099 INFO [main] > > org.apache.catalina.startup.Catalina.load Server initialization in [548] > > milliseconds > > 12-Oct-2023 14:47:19.122 INFO [main] > > org.apache.catalina.core.StandardService.startInternal Starting service > > [Catalina] > > 12-Oct-2023 14:47:19.123 INFO [main] > > org.apache.catalina.core.StandardEngine.startInternal Starting Servlet > > engine: [Apache Tomcat/9.0.71] > > 12-Oct-2023 14:47:19.685 INFO [main] > > org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was > scanned > > for TLDs yet contained no TLDs. Enable debug logging for this logger for > a > > complete list of JARs that were scanned but no TLDs were found in them. > > Skipping unneeded JARs during scanning can improve startup time and JSP > > compilation time. > > 12-Oct-2023 14:47:21.608 INFO [main] > > com.sun.faces.config.ConfigureListener.contextInitialized Initializing > > Mojarra 2.2.1 ( 20130709-1453 > > https://svn.java.net/svn/mojarra~svn/tags/2.2.1@12065) for context > > '/VistaControlador' > > 12-Oct-2023 14:47:21.674 INFO [main] > > com.sun.faces.spi.InjectionProviderFactory.createInstance JSF1048: > > PostConstruct/PreDestroy annotations present. ManagedBeans methods marked > > with these annotations will have said annotations processed. > > 12-Oct-2023 14:47:21.680 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 18 at position 35 > > 12-Oct-2023 14:47:21.680 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 0 at position 36 > > 12-Oct-2023 14:47:21.680 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 0 at position 37 > > 12-Oct-2023 14:47:21.680 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 0 at position 38 > > 12-Oct-2023 14:47:21.681 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 36 at position 39 > > 12-Oct-2023 14:47:21.681 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 18 at position 86 > > ......... more of these severe errors......... > > 12-Oct-2023 14:47:21.681 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 18 at position 89 > > 12-Oct-2023 14:47:21.681 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 0 at position 90 > > 12-Oct-2023 14:47:21.681 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 37 at position 92 > > 12-Oct-2023 14:47:21.682 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 0 at position 93 > > 12-Oct-2023 14:47:21.682 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 90 at position 94 > > 12-Oct-2023 14:47:21.682 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 18 at position 96 > > 12-Oct-2023 14:47:21.682 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 0 at position 97 > > 12-Oct-2023 14:47:21.682 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 93 at position 99 > > 12-Oct-2023 14:47:21.682 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 18 at position 125 > > 12-Oct-2023 14:47:21.683 SEVERE [main] > > > com.sun.faces.config.JavaClassScanningAnnotationScanner$ConstantPoolInfo.containsAnnotation > > Unknow type constant pool 0 at position 126 > > This kind of thing usually happens when the bytecode scanner is older > than the files it is scanning. Things get added to the class file format > over time and if your class-scanner is old, it may complain there are > things there it does not understand. > > How old is your version of JSF? You may need to upgrade it in order to > avoid those warnings. You may also be able to disable class-file > scanning if you don't use the annotations for anything. I can't tell you > if you can do that, because I don't know anything about (a) your > application and (b) JSF. You could try disabling it and see if your > application still works. > > Hope that helps, > -chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
