Remember the example of a project that cannot be started after a Tomcat deployment project

Source: Internet
Author: User

 After a normal deployment, it was discovered that the project could not be started in Tomcat management and found the following error message in the Tomcat log file Localhost.log:

1Java.lang.NoSuchMethodError:org.springframework.core.GenericTypeResolver.resolveTypeArguments(Ljava/lang/class; Ljava/lang/class;) [ljava/lang/Class;2Org.springframework.core.convert.support.GenericConversionService.getRequiredTypeInfo ( genericconversionservice.java:260)3Org.springframework.core.convert.support.GenericConversionService.addConverter (Genericconversionservice.java : 83)4Org.springframework.core.convert.support.DefaultConversionService.addScalarConverters ( defaultconversionservice.java:63)5Org.springframework.core.convert.support.DefaultConversionService.addDefaultConverters ( defaultconversionservice.java:54)6Org.springframework.core.convert.support.defaultconversionservice.<init> (DefaultConversionService.java : 43)7Org.springframework.core.env.abstractpropertyresolver.<init> (abstractpropertyresolver.java:41)8Org.springframework.core.env.propertysourcespropertyresolver.<init> (Propertysourcespropertyresolver.java : 41)9Org.springframework.core.env.abstractenvironment.<init> (abstractenvironment.java:98)TenOrg.springframework.core.env.standardenvironment.<init> (standardenvironment.java:54) OneOrg.springframework.web.context.support.standardservletenvironment.<init> ( Standardservletenvironment.java:44) AOrg.springframework.web.servlet.HttpServletBean.createEnvironment (httpservletbean.java:213) -Org.springframework.web.servlet.HttpServletBean.getEnvironment (httpservletbean.java:203) -Org.springframework.web.servlet.HttpServletBean.init (httpservletbean.java:126) theJavax.servlet.GenericServlet.init (genericservlet.java:212) -Org.apache.catalina.valves.ErrorReportValve.invoke (errorreportvalve.java:102) -Org.apache.catalina.connector.CoyoteAdapter.service (coyoteadapter.java:298) -Org.apache.coyote.http11.Http11Processor.process (http11processor.java:852) +Org.apache.coyote.http11.http11protocol$http11connectionhandler.process (http11protocol.java:588) -Org.apache.tomcat.util.net.jioendpoint$worker.run (jioendpoint.java:489) +Java.lang.Thread.run (Unknown Source)

I later found out that I imported the updated spring package 3.1.2.RELEASE in my new myeclipse, and I was in conflict with the Spring3.0 package I used for my own project, causing the problem to occur.

So later if a project can be deployed and functioning in its own IDE, and deployment to the server does not start, it is likely that there is a conflict between the different versions of the package between the libraries.

Remember the example of a project that cannot be started after a Tomcat deployment project

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.