404 with Tomcat Local server

[Jan Kaczmarek]

Hello,"
I have got question-why when Im trying to enter "http://localhost:8082/test" or (im not sure which should I use-I think the first one is correct cause I made only /test endpoint) "http://localhost:8082/app_war_exploded/test"  I have got 404?
Configuration class: https://hastebin.com/ocosebogod.kotlin
ApiHello class (my @RestController) : https://hastebin.com/etugoqutop.kotlin
pom.xml https://hastebin.com/avukoxijev.xml
Im using Tomcat Local, I set server at http port 8082, jmx port 1098, I added exploded app:war to deployment, it should work but its not.

[Tim Holloway]

If you are using Tomcat's default deployment mechanism, you would copy your WAR to TOMCAT_HOME/webapps/. You do not actually have to explode WAR files. Tomcat will do that as part of the deployment.

If you have a WAR file mywebapp.war, exploded to TOMCAT_HOME/webapps/mywebapp, then the URL for its /index.jsp page would be: http://localhost:8082/mywebapp/index.jsp.

If you do this and still get a "404" check the Tomcat logs to make sure that there was no error in deploying the webapp.

[Jan Kaczmarek]

Tim Holloway wrote:If you are using Tomcat's default deployment mechanism, you would copy your WAR to TOMCAT_HOME/webapps/. You do not actually have to explode WAR files. Tomcat will do that as part of the deployment.

If you have a WAR file mywebapp.war, exploded to TOMCAT_HOME/webapps/mywebapp, then the URL for its /index.jsp page would be: http://localhost:8082/mywebapp/index.jsp.

If you do this and still get a "404" check the Tomcat logs to make sure that there was no error in deploying the webapp.

So i checked in Tomcat Manager and app is deployed. In Tomcat adres /webapps there is nothing about this app.
Tomcat logs from deploying (Edit)  
Connected to server [2020-11-20 06:42:21,572] Artifact app:war exploded: Artifact is being deployed, please wait... 20-Nov-2020 18:42:23.740 INFO [RMI TCP Connection(3)-127.0.0.1] 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. 18:42:23.979 [RMI TCP Connection(3)-127.0.0.1] DEBUG app.Config - No ContextLoaderListener registered, as createRootApplicationContext() did not return an application context 18:42:24.070 [RMI TCP Connection(3)-127.0.0.1] INFO org.springframework.web.servlet.DispatcherServlet - Initializing Servlet 'dispatcher' 18:42:24.111 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.web.context.support.AnnotationConfigWebApplicationContext - Refreshing WebApplicationContext for namespace 'dispatcher-servlet' 18:42:24.248 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Creating shared instance of singleton bean 'org.springframework.context.annotation.internalConfigurationAnnotationProcessor' 18:42:24.289 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Creating shared instance of singleton bean 'org.springframework.context.event.internalEventListenerProcessor' 18:42:24.292 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Creating shared instance of singleton bean 'org.springframework.context.event.internalEventListenerFactory' 18:42:24.293 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Creating shared instance of singleton bean 'org.springframework.context.annotation.internalAutowiredAnnotationProcessor' 18:42:24.298 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.beans.factory.support.DefaultListableBeanFactory - Creating shared instance of singleton bean 'org.springframework.context.annotation.internalCommonAnnotationProcessor' 18:42:24.314 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.ui.context.support.UiApplicationContextUtils - Unable to locate ThemeSource with name 'themeSource': using default [org.springframework.ui.context.support.ResourceBundleThemeSource@341d528e] 18:42:24.876 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter - ControllerAdvice beans: none 18:42:24.959 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver - ControllerAdvice beans: none 18:42:24.990 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.jndi.JndiTemplate - Looking up JNDI object with name [java:comp/env/spring.liveBeansView.mbeanDomain] 18:42:24.991 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.jndi.JndiLocatorDelegate - Converted JNDI name [java:comp/env/spring.liveBeansView.mbeanDomain] not found - trying original name [spring.liveBeansView.mbeanDomain]. javax.naming.NameNotFoundException: Name [spring.liveBeansView.mbeanDomain] is not bound in this Context. Unable to find [spring.liveBeansView.mbeanDomain]. 18:42:24.991 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.jndi.JndiTemplate - Looking up JNDI object with name [spring.liveBeansView.mbeanDomain] 18:42:24.992 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.jndi.JndiPropertySource - JNDI lookup for name [spring.liveBeansView.mbeanDomain] threw NamingException with message: Name [spring.liveBeansView.mbeanDomain] is not bound in this Context. Unable to find [spring.liveBeansView.mbeanDomain].. Returning null. 18:42:25.005 [RMI TCP Connection(3)-127.0.0.1] DEBUG org.springframework.web.servlet.DispatcherServlet - enableLoggingRequestDetails='false': request parameters and headers will be masked to prevent unsafe logging of potentially sensitive data 18:42:25.005 [RMI TCP Connection(3)-127.0.0.1] INFO org.springframework.web.servlet.DispatcherServlet - Completed initialization in 935 ms [2020-11-20 06:42:25,030] Artifact app:war exploded: Artifact is deployed successfully [2020-11-20 06:42:25,030] Artifact app:war exploded: Deploy took 3,458 milliseconds 20-Nov-2020 18:42:31.379 INFO [Catalina-utility-2] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\manager] 20-Nov-2020 18:42:31.428 INFO [Catalina-utility-2] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\manager] has finished in [49] ms
Im not sure if I understand it right but I think Im missing something in Spring configuration

