Issues
template might not exist or might not be accessible by any of the configured Template Resolvers
The spring boot error template might not exist or might not be accessible by any of the configured Template Resolvers occurs when the template files are not available in src/main/resources/templates folder or the file name is incorrect. The exception org.thymeleaf.exceptions.TemplateInputException: Error resolving template is thrown if the template file can
Path with “WEB-INF” or “META-INF”
The spring boot error Path with “WEB-INF” or “META-INF” occurs when the jsp page url is invoked and the tomcat jasper dependency is not configured in the application. The jsp files are compiled and rendered using the tomcat embedded jasper maven dependency. If the maven dependency is not configured in
javax.servlet.ServletException: Circular view path [error]: would dispatch back to the current handler URL [/error] again.
javax.servlet.ServletException: Circular view path [error]: would dispatch back to the current handler URL [/error] again. Check your ViewResolver setup! (Hint: This may be the result of an unspecified view, due to default view name generation.) The spring boot exception javax.servlet.ServletException: Circular view path [error]: would dispatch back to the current
Ambiguous mapping. Cannot map ‘basicErrorController’ method
Spring boot error Ambiguous mapping. Cannot map ‘basicErrorController’ method occurs when the url ‘/error’ url is configured in the request mapping annotation of the rest controller method. By default, “/error” is mapped in the BasicErrorController class to handle errors and exceptions in the spring boot application. This error occurs when
This application has no explicit mapping for /error, so you are seeing this as a fallback. Whitelabel error page
This application has no explicit mapping for /error, so you are seeing this as a fallback. error can be resolved in three ways, Identify the loading issue of the controller or method, disable the error page from the browser, and customize the error page to display the appropriate error message.
Web server failed to start. Port 8080 was already in use.
The spring boot Web server failed to start. Port 8080 was already in use. error occurs because port 8080 is already configured with another application, or port 8080 has not been released yet. The spring boot application is trying to configure port 8080 to start a web server. Since the
java.lang.IllegalArgumentException: Sources must not be empty
The spring boot error java.lang.IllegalArgumentException: Sources must not be empty occurs if the source class name is not specified in the SpringApplicationBuilder. When the spring boot application starts, this error is thrown in the console. SpringApplicationBuilder creates and loads the spring boot application using the name of the source class
Main method not found in class, please define the main method as: public static void main(String[] args) or a JavaFX
The java error: main method not found in the file, please define the main method as: public static void main(string[] args) occurs if the main method not found in class or the main method is not accessible or the main method is invalid. The main method indicates the start of