TLD jar scanning at Tomcat Startup
Good Evening, Tomcat 9.082 on Windows 11. Tomcat runs as a Windows service. When I start Tomcat and deploy my war file, it hangs at the following in the Catalina Log: 06-Nov-2023 15:21:59.819 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. I see nothing in stderr or stdout I have enabled the logging in logging.properties # To see debug messages in TldLocationsCache, uncomment the following line: org.apache.jasper.compiler.TldLocationsCache.level = FINE I have also edited the default list of jars to scan as below: # Default list of JAR files that should be scanned that overrides the default # jarsToSkip list above. This is typically used to include a specific JAR that # has been excluded by a broad file name pattern in the jarsToSkip list. # The list of JARs to scan may be over-ridden at a Context level for individual # scan types by configuring a JarScanner with a nested JarScanFilter. tomcat.util.scan.StandardJarScanFilter.jarsToScan=\ log4j-taglib*.jar,\ log4j-web*.jar,\ log4javascript*.jar,\ slf4j-taglib*.jar,\ jstl-1.2.jar,\ CKFinder-2.3.1.jar, \ sitemesh-2.4.2.jar, \ ckeditor-java-core-3.5.3.jar, \ spring-security-taglibs-4.0.3.RELEASE.jar It is my understanding that the jarsToScan overrides the jarsToSkip. I believe I have no override in my app context war file. I am not seeing the intended behavior of the jar scanning and the tomcat server never deploys the single war file. Eventually the server encounters an OOM state and crashes. Am I configuring something incorrectly? Thanks Charlie D
FW: question on clustering Tomcat 7.0
I have two tomcat instances on 1 machine, each with a different AJP connector port and manager application port. I have Apache webserver for load balancing. When I undeploy my web app from one of the tomcat instances, it does not fail over to the other tomcat in the cluster and I get a 404 error. I am using a Simple TCP cluster. I have attached my server.xml. Can someone please tell me what I am missing? Thanks Charlie - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
a question on tomcat failover
I have 2 instances of Tomcat 7.0 on the same host with two manager apps (different ports) and two AJP connectors On different ports. Apache 2.4 is providing the load balancing and when I stop one instance of Tomcat, it fails over To the other instance. My question is should I have to stop one instance of the Tomcat server to fail over or can I simply just Stop the application in one instance using the Tomcat manager ( or undeploy for that matter)? If I have to stop the Tomcat Instance completely would I just install the new war file to that instance and restart with auto deploy? And then repeat this Procedure on the other node? Thanks in advance Charlie
RE: App Initialization Order In Tomcat
-Original Message- From: Jose H. Martinez [mailto:josehmartin...@gmail.com] Sent: Wednesday, November 07, 2012 6:23 PM To: users@tomcat.apache.org Subject: App Initialization Order In Tomcat I am running two applications under tomcat. One application is a web service and the other is a web app that depends on the web service to be started first before it can be initialized. The problem I am having is that the web app is starting before the web service an is causing it to hang waiting for the service to be started. Is there a way to tell tomcat the order in which the war files should be deployed so that the web service gets deployed first and then the web app? Note: In the future we will deploy the applications on different servers but for now that's not an option. I'm running tomcat 7.0.29. Thanks. Your help is very much appreciated. Make the web service war filename be alphabetically before the second application war fileEg alpha.war is the web service and beta.war is the dependant application. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
