在搭建web項目時，出現一個比較詭異的問題，任何JSP頁面突然都不能夠正常地顯示，系統爆出HTTP：500(服務器內部錯誤)的頁面

HTTP Status 500 - java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem;

---

type?Exception report

message?java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem;

description?The server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem;org.apache.jasper.servlet.JspServlet.service(JspServlet.java:273)javax.servlet.http.HttpServlet.service(HttpServlet.java:727)org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238)org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:264)org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1208)org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:992)org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:939)org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:936)org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:827)javax.servlet.http.HttpServlet.service(HttpServlet.java:620)org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:812)javax.servlet.http.HttpServlet.service(HttpServlet.java:727)org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:77)org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

?

root cause

?

java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems()[Lorg/eclipse/jdt/core/compiler/IProblem; org.apache.jasper.compiler.JDTCompiler$2.acceptResult(JDTCompiler.java:354) org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:480) org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:425) org.apache.jasper.compiler.Compiler.compile(Compiler.java:298) org.apache.jasper.compiler.Compiler.compile(Compiler.java:277) org.apache.jasper.compiler.Compiler.compile(Compiler.java:265) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:564) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:299) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:315) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) javax.servlet.http.HttpServlet.service(HttpServlet.java:727) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238) org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:264) org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1208) org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:992) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:939) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:936) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:827) javax.servlet.http.HttpServlet.service(HttpServlet.java:620) org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:812) javax.servlet.http.HttpServlet.service(HttpServlet.java:727) org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:77) org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) ? 經過初步查看堆棧，大意是將JSP編譯成Servlet產生了錯誤，類不匹配，懷疑可能是JSTL，Servlet和Tomcat版本產生了沖突。一番折騰，沒有進展。 于是思考了一下，剛才只不過是添加了hadoop hdfs相關的jar包： <dependency><groupId>org.apache.hadoop</groupId><artifactId>hadoop-common</artifactId><version>2.2.0</version> </dependency><dependency><groupId>org.apache.hadoop</groupId><artifactId>hadoop-hdfs</artifactId><version>2.2.0</version> </dependency><dependency><groupId>org.apache.hadoop</groupId><artifactId>hadoop-auth</artifactId><version>2.2.0</version> </dependency> ? 難道是其中包含了一些特殊的依賴？通過IntelliJ Idea中的pom編輯器，可以顯示Maven Show Dependencies：

