`
zhuxinzx
  • 浏览: 288702 次
  • 性别: Icon_minigender_1
  • 来自: 深圳
社区版块
存档分类
最新评论

启动Tomcat不能加载Servlet的问题:Error deploying web application directory

阅读更多
今天,在启动Tomcat服务器的时候,突然发现不能load已经存在的Servlet类,而且提示java.lang.UnsupportedClassVersionError: Bad version number in .class file ,JDK版本号不支持问题,抛出异常,详细异常信息如下所示:

2009-8-3 12:35:54 org.apache.catalina.core.AprLifecycleListener init
信息: Loaded APR based Apache Tomcat Native library 1.1.16.
2009-8-3 12:35:54 org.apache.catalina.core.AprLifecycleListener init
信息: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
2009-8-3 12:35:55 org.apache.coyote.http11.Http11AprProtocol init
信息: Initializing Coyote HTTP/1.1 on http-8080
2009-8-3 12:35:55 org.apache.coyote.ajp.AjpAprProtocol init
信息: Initializing Coyote AJP/1.3 on ajp-8009
2009-8-3 12:35:55 org.apache.catalina.startup.Catalina load
信息: Initialization processed in 949 ms
2009-8-3 12:35:55 org.apache.catalina.core.StandardService start
信息: Starting service Catalina
2009-8-3 12:35:55 org.apache.catalina.core.StandardEngine start
信息: Starting Servlet Engine: Apache Tomcat/6.0.20
2009-8-3 12:35:56 org.apache.catalina.core.ApplicationContext log
信息: ContextListener: contextInitialized()
2009-8-3 12:35:56 org.apache.catalina.core.ApplicationContext log
信息: SessionListener: contextInitialized()
2009-8-3 12:35:56 org.apache.tomcat.util.modeler.Registry registerComponent
严重: Null component Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/filter,J2EEApplication=none,J2EEServer=none
2009-8-3 12:35:56 org.apache.catalina.startup.HostConfig deployDirectory
严重: Error deploying web application directory filter
java.lang.UnsupportedClassVersionError: Bad version number in .class file (unable to load class org.shirdrn.action.FilterAction)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1854)
at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:890)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1354)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
at org.apache.catalina.startup.WebAnnotationSet.loadApplicationServletAnnotations(WebAnnotationSet.java:108)
at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnnotations(WebAnnotationSet.java:58)
at org.apache.catalina.startup.ContextConfig.applicationAnnotationsConfig(ContextConfig.java:297)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1068)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:261)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4339)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:987)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:909)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:495)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
2009-8-3 12:35:56 org.apache.coyote.http11.Http11AprProtocol start
信息: Starting Coyote HTTP/1.1 on http-8080
2009-8-3 12:35:56 org.apache.coyote.ajp.AjpAprProtocol start
信息: Starting Coyote AJP/1.3 on ajp-8009
2009-8-3 12:35:56 org.apache.catalina.startup.Catalina start
信息: Server startup in 1318 ms

因为原来一直是在MyEclipse 6.5上开发,昨天我重新安装了MyEclipse 7.1,在MyEclipse 7.1上。我猜想可能是MyEclipse 7.1版本比较新的原因,但是版本新导致不能加载Servlet这种可能不是很大,如果连加载类都成问题,那可不是一款优秀的IDE,起初我还是试着按照这种猜测去尝试,将在MyEclipse 6.5下最原始的备份重新导入MyEclipse 7.1,结果问题依然。

其实,异常已经显示了,WEB服务器启动的过程中抛出异常,也就说,可能的原因是某些对于WEB服务器直观重要的配置使其不能正常启动,最能想到的就是——Java虚拟机。因为异常java.lang.UnsupportedClassVersionError: Bad version number in .class file,可能是由于当前JDK版本不匹配造成的问题。

已经找到问题的根源,一步定位到Tomcat JDK的配置上去,能够解决问题的可能性最大。

下面是解决方法:

在MyEclipse 7.1中打开Preferences,定位到Servers服务器配置选项卡,如图所示:



一般MyEclipse 7.1默认的Tomcat JDK name是其自带的JDK 1.5,只需要添加一个当前在使用的版本的JDK,比如我的是JDK 1.6,然后再启动WEB服务器Tomcat,请求指定的Servlet,就能够成功加载Servlet类了。
分享到:
评论

相关推荐

Global site tag (gtag.js) - Google Analytics