当application的jdk版本与服务器的jdk版本不一致下,常会出现bad version number异常消息。而这个问题的避免,咱们能够在网上搜罗信息,能够经过IDE设置complie level,来保证编译class的级别。这里很少说。 java
今天,我遇到的问题,也是bad version number的错误。可是我已经设置好了complie level,却依旧出现这样的问题。这个问题,并非在服务器启动时出现,而是由于我访问某个类的时候,出现如此问题。那么,如此证实了问题也不是我自身代码编译的问题(由于有能运行class)。 web
因而,我找到了代码的错误日志信息,发现如此:
apache
20131105 17:08:20 com.pdager.enavi.wap.web.impl.RedirectExceptionResolver - server error! java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1876) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:889) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1353) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1232) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.hibernate.connection.C3P0ConnectionProvider.configure(C3P0ConnectionProvider.java:92) at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124) at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56) at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:410) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:62) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292) at com.autonavi.data.persister.PersistenceFacade.<clinit>(PersistenceFacade.java:26) at com.autonavi.data.dao.LuckyHistoryDao.queryByCodeAndMdn(LuckyHistoryDao.java:36) at com.pdager.enavi.wap.servlet.DefaultQueryServlet.handlePost(DefaultQueryServlet.java:46) at com.pdager.enavi.wap.web.impl.ActiveHandler.handle(ActiveHandler.java:30) at com.pdager.enavi.wap.web.DispatcherServlet.service(DispatcherServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:595)
后来,通过查看Hibernate.jar和c3p0.jar的编译版本,均没有问题。但是,在我查看jdbc-driver.jar的时候,发现了问题,它的编译级别为1.6。至此,问题解决。 tomcat
注:
1. bad number version的错误缘由:在低版本的jdk下,运行高版本的jdk编译class
2. 不要怀疑本身,应该根据程序的提示,顺藤摸瓜,由于程序不说谎! 服务器