? 可以看出所有的依賴關系，果然，hadoop-common包依賴了servlet-api, jasper-runtime等可能與當前環境沖突的jar包，由于這些都是通過依賴關系鏈產生的關系，所以非常不容易被察覺。 同樣，也可以通過mvn自帶的工具在項目中命令行操作得到整個依賴的樹形結構： mvn dependency: tree [INFO] com.xxx:diablo-framework:war:1.0-SNAPSHOT [INFO] +- javax.servlet:jstl:jar:1.2:compile [INFO] +- javax:javaee-api:jar:6.0:provided [INFO] +- log4j:log4j:jar:1.2.8:compile [INFO] +- com.sun.mail:javax.mail:jar:1.5.2:compile [INFO] | \- javax.activation:activation:jar:1.1:compile [INFO] +- commons-io:commons-io:jar:2.4:compile [INFO] +- commons-beanutils:commons-beanutils:jar:1.9.2:compile [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile [INFO] | \- commons-collections:commons-collections:jar:3.2.1:compile [INFO] +- commons-lang:commons-lang:jar:2.6:compile [INFO] +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile [INFO] | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile [INFO] +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile [INFO] +- commons-httpclient:commons-httpclient:jar:3.1:test [INFO] | \- commons-codec:commons-codec:jar:1.2:compile [INFO] +- junit:junit:jar:4.11:test [INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test [INFO] +- org.springframework:spring-core:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-aop:jar:3.2.2.RELEASE:compile [INFO] | \- aopalliance:aopalliance:jar:1.0:compile [INFO] +- org.springframework:spring-aspects:jar:3.2.2.RELEASE:compile [INFO] | \- org.aspectj:aspectjweaver:jar:1.7.2:compile [INFO] +- org.springframework:spring-beans:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-context:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-context-support:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-dao:jar:2.0.8:compile [INFO] +- org.springframework:spring-expression:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-jdbc:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-jms:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-orm:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-oxm:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-test:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-tx:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-web:jar:3.2.2.RELEASE:compile [INFO] +- org.springframework:spring-webmvc:jar:3.2.2.RELEASE:compile [INFO] +- org.apache.commons:commons-exec:jar:1.3:compile [INFO] +- commons-dbcp:commons-dbcp:jar:1.4:compile [INFO] | \- commons-pool:commons-pool:jar:1.5.4:compile [INFO] +- org.hibernate:hibernate-core:jar:3.6.10.Final:compile [INFO] | +- antlr:antlr:jar:2.7.6:compile [INFO] | +- dom4j:dom4j:jar:1.6.1:compile [INFO] | +- org.hibernate:hibernate-commons-annotations:jar:3.2.0.Final:compile [INFO] | +- org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar:1.0.1.Final:compile [INFO] | +- javax.transaction:jta:jar:1.1:compile [INFO] | \- org.slf4j:slf4j-api:jar:1.6.1:compile [INFO] +- org.hibernate:hibernate-entitymanager:jar:3.6.10.Final:compile [INFO] | +- cglib:cglib:jar:2.2:compile [INFO] | | \- asm:asm:jar:3.1:compile [INFO] | \- javassist:javassist:jar:3.12.0.GA:compile [INFO] +- net.sf.ehcache:ehcache-core:jar:2.6.9:compile [INFO] +- mysql:mysql-connector-java:jar:5.1.31:compile [INFO] +- org.hsqldb:hsqldb:jar:2.2.9:compile [INFO] +- commons-fileupload:commons-fileupload:jar:1.3.1:compile [INFO] +- org.apache.poi:poi:jar:3.5-FINAL:compile [INFO] +- org.apache.poi:poi-ooxml:jar:3.5-FINAL:compile [INFO] | \- org.apache.poi:ooxml-schemas:jar:1.0:compile [INFO] | \- org.apache.xmlbeans:xmlbeans:jar:2.3.0:compile [INFO] | \- stax:stax-api:jar:1.0.1:compile [INFO] +- org.apache.oozie:oozie-client:jar:4.1.0:compile [INFO] | +- com.googlecode.json-simple:json-simple:jar:1.1:compile [INFO] | +- commons-cli:commons-cli:jar:1.2:compile [INFO] | +- com.google.guava:guava:jar:11.0.2:compile [INFO] | | \- com.google.code.findbugs:jsr305:jar:1.3.9:compile [INFO] | +- org.apache.activemq:activemq-client:jar:5.8.0:compile [INFO] | | +- org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile [INFO] | | +- org.fusesource.hawtbuf:hawtbuf:jar:1.9:compile [INFO] | | \- org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1:compile [INFO] | +- org.slf4j:slf4j-simple:jar:1.6.6:compile [INFO] | \- xerces:xercesImpl:jar:2.10.0:compile [INFO] | \- xml-apis:xml-apis:jar:1.4.01:compile [INFO] +- org.freemarker:freemarker:jar:2.3.20:compile [INFO] +- org.apache.hadoop:hadoop-common:jar:2.2.0:compile [INFO] | +- org.apache.hadoop:hadoop-annotations:jar:2.2.0:compile [INFO] | +- org.apache.commons:commons-math:jar:2.1:compile [INFO] | +- xmlenc:xmlenc:jar:0.52:compile [INFO] | +- commons-net:commons-net:jar:3.1:compile [INFO] | +- org.mortbay.jetty:jetty:jar:6.1.26:compile [INFO] | +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile [INFO] | +- com.sun.jersey:jersey-core:jar:1.9:compile [INFO] | +- com.sun.jersey:jersey-json:jar:1.9:compile [INFO] | | +- org.codehaus.jettison:jettison:jar:1.1:compile [INFO] | | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile [INFO] | | | \- javax.xml.bind:jaxb-api:jar:2.2.2:compile [INFO] | | \- org.codehaus.jackson:jackson-jaxrs:jar:1.8.3:compile [INFO] | +- com.sun.jersey:jersey-server:jar:1.9:compile [INFO] | +- commons-el:commons-el:jar:1.0:compile [INFO] | +- net.java.dev.jets3t:jets3t:jar:0.6.1:compile [INFO] | +- commons-configuration:commons-configuration:jar:1.6:compile [INFO] | | +- commons-digester:commons-digester:jar:1.8:compile [INFO] | | \- commons-beanutils:commons-beanutils-core:jar:1.8.0:compile [INFO] | +- org.slf4j:slf4j-log4j12:jar:1.7.5:compile [INFO] | +- org.apache.avro:avro:jar:1.7.4:compile [INFO] | | +- com.thoughtworks.paranamer:paranamer:jar:2.3:compile [INFO] | | \- org.xerial.snappy:snappy-java:jar:1.0.4.1:compile [INFO] | +- com.google.protobuf:protobuf-java:jar:2.5.0:compile [INFO] | +- com.jcraft:jsch:jar:0.1.42:compile [INFO] | +- org.apache.zookeeper:zookeeper:jar:3.4.5:compile [INFO] | \- org.apache.commons:commons-compress:jar:1.4.1:compile [INFO] | \- org.tukaani:xz:jar:1.0:compile [INFO] +- org.apache.hadoop:hadoop-hdfs:jar:2.2.0:compile [INFO] | +- commons-daemon:commons-daemon:jar:1.0.13:compile [INFO] | +- javax.servlet.jsp:jsp-api:jar:2.1:compile [INFO] | \- tomcat:jasper-runtime:jar:5.5.23:compile [INFO] +- org.apache.hadoop:hadoop-auth:jar:2.2.0:compile [INFO] +- com.xxx:diablo.communication:jar:1.0-SNAPSHOT:compile [INFO] +- com.caucho:hessian:jar:3.1.5:compile [INFO] \- org.quartz-scheduler:quartz:jar:1.8.4:compile ? 于是，通過右鍵將這些jar包排除(Exclude)出去，最后編輯生成的依賴成為了這樣： <dependency><groupId>org.apache.hadoop</groupId><artifactId>hadoop-common</artifactId><version>2.2.0</version><exclusions><exclusion><artifactId>servlet-api</artifactId><groupId>javax.servlet</groupId></exclusion><exclusion><artifactId>jasper-compiler</artifactId><groupId>tomcat</groupId></exclusion><exclusion><artifactId>jasper-runtime</artifactId><groupId>tomcat</groupId></exclusion><exclusion><artifactId>jsp-api</artifactId><groupId>javax.servlet.jsp</groupId></exclusion></exclusions> </dependency><dependency><groupId>org.apache.hadoop</groupId><artifactId>hadoop-hdfs</artifactId><version>2.2.0</version><exclusions><exclusion><artifactId>servlet-api</artifactId><groupId>javax.servlet</groupId></exclusion></exclusions> </dependency> ? ? 問題才得以解決，在普通的Java應用中，當出現相同版本的jar包，class時，是根據啟動時的CLASSPATH先后順序來決定最終使用的是哪個類型，但是這樣就非常不確定。雖然OSGi技術可以通過隔離ClassLoader的方式解決這個問題，但OSGi本身稍顯復雜臃腫，學習成本比較高，而且同樣需要一個OSGi容器。這就要求我們在平時引入新的jar包時能夠對其進行依賴分析，找出可能產生沖突的jar包，最終解決問題。

轉載于:https://www.cnblogs.com/mmaa/p/5789880.html

總結

以上是生活随笔為你收集整理的web项目中遇到的Maven包依赖冲突问题解决的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。