[Tim Holloway]

Generally we'd prefer that you paste in your log info in code tags on this site rather than having them as an off-site reference. It helps other people that may have the same problem and reduces the likelihood that the log info might get taken down before thay can read it.

As near as I can tell, the only webapp that Tomcat deployed was the "manager" app, and not your own app. That's less likely to be a Spring problem as it is that your "WAR" wasn't recognized as a WAR. If you just throw stuff under TOMCAT_HOME/webapps and it isn't conformant with the specifications for a WAR in the JEE standards doc, Tomcat will just ignore it.

I am, incidentally, referring to stand-alone Tomcat webapps. If you're using Spring Boot then things operate a little differently.

[Jan Kaczmarek]

Ok, I edited my post and added code directly.
So this is my app manager at this localhost and it showing that "something" is deployed (I added this as a attachment to be sure its not going to vanish)
I manually created WAR file, it was automatically added to webapps folder. Im trying to access to http://localhost:8082/app-1.0-SNAPSHOT with index.jsp, without it, with /test etc and still throwing 404

[Ron McLeod]

Code and configuration files referenced in the original post ...


Configuration class:

package app;

import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;
import org.springframework.web.servlet.support.AbstractAnnotationConfigDispatcherServletInitializer;

@Configuration
@ComponentScan("app")
public class Config extends AbstractAnnotationConfigDispatcherServletInitializer {
    @Override
    protected Class<?>[] getRootConfigClasses() {
        return new Class[0];
    }

    @Override
    protected Class<?>[] getServletConfigClasses() {
        return new Class[0];
    }

    @Override
    protected String[] getServletMappings() {
        return new String[0];
    }
}

ApiHello class (my @RestController):

package app;

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class ApiHello {

    @GetMapping("/test")
    public String test(){
        return "test";
    }
}

