Thread: At least one JAR was scanned for TLDs yet contained no TLDs

I have an application which runs perfectly in WebSphere 6.1 using JDK6 but now I want to publish it to Tomcat8 using JDK8. It is a simple application which is based on some JSP and some servlets. I was able to deploy it to Tomcat8 eithier from my STS or by creating a war file an publishing this war from admin console. But I can't access this application. There is no error in my console output and every dependency I have fix it. I have no idea what can be the root cause. The only message I saw it the one pasted in the title. I change to FINE the four lines in logging.properties but it didn't help to see any clear message. Any suggestion that help me at least to know where to check will be very appreciatted.

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = FINE
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].level = FINE
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].level = FINE
org.apache.jasper.compiler.TldLocationsCache.level = FINE

Oct 08, 2014 3:08:29 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor C:\STS\apache-tomcat-8.0.14\conf\Catalina\localhost\my_aplication2.xml
Oct 08, 2014 3:08:29 PM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.j2ee.server:my_aplication' did not find a matching property.
Oct 08, 2014 3:08:30 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: 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.
Oct 08, 2014 3:08:30 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deployment of configuration descriptor C:\STS\apache-tomcat-8.0.14\conf\Catalina\localhost\my_aplication2.xml has finished in 873 ms

Thread moved.

I don't know that you've given enough detail to help you. Have you tried increasing the logging level or looking at the existing logs to determine where the failure is occurring?

Yes, I even pointed the catalina.out to some txt file to analyse every lines. What extra details do you suggest me to place here?

If I were you, this is what I'd be thinking:

My program - some piece of it - is looking for something. It checked every .jar file looking for it. (Every .jar file on the classpath, or some .jars?) Why is it looking for that thing? (Why is it needed? Where is it needed? Did I make some change to cause it? Am I doing something differently in this program than I've done before?) Should it be looking for that thing? (Have I made a mistake in my code to cause it to look for something it doesn't need? Have I neglected to add a resource to the build path that the program needs?) If I change my code so that it's not looking for that thing, is something broken?

And because I'm curious, I could probably think of several more questions, but you get the idea. I can't answer any of those questions with what you've given us, but we shouldn't be asking and answering the questions, anyway. That's your job.

Greg, thank you.
In few words I didn't change anything in my code. The only thing I did was coping the project folder from Eclipse (IBM RAD) which has Websphere6.1 and JDK6 and import in other Eclipse (Spring Tools Suite) and added Tomcat8 and JDK8. I had checked and every dependency is fine and there isn't any conflict complaint in Eclipse about missing anything. But I am getting the info message "At least one JAR was scanned for TLDs yet contained no TLDs" when compiling. If you were getting this info, how would you go deeper in the analysis? I changed the above INFO to FINE in logging.properties but it doesn't improve the details. Basically, because I can't even access via Browser (only getting 404) and not getting any more suggestive error it is hard to think for any possible problem.