pom.xml:<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0"         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">    <modelVersion>4.0.0</modelVersion>    <groupId>groupId</groupId>    <artifactId>app</artifactId>    <version>1.0-SNAPSHOT</version>    <packaging>war</packaging>    <properties>        <maven.compiler.source>14</maven.compiler.source>        <maven.compiler.target>14</maven.compiler.target>        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>    </properties>    <dependencies>        <dependency>            <groupId>javax.servlet</groupId>            <artifactId>javax.servlet-api</artifactId>            <version>4.0.1</version>            <scope>provided</scope>        </dependency>        <dependency>            <groupId>org.springframework</groupId>            <artifactId>spring-web</artifactId>            <version>5.3.1</version>        </dependency>        <dependency>            <groupId>org.projectlombok</groupId>            <artifactId>lombok</artifactId>            <version>1.18.16</version>            <scope>provided</scope>        </dependency>        <dependency>            <groupId>org.springframework.boot</groupId>            <artifactId>spring-boot-starter-web</artifactId>            <version>2.4.0</version>        </dependency>    </dependencies> </project>

[Himai Minh]

I believe in IntelliJ, you can change the context path to anything you want.
Here is a reference:
https://mkyong.com/intellij/intellij-idea-run-debug-web-application-on-tomcat/

You can see from section 3.2 of  this reference . You can set localhost:8080/ for starting up the app.

[Tim Holloway]

Himai Minh wrote:I believe in IntelliJ, you can change the context path to anything you want.
Here is a reference:
https://mkyong.com/intellij/intellij-idea-run-debug-web-application-on-tomcat/

You can see from section 3.2 of  this reference . You can set localhost:8080/ for starting up the app.

That only works for IntelliJ. IntelliJ is simply deploying the IntelliJ web project according to Tomcat's rules.


The admin webapp shows that there are 3 webapps (Applications) deployed in that Tomcat server:

* The /admin webapp
* The /app_exploded webapp
* The /app-1.0-SNAPSHOT webapp

Those last 2 apps do not show in the catalina.out log sample you posted, so I have to assume that the log sample was incomplete, possibly taken before the other 2 apps deployed.

Note that the Application context paths in the admin page are all hyperlinks. Clicking on them should take you to the welcome page defined in web.xml. If no welcome page was defined, then you should get a directory listing of the root directory in the WAR.

[Jan Kaczmarek]

Yes, these two new webapps are result of manual addition of WAR to Tomcat server+Intellij deployment.
Hmm to be honest-I don't have got web.xml file in my project. I thought when I use annotations I don't need a web.xml file-so it looks like im wrong.
I just created it and now I need to fill it with something ( I will find some reasonably correct tutorial )-I hope this one is going to work, Im not ready for 3rd day with this problem.

[Tim Holloway]

You only need web.xml in 2 situations.

1. You need to configure a webapp with a parameter(s) that aren't supported by annotations. Such as stuff that doesn't fit into any of the class files. That might include the welcome page definition, though I'm not sure.

2. You need to override an annotation. This might happen if you're using a re-usable component whose default annotation value isn't what you want.

I use the term "web.xml" because before annotations web.xml was the sole place to setup server-independent deployment info. These days, there's a "virtual" web.xml that's build by assembling all the web-related annotations, reading and applying an actual web.xml file if it exists, and working with the composite result, so it's just easier to call all of it "web.xml". Technically, it's the "server-independent deployment descriptor" just as the Context XML element is Tomcat's "server-dependent deployment descriptor".

[Jan Kaczmarek]

If someone else may have same problem-I just solved it. It was all about configuration in Config class.
I left getServletMappings() and getServletConfigClasses() with default, empty implementation. To make it works I just had to add "/" for servlet mapping and  point class with configuration. Thank you for all advice and help!  

package app;

import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;
import org.springframework.web.servlet.support.AbstractAnnotationConfigDispatcherServletInitializer;

@Configuration
@ComponentScan("app")
public class Config extends AbstractAnnotationConfigDispatcherServletInitializer {
    @Override
    protected Class<?>[] getRootConfigClasses() {
        return new Class[0];
    }

    @Override
    protected Class<?>[] getServletConfigClasses() {
        return new Class[]{Config.class};
    }

    @Override
    protected String[] getServletMappings() {
        return new String[]{"/"};
    }
}